[gentoo-dev] Announcing new Prelinking Guide

[gentoo-dev] Announcing new Prelinking Guide

[John P. Davis]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks to the hard work of Cretin, we now have a guide that explains the ins 
and outs of prelinking in Gentoo. The document can be found here:
http://www.gentoo.org/doc/en/prelink-howto.xml

Cheers, and have fun!

//zhen
- -- 
John P. Davis
Gentoo Linux Documentation Developer / Bugzilla Administrator
http://www.gentoo.org
#gentoo-doc on irc.freenode.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+FObsYfES/KZpj3kRAhcfAJ9LZK/zL7xHtdRxd42EyaJPqEpmkgCfYsCP
9bd8+bMPz971LWxcdY2wN/8=
=T172
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Terje Kvernes]

"John P. Davis" <zhen@gentoo.org> writes:

> Thanks to the hard work of Cretin, we now have a guide that explains the ins 
> and outs of prelinking in Gentoo. The document can be found here:
> http://www.gentoo.org/doc/en/prelink-howto.xml

  well, I ran prelink, found out that all daemons had to be restarted,
  and figured I'd undo and look at it later.   bad idea.

  /usr went full, and now prelink segfaults midway through the KDE
  library directory.  I'm mostly just removing whatever it segfaults
  on and hoping it will continue.  my real problem however is this:

[x200 /] # python2.2
python2.2: error while loading shared libraries: unexpected PLT reloc type 0x00

  which sort of hurts when running Gentoo.  I'm fetching a stage3
  tarball on another system and I'll remerge, hm, kdelibs parts of
  gnome and what have you not once I get this working again.

  one might want to note on the webpage that this _might_ hurt.
  badly.  and maybe python should be protected from optimizations like
  this under Gentoo?

-- 
Terje

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Terje Kvernes]

Terje Kvernes <terjekv@math.uio.no> writes:

  [ ... ]

> [x200 /] # python2.2
> python2.2: error while loading shared libraries: unexpected PLT reloc type 0x00
> 
> which sort of hurts when running Gentoo.  I'm fetching a stage3
> tarball on another system and I'll remerge, hm, kdelibs parts of
> gnome and what have you not once I get this working again.

  ick!  I fixed this by getting the rc2-tarball and getting the binary
  from there.  luckily the rest of the state of the box ate that.
  but, when rebuilding kdelibs I get:

checking if STL implementation is SGI like... no
checking if STL implementation is HP like... no
configure: error: "no known STL type found - did you forget to install libstdc++-devel ?"

  oh well.  sigh.  I guess I'll have to rebuild GCC.  mental note:
  usermode-linux was made for testing stuff like this.  I wish I
  wasn't so trusting towards new things all the time.  :-)

-- 
Terje

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Stefan Jones]

Terje Kvernes said:
> Terje Kvernes <terjekv@math.uio.no> writes:
>
>  [ ... ]
>
>> [x200 /] # python2.2
>> python2.2: error while loading shared libraries: unexpected PLT reloc
>> type 0x00
>>
>> which sort of hurts when running Gentoo.  I'm fetching a stage3
>> tarball on another system and I'll remerge, hm, kdelibs parts of gnome
>> and what have you not once I get this working again.
>
>  ick!  I fixed this by getting the rc2-tarball and getting the binary
>  from there.  luckily the rest of the state of the box ate that.
>  but, when rebuilding kdelibs I get:
>
> checking if STL implementation is SGI like... no
> checking if STL implementation is HP like... no
> configure: error: "no known STL type found - did you forget to install
> libstdc++-devel ?"
>
>  oh well.  sigh.  I guess I'll have to rebuild GCC.  mental note:
>  usermode-linux was made for testing stuff like this.  I wish I
>  wasn't so trusting towards new things all the time.  :-)

Well I'm sorry about this but I have had no reports about any such problems.
Prelink was tested by many people (10's of system which included
installing prelink at the start and upgrading a system to prelink)
The error you got is fairly unique, could anyone else confirm?

Note that prelink is statically linked, and so is sash, so rescue is
always possible, I haven't seen prelink --undo fail, did it for you?
I am guessing this is a compound error,

Stefan




--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Terje Kvernes]

"Stefan Jones" <cretin@gentoo.org> writes:

  [ ... ]

> > oh well.  sigh.  I guess I'll have to rebuild GCC.  mental note:
> > usermode-linux was made for testing stuff like this.  I wish I
> > wasn't so trusting towards new things all the time.  :-)
> 
> Well I'm sorry about this but I have had no reports about any such
> problems.  

  it's not your fault, nothing to be sorry about.  there are
  eventualities one cannot predict without reading the source and
  trying very hard to think "what if" everywhere.  my only concern is
  that prelink alters the one thing you really need to survive,
  library management, and a small note might be appropriate.  it might
  also just be me, but why does prelink need to place its temporary
  files on the same filesystem as the original file?  atomic mv?

> Prelink was tested by many people (10's of system which included
> installing prelink at the start and upgrading a system to prelink)

  the problem is that /usr went full while prelink was doing undo.
  that caused it to report I/O errors and corrupt libraries and
  binaries for a while.  no, it wasn't harddrive problems.  the system
  logs don't mention anything with regards to hda.  trust me, I
  checked that rather quickly when something returns I/O errors. 

  I doubt that the filesystem (reiserfs in this situation) manages to
  report I/O error to an application without logging the event.  I
  will however do a badblock readonly test just to be sure.

> The error you got is fairly unique, could anyone else confirm?

  try filling /usr and then run prelink.  preferably leave a little
  space so it'll start on its job.  when it then starts to fail, and
  things crash, use "undo" for maximum carnage.  I'm not in a position
  to test this for another day or two.  I'm still digging up broken
  libraries.

  it might also be a good idea to create a log from what prelink did?

prelink -afmRv > /tmp/prelink.log 2> /tmp/prelink.error.log

  if the user has tee, errors should probably be sent both to STDERR
  and to a logfile.  at least I think it's -v for prelink?

[x200 /usr/bin] # man prelink
-bash: /usr/bin/man: cannot execute binary file

  life is interesting.  for some reason I'm not booting the box or
  closing my already open applications.  :-)
 
> Note that prelink is statically linked, and so is sash, so rescue is
> always possible, 

  of course, and I have enough hardware to be able to get or build
  whatever I need.  it's just not overly fun to rebuild stuff like X,
  Gnome and KDE in Gentoo.  buildpkg?  right.  stupid me saw that /usr
  was very full and zapped the files.  I'm creating a small LV for the
  packages now.  and my other Gentoo-box runs 1.2 still, so I can test
  my builds with gcc-2.95 before committing them to bugzilla.  

