On Wed, 23 Nov 2005, Paul Cartwright wrote:
On Wed November 23 2005 11:55 am, Jon Nelson wrote:
I've been trying out the smart package manager on SuSE 10.0. When there are a lot of packages to update, 'smart --gui' "freezes" on me while "installing" the packages (after it has downloaded them). Not yet ready for the big time.
Try invoking it like this:
LD_ASSUME_KERNEL="2.4.0" smart ...
I am running 10.0 and uname says: 2.6.13-15-default
I just had smart lock up on me last night for the first time. Killing and restarting it worked. What doea that LD_ASSUME_KERNEL="2.4.0" give me?
It tells the linux dynamic symbol resolver (ld, basically) to use the
"old" threading library (linuxthreads) and not the new (nptl) one, among
other things (all threading related). My theory is that RPM's long
history of having a complicated threading model internally goes haywire
when run under a program that /itself/ is threaded. The semantics and
issues surrounding a threaded program forking and then execting another
program (which is also threaded) make my brain hurt.
Note that the smart package's upstream bug tracking system has a bug for
this entry already. Can anybody definitively say how apt (probably
threaded) behaves with respect to invoking RPM?
--
Carpe diem - Seize the day.
Carp in denim - There's a fish in my pants!
Jon Nelson