> I haven't seen prelink --undo fail, did it for you?

  yup.  it keeps segfaulting when it reaches the KDE-libraries that
  were bitten by the I/O issues.

> I am guessing this is a compound error,

  I am guessing that someone needs to handle error situations better
  in prelink.  the exact error message is lost, since the shell died
  quickly after the problems started.

-- 
Terje

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Terje Kvernes]

"Stefan Jones" <cretin@gentoo.org> writes:

> Note that prelink is statically linked, and so is sash, so rescue is
> always possible, I haven't seen prelink --undo fail, did it for you?

  I'm getting a lot of segfaults when I try to undo prelink.  any
  suggestions to save me from rebuilding pretty much everything?  I'm
  not sure how to find broken libraries even, so I'm just emergeing
  stuff that is broken when I find it to be so.

[x200 /usr/bin] # strace -f prelink -u /usr/lib/libMagick.so.5.0.47 
execve("/usr/sbin/prelink", ["prelink", "-u", "/usr/lib/libMagick.so.5.0.47"], [/* 42 vars */]) = 0
fcntl64(0, F_GETFD)                     = 0
fcntl64(1, F_GETFD)                     = 0
fcntl64(2, F_GETFD)                     = 0
uname({sys="Linux", node="x200.forsaken.lands", ...}) = 0
geteuid32()                             = 0
getuid32()                              = 0
getegid32()                             = 0
getgid32()                              = 0
brk(0)                                  = 0x80ffd84
brk(0x8100d84)                          = 0x8100d84
brk(0x8101000)                          = 0x8101000
open("/usr/lib/libMagick.so.5.0.47", O_RDONLY) = 3
lseek(3, 0, SEEK_END)                   = 2035255
mmap2(NULL, 2035255, PROT_READ|PROT_WRITE, MAP_PRIVATE, 3, 0) = 0x40000000
brk(0x8102000)                          = 0x8102000
brk(0x8103000)                          = 0x8103000
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++

-- 
Terje

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Terje Kvernes]

Terje Kvernes <terjekv@math.uio.no> writes:

> I'm getting a lot of segfaults when I try to undo prelink.  any
> suggestions to save me from rebuilding pretty much everything?  I'm
> not sure how to find broken libraries even, so I'm just emergeing
> stuff that is broken when I find it to be so.

  right.  broken stuff, be it binaries or libraries, come up as "data"
  with "file".  this can, thankfully, be used to find most of the
  broken stuff:

for f in $( file /usr/bin/* /bin/* /usr/X11R6/bin/* /usr/lib/*.so\
/lib/*.so /usr/kde/3/lib/*.so | grep ":.*data" |\
cut -f1 -d: ); do qpkg -nc -f $f; done | sort | uniq > /tmp/packages

  this harked up the following packages on my box, after I've rebuilt
  about ten or so by hand.  at least that's a start.  :-)

  hm, what other directories should I check?

Calculating dependencies ...done!
[ebuild   R  ] app-cdr/cdrtools-2.0 
[ebuild   R  ] app-editors/vim-core-6.1-r2 
[ebuild   R  ] app-misc/jail-1.9 
[ebuild   R  ] app-text/ispell-3.2.06-r5 
[ebuild   R  ] app-text/openjade-1.3.1-r6 
[ebuild   R  ] dev-libs/pilot-link-0.11.3 
[ebuild   R  ] dev-util/guile-1.4.1 
[ebuild   R  ] gnome-base/ORBit-0.5.17 
[ebuild   R  ] gnome-base/bonobo-activation-1.0.4 
[ebuild   R  ] gnome-base/control-center-2.0.3 
[ebuild   R  ] gnome-base/gdm-2.4.0.12-r2 
[ebuild   R  ] gnome-base/gnome-libs-1.4.2 
[ebuild   R  ] gnome-base/gnome-panel-2.0.11 
[ebuild   R  ] gnome-extra/gnome-games-2.0.6 
[ebuild   R  ] media-gfx/eog-1.0.4 
[ebuild   R  ] media-gfx/imagemagick-5.4.7.4 
[ebuild   R  ] media-gfx/xv-3.10a-r2 
[ebuild   R  ] media-libs/giflib-4.1.0-r3 
[ebuild   R  ] media-libs/libgd-1.8.3-r5 
[ebuild   R  ] media-libs/libquicktime-0.9.2_pre1 
[ebuild   R  ] media-libs/speex-1.0_beta3 
[ebuild   R  ] media-libs/tiff-3.5.7-r1 
[ebuild   R  ] media-sound/vorbis-tools-1.0-r1 
[ebuild   R  ] media-video/transcode-0.6.0 
[ebuild   R  ] media-video/xawtv-3.80 
[ebuild   R  ] net-nds/openldap-2.0.27 
[ebuild   R  ] sys-apps/kbd-1.06-r1 
[ebuild   R  ] sys-apps/shadow-4.0.3-r3 
[ebuild   R  ] sys-apps/texinfo-4.3 
[ebuild   R  ] sys-apps/textutils-2.1 
[ebuild   R  ] sys-apps/util-linux-2.11y 
[ebuild   R  ] sys-devel/gettext-0.11.5 
[ebuild   R  ] sys-libs/db-3.2.9-r1 
[ebuild   R  ] sys-libs/glibc-2.3.1-r2 
[ebuild   R  ] x11-wm/enlightenment-0.16.5-r4 
[ebuild   R  ] kde-base/kdebase-3.0.5a 
  

-- 
Terje

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Stefan Jones]

On Fri, 2003-01-03 at 20:54, Terje Kvernes wrote:
>   right.  broken stuff, be it binaries or libraries, come up as "data"
>   with "file".  this can, thankfully, be used to find most of the
>   broken stuff:
> 
> for f in $( file /usr/bin/* /bin/* /usr/X11R6/bin/* /usr/lib/*.so\
> /lib/*.so /usr/kde/3/lib/*.so | grep ":.*data" |\
> cut -f1 -d: ); do qpkg -nc -f $f; done | sort | uniq > /tmp/packages
> 
Good idea, be careful not only binaries reside in those dirs, but that
will not hurt you.

>   this harked up the following packages on my box, after I've rebuilt
>   about ten or so by hand.  at least that's a start.  :-)
> 
>   hm, what other directories should I check?
> 
see /etc/prelink.conf for the dirs prelink reads

-- 
Stefan Jones <cretin@gentoo.org>
Gentoo Linux


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Terje Kvernes]

Stefan Jones <cretin@gentoo.org> writes:

> On Fri, 2003-01-03 at 20:54, Terje Kvernes wrote:
>
> > right.  broken stuff, be it binaries or libraries, come up as
> > "data" with "file".  this can, thankfully, be used to find most of
> > the broken stuff:
> > 
> > for f in $( file /usr/bin/* /bin/* /usr/X11R6/bin/* /usr/lib/*.so\
> > /lib/*.so /usr/kde/3/lib/*.so | grep ":.*data" |\
> > cut -f1 -d: ); do qpkg -nc -f $f; done | sort | uniq > /tmp/packages
>  
> Good idea, be careful not only binaries reside in those dirs, but
> that will not hurt you.

  I know.  and it works.  :-)

  I've now rebuilt every package I listed earlier, as well as kdebase
  and kdelibs.  things work[tm].  there might have been some slipups,
  somewhere, but I'll find them eventually.  oh, interesting sidenote.
  some merges like ORBit2 actually required me to remove the old
  libraries from the same package by hand first, as the build (make)
  for some reason tried to use those libraries.  when I removed them
  manually (they where broken anyway), things worked.

  so a rescue guide should probably include removing the broken files
  after we've made the package list, and before we start to remerge
  stuff.
 
> > hm, what other directories should I check?
>  
> see /etc/prelink.conf for the dirs prelink reads
  
  er, good point.  thanks.

-- 
Terje

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Stefan Jones]

On Fri, 2003-01-03 at 19:21, Terje Kvernes wrote:
> "Stefan Jones" <cretin@gentoo.org> writes:
> 
> > Note that prelink is statically linked, and so is sash, so rescue is
> > always possible, I haven't seen prelink --undo fail, did it for you?
> 
>   I'm getting a lot of segfaults when I try to undo prelink.  any
>   suggestions to save me from rebuilding pretty much everything?  I'm
>   not sure how to find broken libraries even, so I'm just emergeing
>   stuff that is broken when I find it to be so.


Lots of problems here. It seems that because of the disk space shortage
some libraries must of got corrupted and thus are unfixable, they
probably got truncated.

How much was the amount of space used up by prelink, details, so I can
update my howto, for I think as you say, that was the source of the
errors. 

Stefan

-- 
Stefan Jones <cretin@gentoo.org>
Gentoo Linux


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Terje Kvernes]

Stefan Jones <cretin@gentoo.org> writes:

> On Fri, 2003-01-03 at 19:21, Terje Kvernes wrote:
>
> > I'm getting a lot of segfaults when I try to undo prelink.  any
> > suggestions to save me from rebuilding pretty much everything?
> > I'm not sure how to find broken libraries even, so I'm just
> > emergeing stuff that is broken when I find it to be so.
> 
> Lots of problems here. 

  ouch.  you have my sympathy.  thanks for testing, I hope you did so
  with careful planning?  :-)

> It seems that because of the disk space shortage some libraries must
> of got corrupted and thus are unfixable, they probably got
> truncated.

  good point.  I thought that should be easy enough to check so I
  created a small logical volume directory for testing.  I then ran
  prelink -v /mnt/prelink/*.so, and even if the partition was 100%
  full it ran okay.  well, seemingly at least.  nothing ended up as
  "data".  I wonder what libraries cause massive space usage?
 
> How much was the amount of space used up by prelink, details, so I
> can update my howto, for I think as you say, that was the source of
> the errors.

  I noticed the space on /usr having 50MiB free at one point, and
  dropping down to around 10MiB when I reran "prelink -u".  I'd say
  that 100MiB should be plenty, and probably give us a bit of
  headspace as well.  I'll try to reproduce the events under
  controlled circumstances.  

  anyhow, since /etc/prelink.conf contains all the stuff that can be
  broken, this find everything that is broken, and then some:

for build in $(
  for broken in $(
    for dir in $( grep -v '#' /etc/prelink.conf | cut -f2 -d' ' );
      do
       file $dir/* | grep ":.*data";
    done | cut -f1 -d: );
    do     
     qpkg -v -nc -f $broken;
  done | sort | uniq );
do echo "=$build"; done
  
  produces a nice list to feed emerge:

=dev-util/guile-1.4-r3
=gnome-base/gnome-panel-1.4.1
=kde-base/kdebase-3.0.5a
=kde-base/kdelibs-3.0.5a
=kde-base/kdemultimedia-3.0.5a
=media-video/transcode-0.6.0
=media-video/xawtv-3.80
=net-print/cups-1.1.18
=sys-libs/cracklib-2.7-r6
=sys-libs/db-1.85-r1
=x11-libs/qt-3.1.0-r1

  emerge $( for ... ) works as it should, and grabs the proper
  versions.

  the only false positive I find comes from /usr/lib/cracklib_dict.hwm
  and will require a remerge of cracklib, which isn't that bad.  one
  can of course just grep that away, if you know it's clean.  there is
  also the issue that ORBit2 required me to delete the broken
  libraries by hand, and also that packages have to be built in the
  correct order.  building kdelibs with a broken kdebase doesn't quite
  work.  but, at least the above script should ease ones pain.
  
-- 
Terje

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Bart Verwilst]

On Saturday 04 January 2003 23:18, Terje Kvernes wrote:
||    I noticed the space on /usr having 50MiB free at one point, and
||    dropping down to around 10MiB when I reran "prelink -u".  I'd say
||    that 100MiB should be plenty, and probably give us a bit of
||    headspace as well.  I'll try to reproduce the events under
||    controlled circumstances.

MiB, are those MiniBytes or something? :op
Hehe, just kidding ;o) I only wanted to say that prelinking worked flawlessly 
here. Cool stuff ;o)

See ya
-- 
Bart Verwilst
Gentoo Linux Developer, Desktop Team
Gent, Belgium

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[William Kenworthy]

Does pre-linking work with openoffice - and is there a noticable
difference in performance?

BillK


On Sun, 2003-01-05 at 07:11, Bart Verwilst wrote:
> On Saturday 04 January 2003 23:18, Terje Kvernes wrote:
> ||    I noticed the space on /usr having 50MiB free at one point, and
> ||    dropping down to around 10MiB when I reran "prelink -u".  I'd say
> ||    that 100MiB should be plenty, and probably give us a bit of
> ||    headspace as well.  I'll try to reproduce the events under
> ||    controlled circumstances.
> 
> MiB, are those MiniBytes or something? :op
> Hehe, just kidding ;o) I only wanted to say that prelinking worked flawlessly 
> here. Cool stuff ;o)
> 
> See ya
> -- 
> Bart Verwilst
> Gentoo Linux Developer, Desktop Team
> Gent, Belgium
> 
> --
> gentoo-dev@gentoo.org mailing list
> 
> 



--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Paul de Vrieze]

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 452 bytes --]

On Sunday 05 January 2003 00:24, William Kenworthy wrote:
> Does pre-linking work with openoffice - and is there a noticable
> difference in performance?

Not by default as it uses libraries in it's own directory which the prelinker 
cannot find. I believe if you add the openoffice library dir it should work 
though with a self-compiled openoffice.

Paul

-- 
Paul de Vrieze
Junior Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.devrieze.net

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Announcing new Prelinking Guide

[Terje Kvernes]

Bart Verwilst <verwilst@gentoo.org> writes:

  [ ... ]

> MiB, are those MiniBytes or something? :op

  <url: http://physics.nist.gov/cuu/Units/binary.html >

> Hehe, just kidding ;o) I only wanted to say that prelinking worked
> flawlessly here. Cool stuff ;o)

  good to see it working as it should.  I'll probably retry prelink
  around here, eventually.  :-)

-- 
Terje

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[John P. Davis]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 03 January 2003 03:06 am, Terje Kvernes wrote:
> "John P. Davis" <zhen@gentoo.org> writes:
> > Thanks to the hard work of Cretin, we now have a guide that explains the
> > ins and outs of prelinking in Gentoo. The document can be found here:
> > http://www.gentoo.org/doc/en/prelink-howto.xml
>
>   well, I ran prelink, found out that all daemons had to be restarted,
>   and figured I'd undo and look at it later.   bad idea.
>
>   /usr went full, and now prelink segfaults midway through the KDE
>   library directory.  I'm mostly just removing whatever it segfaults
>   on and hoping it will continue.  my real problem however is this:
>
> [x200 /] # python2.2
> python2.2: error while loading shared libraries: unexpected PLT reloc type
> 0x00
>
>   which sort of hurts when running Gentoo.  I'm fetching a stage3
>   tarball on another system and I'll remerge, hm, kdelibs parts of
>   gnome and what have you not once I get this working again.
>
>   one might want to note on the webpage that this _might_ hurt.
>   badly.  and maybe python should be protected from optimizations like
>   this under Gentoo?

I have forwarded this to the guy that wrote the guide, and we will take care 
of it. I hope your system gets better!

Cheers,
//zhen

- -- 
John P. Davis
Gentoo Linux Documentation Developer / Bugzilla Administrator
http://www.gentoo.org
#gentoo-doc on irc.freenode.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+FZbYYfES/KZpj3kRAmraAKCFipqa/MbdTd0Dtrla3L32UO6q6ACdF3+e
JXTd0tlefE0FsBg4PGmEE4Q=
=yEii
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Terje Kvernes]

"John P. Davis" <zhen@gentoo.org> writes:

> On Friday 03 January 2003 03:06 am, Terje Kvernes wrote:
>
> >   well, I ran prelink, found out that all daemons had to be restarted,
> >   and figured I'd undo and look at it later.   bad idea.
> >
> >   /usr went full, and now prelink segfaults midway through the KDE
> >   library directory.  I'm mostly just removing whatever it segfaults
> >   on and hoping it will continue.  my real problem however is this:
> >
> > [x200 /] # python2.2
> > python2.2: error while loading shared libraries: unexpected PLT reloc type
> > 0x00
> >
> >   which sort of hurts when running Gentoo.  I'm fetching a stage3
> >   tarball on another system and I'll remerge, hm, kdelibs parts of
> >   gnome and what have you not once I get this working again.
> >
> >   one might want to note on the webpage that this _might_ hurt.
> >   badly.  and maybe python should be protected from optimizations like
> >   this under Gentoo?
> 
> I have forwarded this to the guy that wrote the guide, and we will take care 
> of it. I hope your system gets better!

  it will, over time.  :-)

  I have to admit though, sometimes I'd give an arm and a leg for not
  just a portage-rescue, but also rescues for python and gcc.  you
  don't get far in Gentoo when python or gcc are dead.

  the idea would be to produce a package containing portage, python,
  gcc that would install gcc, python and portage by itself when
  invoked.  I'm not sure how much time you'd save from bootstrapping,
  but you'd be able to rescue your basic system fairly easy.

  besides, it should be fully doable to automatically build packages
  that do this?  if there is real interest, maybe I'll have a go at it
  myself.

-- 
Terje

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Toby Dickenson]

On Friday 03 January 2003 5:23 pm, Terje Kvernes wrote:

>   I have to admit though, sometimes I'd give an arm and a leg for not
>   just a portage-rescue, but also rescues for python and gcc.  you
>   don't get far in Gentoo when python or gcc are dead.

I like to keep a second bootable copy of the root and /usr partition on lvm 
for this type of emergency. Its worth the 3G of disk space



--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Terje Kvernes]

Toby Dickenson <tdickenson@devmail.geminidataloggers.co.uk> writes:

> On Friday 03 January 2003 5:23 pm, Terje Kvernes wrote:
> 
> > I have to admit though, sometimes I'd give an arm and a leg for
> > not just a portage-rescue, but also rescues for python and gcc.
> > you don't get far in Gentoo when python or gcc are dead.
> 
> I like to keep a second bootable copy of the root and /usr partition
> on lvm for this type of emergency. Its worth the 3G of disk space

  you do have a good point.  diskspace is practically free these
  days.

-- 
Terje

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Paul de Vrieze]

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 485 bytes --]

On Friday 03 January 2003 02:27, John P. Davis wrote:
> Thanks to the hard work of Cretin, we now have a guide that explains the
> ins and outs of prelinking in Gentoo. The document can be found here:
> http://www.gentoo.org/doc/en/prelink-howto.xml
>
> Cheers, and have fun!
>

One note is that for me I needed to rebuild lcms (color managment) and qt 
afterwards to make things go.

Paul

-- 
Paul de Vrieze
Junior Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.devrieze.net

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Announcing new Prelinking Guide

[Caleb Shay]

[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]

2 things.

1) You spelled "summary" wrong (summery)

2) prelink -famv segfaults for me:

<snip lots of stuff working correctly>
/usr/lib/libnautilus-adapter.so.2                415ec000-415ee494
/usr/lib/libpcreposix.so.0                       41152000-41154770
/usr/lib/libcpuaccel.so.0                        41288000-41289900
Segmentation fault

Thinking that maybe it was failing on /usr/lib/libcpuaccel.so.0 I tried

prelink -mfv /usr/lib/libcpuaccel.so.0

and that completes without error, so I guess it is segfaulting on
whatever it is trying to prelink next, but I don't know what that is. 
Any tips?

Caleb Shay
caleb@webninja.com


On Thu, 2003-01-02 at 20:27, John P. Davis wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Thanks to the hard work of Cretin, we now have a guide that explains the ins 
> and outs of prelinking in Gentoo. The document can be found here:
> http://www.gentoo.org/doc/en/prelink-howto.xml
> 
> Cheers, and have fun!
> 
> //zhen
> - -- 
> John P. Davis
> Gentoo Linux Documentation Developer / Bugzilla Administrator
> http://www.gentoo.org
> #gentoo-doc on irc.freenode.net
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
> 
> iD8DBQE+FObsYfES/KZpj3kRAhcfAJ9LZK/zL7xHtdRxd42EyaJPqEpmkgCfYsCP
> 9bd8+bMPz971LWxcdY2wN/8=
> =T172
> -----END PGP SIGNATURE-----
> 
> 
> --
> gentoo-dev@gentoo.org mailing list
-- 
Caleb Shay <caleb@webninja.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Announcing new Prelinking Guide

[Terje Kvernes]

Caleb Shay <caleb@webninja.com> writes:

> 2 things.
> 
> 1) You spelled "summary" wrong (summery)
> 
> 2) prelink -famv segfaults for me:
> 
> <snip lots of stuff working correctly>
> /usr/lib/libnautilus-adapter.so.2                415ec000-415ee494
> /usr/lib/libpcreposix.so.0                       41152000-41154770
> /usr/lib/libcpuaccel.so.0                        41288000-41289900
> Segmentation fault

  ick.  been there, done that.  I don't know what caused the error
  though, I was too busy rebuilding stuff.
 
> Thinking that maybe it was failing on /usr/lib/libcpuaccel.so.0 I
> tried
> 
> prelink -mfv /usr/lib/libcpuaccel.so.0
> 
> and that completes without error, so I guess it is segfaulting on
> whatever it is trying to prelink next, but I don't know what that
> is.  Any tips?

  yeah. 

strace -f -eopen,stat64 prelink -famv

  should show you the culprit.

-- 
Terje

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Caleb Shay]

And the culprit is...<drum roll please>..

/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2

Bloody gcc.  I'll have to rebuild that again for something like the 5th
time this week.  Bah!



> > and that completes without error, so I guess it is segfaulting on
> > whatever it is trying to prelink next, but I don't know what that
> > is.  Any tips?
> 
>   yeah. 
> 
> strace -f -eopen,stat64 prelink -famv
> 
>   should show you the culprit.
-- 
Caleb Shay <caleb@webninja.com>


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Caleb Shay]

[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]

And that didn't fix it.  Hmmm.  Still segfaulting at the same place.  I
tried running

prelink -fmv /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2

and that finished fine.

Last few lines from
strace -f -eopen,stat64 prelink -famv

stat64("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libgcc_s.so.1",
{st_mode=S_IFREG|0644, st_size=833765, ...}) = 0
Prelinking /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2
open("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2",
O_RDONLY|O_LARGEFILE) = 3
open("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2.#prelink#.ufprtp", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0600) = 4
--- SIGCHLD (Child exited) ---
stat64("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2",
{st_mode=S_IFREG|0755, st_size=4233762, ...}) = 0
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++


Any more ideas?

Thanks.

Caleb


On Sat, 2003-01-04 at 22:52, Caleb Shay wrote:
> And the culprit is...<drum roll please>..
> 
> /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2
> 
> Bloody gcc.  I'll have to rebuild that again for something like the 5th
> time this week.  Bah!
> 
> 
> 
> > > and that completes without error, so I guess it is segfaulting on
> > > whatever it is trying to prelink next, but I don't know what that
> > > is.  Any tips?
> > 
> >   yeah. 
> > 
> > strace -f -eopen,stat64 prelink -famv
> > 
> >   should show you the culprit.
-- 
Caleb Shay <caleb@webninja.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Announcing new Prelinking Guide

[Terje Kvernes]

Caleb Shay <caleb@webninja.com> writes:

> And that didn't fix it.  Hmmm.  Still segfaulting at the same place.  I
> tried running
> 
> prelink -fmv /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2
> 
> and that finished fine.
> 
> Last few lines from
> strace -f -eopen,stat64 prelink -famv
> 
> stat64("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libgcc_s.so.1",
> {st_mode=S_IFREG|0644, st_size=833765, ...}) = 0
> Prelinking /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2
> open("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2",
> O_RDONLY|O_LARGEFILE) = 3
> open("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2.#prelink#.ufprtp", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0600) = 4
> --- SIGCHLD (Child exited) ---
> stat64("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2",
> {st_mode=S_IFREG|0755, st_size=4233762, ...}) = 0
> --- SIGSEGV (Segmentation fault) ---
> +++ killed by SIGSEGV +++
> 
> 
> Any more ideas?

  run "strace -f prelink -famv".  and please tell me that mmap or one
  of his brothers isn't the last thing there.

-- 
Terje

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Caleb Shay]

[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]

On Sun, 2003-01-05 at 00:27, Terje Kvernes wrote:

<snip>

> 
>   run "strace -f prelink -famv".  and please tell me that mmap or one
>   of his brothers isn't the last thing there.


Well, not quite the last thing...

munmap(0x40654000, 274432)              = 0
munmap(0x406c5000, 188416)              = 0
close(4)                                = 0
munmap(0x40697000, 188416)              = 0
brk(0x8cf1000)                          = 0x8cf1000
munmap(0x40611000, 274432)              = 0
brk(0x8cc7000)                          = 0x8cc7000
munmap(0x405a9000, 212992)              = 0
munmap(0x40167000, 2232320)             = 0
munmap(0x400f3000, 237568)              = 0
brk(0x8ca2000)                          = 0x8ca2000
brk(0x8c72000)                          = 0x8c72000
munmap(0x40027000, 417792)              = 0
close(3)                                = 0
time(NULL)                              = 1041747716
utime("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2.#prelink#.UofgUB", [2003/01/05-01:21:56, 2003/01/04-23:28:30]) = 0
rename("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2.#prelink#.UofgUB", "/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2") = 0
stat64("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2",
{st_mode=S_IFREG|0755, st_size=4233762, ...}) = 0
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Announcing new Prelinking Guide

[Terje Kvernes]

Caleb Shay <caleb@webninja.com> writes:

> On Sun, 2003-01-05 at 00:27, Terje Kvernes wrote:
> 
> > run "strace -f prelink -famv".  and please tell me that mmap or
> > one of his brothers isn't the last thing there.
> 
> Well, not quite the last thing...
> 
> munmap(0x40654000, 274432)              = 0
> munmap(0x406c5000, 188416)              = 0
> close(4)                                = 0
> munmap(0x40697000, 188416)              = 0
> brk(0x8cf1000)                          = 0x8cf1000
> munmap(0x40611000, 274432)              = 0
> brk(0x8cc7000)                          = 0x8cc7000
> munmap(0x405a9000, 212992)              = 0
> munmap(0x40167000, 2232320)             = 0
> munmap(0x400f3000, 237568)              = 0
> brk(0x8ca2000)                          = 0x8ca2000
> brk(0x8c72000)                          = 0x8c72000
> munmap(0x40027000, 417792)              = 0
> close(3)                                = 0
> time(NULL)                              = 1041747716
> utime("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2.#prelink#.UofgUB", [2003/01/05-01:21:56, 2003/01/04-23:28:30]) = 0
> rename("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2.#prelink#.UofgUB", "/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2") = 0
> stat64("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2",
> {st_mode=S_IFREG|0755, st_size=4233762, ...}) = 0
> --- SIGSEGV (Segmentation fault) ---
> +++ killed by SIGSEGV +++

  this is weird.  okay, so prelink correctly renames the prelink
  mktemp'ed file to the original.  then it does a stat, which returns
  properly, _then_ it segfaults.  I peeked a quick peek at the source
  code, but I'm too tired to dig up anything overly useful from C.  it
  does however look very buggy.  :-/

  but it does work fine if you do

prelink -v /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2

  right?

-- 
Terje

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Caleb Shay]

[-- Attachment #1: Type: text/plain, Size: 1387 bytes --]


>   this is weird.  okay, so prelink correctly renames the prelink
>   mktemp'ed file to the original.  then it does a stat, which returns
>   properly, _then_ it segfaults.  I peeked a quick peek at the source
>   code, but I'm too tired to dig up anything overly useful from C.  it
>   does however look very buggy.  :-/
> 
>   but it does work fine if you do
> 
> prelink -v /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2
> 
>   right?

Actually, this time it didn't (Abort, not segfault), but 
prelink -mvf /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2
worked fine.


Hmm, here's a strange little test case:

#prelink -amv
...
Prelinking /usr/lib/gimp/1.2/plug-ins/sample_colorize
Segmentation fault

#prelink -mvf /usr/lib/gimp/1.2/plug-ins/sample_colorize
<completes fine>

#prelink -amv
...
/usr/lib/libcpuaccel.so.0                                    4114a000-4114b900
Segmentation fault

#prelink -mvf /usr/lib/libcpuaccel.so.0
<completes fine>

#prelink -amv
...
Prelinking /usr/lib/gimp/1.2/plug-ins/sample_colorize
Segmentation fault

and it will just keep alternating between those two.

Note that libcpuaccel.so.0 is the item that comes just before
the gimp stuff when it gets that far.

licpuaccel is from media-libs/libmpeg2, you probably know what the gimp stuff
is from.

Cheers,
Caleb



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Announcing new Prelinking Guide

[Stefan Jones]

On Sun, 2003-01-05 at 08:01, Caleb Shay wrote:
> Prelinking /usr/lib/gimp/1.2/plug-ins/sample_colorize
> Segmentation fault
> 


I am not really all that surprised that is fails on a plugin as plugins
are loaded on demand, thus prelinking them has little purpose as the
loader has little chance of making use of the prelink info. Also they
could have all sorts of strange dependencies on symbols in the parent
gimp executable.


-- 
Stefan Jones <cretin@gentoo.org>
Gentoo Linux


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Werner Van Belle]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 05 January 2003 14:20, Stefan Jones wrote:
> On Sun, 2003-01-05 at 08:01, Caleb Shay wrote:
> > Prelinking /usr/lib/gimp/1.2/plug-ins/sample_colorize
> > Segmentation fault
>
> I am not really all that surprised that is fails on a plugin as plugins
> are loaded on demand, thus prelinking them has little purpose as the
> loader has little chance of making use of the prelink info. Also they
> could have all sorts of strange dependencies on symbols in the parent
> gimp executable.

That doesn't explain why one set of options doesn't crash (-fmv) while the 
other set of options (-amv) does. And after all, a program that segfaults has 
a bug in it.

Furthermore, I've exactly the same behaviour as Mr. Caleb. If I start prelink 
- -anv it crashes after reading libstdc++.so.5.0.2.

- -- 
Werner,-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+GEF/xiU3uL/NdUYRAoK0AJ4llTkDJpxRdpt9VdlHWLjLQIeFVQCfYfsc
TwRyyNsPgYj6ZYvzDBwdVJI=
=ehfH
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Stefan Jones]

On Sun, 2003-01-05 at 14:30, Werner Van Belle wrote:
> -----BEGIN PGP SIGNED MESSAGE-----

> That doesn't explain why one set of options doesn't crash (-fmv) while the 
> other set of options (-amv) does. And after all, a program that segfaults has 
> a bug in it.
> 
> Furthermore, I've exactly the same behaviour as Mr. Caleb. If I start prelink 
> - -anv it crashes after reading libstdc++.so.5.0.2.



I am not saying prelink isn't buggy btw.

The -f flag is needed if you have prelinked binaries already on the
system, otherwise it will abort, that is another matter.....

If you use -f you get around that problem, but you then encounter the
other one, you are between a rock and a hard place it seems.

( this is only an idea )


-- 
Stefan Jones <cretin@gentoo.org>
Gentoo Linux


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Dewet Diener]

Op Sun 05 Jan 03 16:41 skrewe Stefan Jones:
> If you use -f you get around that problem, but you then encounter
> the other one, you are between a rock and a hard place it seems.

After more poking around, I found that I have an older libstdc++ still lying around:

lrwxrwxrwx    1 root     root           18 Dec 17 00:32 libstdc++.so -> libstdc++.so.5.0.2
lrwxrwxrwx    1 root     root           18 Dec 17 00:32 libstdc++.so.5 -> libstdc++.so.5.0.2
-rwxr-xr-x    1 root     root      1077104 Nov 24 05:34 libstdc++.so.5.0.1
-rwxr-xr-x    1 root     root      1083538 Dec 17 00:31 libstdc++.so.5.0.2

5.0.1 prelinked without the segfault, and I got most everything depending on libstdc++ working fine by symlinking it to 5.0.1 instead of 5.0.2.  However, arts (and a whole lot of kde stuff) seems to be unhappy about that...

Dewet

-- 
Dewet Diener   <gentoo@dewet.org>   http://dewet.org
Professional Student, avid Gentoo user :)
Stellenbosch, South Africa (33º 55" 58.80'S  18º 51" 00.00'E)

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Bart Lauwers]

> I am not saying prelink isn't buggy BTW.
>
> The -f flag is needed if you have prelinked binaries already on the
> system, otherwise it will abort, that is another matter.....
>
> If you use -f you get around that problem, but you then encounter the
> other one, you are between a rock and a hard place it seems.

 I've found that the only way around the problem seems to be: prelink -ua, 
followed by a reboot and prelink -a. reboot. (with an occasional tendency to 
break things.)

 I've been wondering about the impact on portage however. Will portage know to 
unmerge these prelinked binaries still? My guess would be no.

 General remark: Prelinking definitely promises to be great but unless your 
willing to deal with some 'early adoption' quirks it isn't for you yet. I've 
broken my system once or twice severely trying to gauge it's state. I would 
say that some challenges remain before it is ready for the masses.


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Stefan Jones]

On Sun, 2003-01-05 at 15:17, Bart Lauwers wrote:
>  I've been wondering about the impact on portage however. Will portage know to 
> unmerge these prelinked binaries still? My guess would be no.
> 

Well the answer is yes, the portage changes are already in and working,
test it if you want. Portage integration is seamless .

>  General remark: Prelinking definitely promises to be great but unless your 
> willing to deal with some 'early adoption' quirks it isn't for you yet. I've 
> broken my system once or twice severely trying to gauge it's state. I would 
> say that some challenges remain before it is ready for the masses.
> 

The problem is that I have never had a single problem with it on three
computers (one of which being a sparc ). I can only fix errors I can
replicate.

-- 
Stefan Jones <cretin@gentoo.org>
Gentoo Linux


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Dewet Diener]

I'm also seeing the exact same behaviour:

Prelinking /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libgcc_s.so.1
open("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libgcc_s.so.1", O_RDONLY|O_LARGEFILE) = 3
open("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libgcc_s.so.1.#prelink#.4P92qy", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0600) = 4
--- SIGCHLD (Child exited) ---
stat64("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libgcc_s.so.1", {st_mode=S_IFREG|0644, st_size=43991, ...}) = 0
Prelinking /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2
open("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2", O_RDONLY|O_LARGEFILE) = 3
open("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2.#prelink#.Ikx2rU", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0600) = 4
--- SIGCHLD (Child exited) ---
stat64("/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2", {st_mode=S_IFREG|0755, st_size=1083538, ...}) = 0
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++
asara root #

The relevant bits of information:
asara root # emerge info
Portage 2.0.46-r4 (default-x86-1.4, gcc-3.2.1, glibc-2.3.1-r3)
=================================================================
System uname: 2.4.19-gentoo-r10 i686 AMD Duron(tm) Processor
USE="x86 3dnow apm avi crypt cups encode gif jpeg libg++ mmx mpeg ncurses nls pdflib png qtmt quicktime spell truetype xml2 xmms xv zlib directfb gtkhtml gdbm berkdb slang readline arts nas bonobo svga java guile ruby X sdl gpm tcpd pam libwww ssl python esd imlib oggvorbis gtk qt kde opengl scanner aalib alsa cdr dga dvd flash gd ggi -gnome gphoto2 imap innodb ldap mbox -mikmod -motif mozilla mysql -oss pda perl postgres samba snmp tcltk tetex tiff wmf freetype -apache2"
ARCH="x86"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=athlon-tbird -O2 -pipe -fomit-frame-pointer"
CXXFLAGS="-march=athlon-tbird -O2 -pipe -fomit-frame-pointer"
ACCEPT_KEYWORDS="x86 ~x86"
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/kde/3.1/share/config /usr/share/config"
CONFIG_PROTECT_MASK="/etc/init.d /etc/gconf /etc/env.d"
MAKEOPTS="-j2"
JDK_HOME="/opt/blackdown-jdk-1.4.1_beta"
JAVA_HOME="/opt/blackdown-jdk-1.4.1_beta"
AUTOCLEAN="no"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
GENTOO_MIRRORS="ftp://ftp.is.co.za/pub/linux/distributions/gentoo
        http://www.ibiblio.org/pub/Linux/distributions/gentoo"


-- 
Dewet Diener   <gentoo@dewet.org>   http://dewet.org
Professional Student, avid Gentoo user :)
Stellenbosch, South Africa (33º 55" 58.80'S  18º 51" 00.00'E)

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Terje Kvernes]

Caleb Shay <caleb@webninja.com> writes:

> And the culprit is...<drum roll please>..
> 
> /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.so.5.0.2
> 
> Bloody gcc.  I'll have to rebuild that again for something like the 5th
> time this week.  Bah!

  todays word of advice is to dump

FEATURES="buildpkg"
  
  into /etc/make.conf.

  as long as that is around, rebuilds are only needed if you change
  any relevant configuration options.

-- 
Terje

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Spider]

[-- Attachment #1: Type: text/plain, Size: 1782 bytes --]

I'm following up in this thread, some breakage :

Darkmere / # emerge -C divx4linux

 media-libs/divx4linux
    selected: 20020418 20020418-r1
   protected: none
     omitted: none

>>> Packages in red are slated for removal.
>>> Packages in green will not be removed.

>>> Waiting 5 seconds before starting...
>>> (Control-C to abort)...
>>> Unmerging in: 5 4 3 2 1 
>>> Unmerging media-libs/divx4linux-20020418...
No package files given... Grabbing a set.
--- !found obj /usr/share/doc/divx4linux-20020418/license.txt.gz
cp: copying multiple files, but last argument `/tmp/portage-prelink.tmp'
is not a directory
Try `cp --help' for more information.
Traceback (most recent call last):
  File "/usr/bin/emerge", line 1411, in ?
    if 1==unmerge(myaction, myfiles):
  File "/usr/bin/emerge", line 1123, in unmerge
    retval=portage.unmerge(mysplit[0],mysplit[1],portage.root)
  File "/usr/lib/python2.2/site-packages/portage.py", line 1517, in
unmerge
    mylink.unmerge()
  File "/usr/lib/python2.2/site-packages/portage.py", line 3532, in
unmerge
    mymd5=perform_md5(obj, calc_prelink=1)
  File "/usr/lib/python2.2/site-packages/portage.py", line 1505, in
perform_md5
    return perform_checksum(x, calc_prelink)[0]
  File "/usr/lib/python2.2/site-packages/portage.py", line 69, in
perform_checksum
    retval = fchksum.fmd5t(prelink_tmpfile)
IOError: [Errno 2] No such file or directory: '/tmp/portage-prelink.tmp'
Darkmere / # 


Darkmere / # emerge info
Portage 2.0.46-r4 (default-x86-1.4, gcc-3.2.1, glibc-2.3.1-r2)
=================================================================


Seems something is odd here..


//Spider

--
begin  .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Announcing new Prelinking Guide

[Viktor Lakics]

Variations with unmerge:

root lakicsok # emerge unmerge winex

 app-emulation/winex
     selected: 20020807-r1
    protected: none
     omitted: none

 >>> Packages in red are slated for removal.
 >>> Packages in green will not be removed.

 >>> Waiting 5 seconds before starting...
 >>> (Control-C to abort)...
 >>> Unmerging in: 5 4 3 2 1
 >>> Unmerging app-emulation/winex-20020807-r1...
 No package files given... Grabbing a set.
 --- !found obj /usr/share/man/man1/winex.1.g

 [Snip : almost done with unmerge]


--- !found obj
/usr/lib/winex/.data/fake_windows/Windows/System/.keep
cp: copying multiple files, but last argument
`/tmp/portage-prelink.tmp' is not a directory
Try `cp --help' for more information.
Traceback (most recent call last):
  File "/usr/bin/emerge", line 1411, in ?
      if 1==unmerge(myaction, myfiles):
    File "/usr/bin/emerge", line 1123, in unmerge
    retval=portage.unmerge(mysplit[0],mysplit[1],portage.root)
  File "/usr/lib/python2.2/site-packages/portage.py",
  line 1517, in unmerge
      mylink.unmerge()
    File
"/usr/lib/python2.2/site-packages/portage.py",
line 3532, in unmerge
    mymd5=perform_md5(obj, calc_prelink=1)
  File
  "/usr/lib/python2.2/site-packages/portage.py",
  line 1505, in perform_md5
      return perform_checksum(x,
  calc_prelink)[0]
    File
"/usr/lib/python2.2/site-packages/portage.py",
line 69, in perform_checksum
    retval =
fchksum.fmd5t(prelink_tmpfile)
IOError: [Errno 2] No such file
or directory:
'/tmp/portage-prelink.tmp'


Other package unmerging just fine...



On Tue, Jan 07, 2003 at 05:02:06AM +0100, Spider wrote:
> I'm following up in this thread, some breakage :
> 
> Darkmere / # emerge -C divx4linux
> 
>  media-libs/divx4linux
>     selected: 20020418 20020418-r1
>    protected: none
>      omitted: none
> 
> >>> Packages in red are slated for removal.
> >>> Packages in green will not be removed.
> 
> >>> Waiting 5 seconds before starting...
> >>> (Control-C to abort)...
> >>> Unmerging in: 5 4 3 2 1 
> >>> Unmerging media-libs/divx4linux-20020418...
> No package files given... Grabbing a set.
> --- !found obj /usr/share/doc/divx4linux-20020418/license.txt.gz
> cp: copying multiple files, but last argument `/tmp/portage-prelink.tmp'
> is not a directory
> Try `cp --help' for more information.
> Traceback (most recent call last):
>   File "/usr/bin/emerge", line 1411, in ?
>     if 1==unmerge(myaction, myfiles):
>   File "/usr/bin/emerge", line 1123, in unmerge
>     retval=portage.unmerge(mysplit[0],mysplit[1],portage.root)
>   File "/usr/lib/python2.2/site-packages/portage.py", line 1517, in
> unmerge
>     mylink.unmerge()
>   File "/usr/lib/python2.2/site-packages/portage.py", line 3532, in
> unmerge
>     mymd5=perform_md5(obj, calc_prelink=1)
>   File "/usr/lib/python2.2/site-packages/portage.py", line 1505, in
> perform_md5
>     return perform_checksum(x, calc_prelink)[0]
>   File "/usr/lib/python2.2/site-packages/portage.py", line 69, in
> perform_checksum
>     retval = fchksum.fmd5t(prelink_tmpfile)
> IOError: [Errno 2] No such file or directory: '/tmp/portage-prelink.tmp'
> Darkmere / # 
> 
> 
> Darkmere / # emerge info
> Portage 2.0.46-r4 (default-x86-1.4, gcc-3.2.1, glibc-2.3.1-r2)
> =================================================================
> 
> 
> Seems something is odd here..
> 
> 
> //Spider
> 
> --
> begin  .signature
> This is a .signature virus! Please copy me into your .signature!
> See Microsoft KB Article Q265230 for more information.
> end



-- 
_______________________________________
Viktor Lakics
email: viktor@lakics.net

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Announcing new Prelinking Guide

[Stefan Jones]

On Tue, 2003-01-07 at 07:01, Viktor Lakics wrote:
> Variations with unmerge:
> 
> root lakicsok # emerge unmerge winex
> 
>  app-emulation/winex
>      selected: 20020807-r1
>     protected: none
>      omitted: none
> 
>  >>> Packages in red are slated for removal.
>  >>> Packages in green will not be removed.
> 
>  >>> Waiting 5 seconds before starting...
>  >>> (Control-C to abort)...
>  >>> Unmerging in: 5 4 3 2 1
>  >>> Unmerging app-emulation/winex-20020807-r1...
>  No package files given... Grabbing a set.
>  --- !found obj /usr/share/man/man1/winex.1.g
> 
>  [Snip : almost done with unmerge]
> 
This is a missing quotes in the portage code, fixed in the newest portage


--
gentoo-dev@gentoo.org mailing list