On Wed, 21 May 2003, Matthew T. O'Connor wrote: > > I decided to play with prelink and see if/how much it helps. > > > > >From the list here, I saw that people were just running it on RH9 with > > the command: prelink -aRv so I tried it and got the following: > > > > [root@xxxxxxx lib]# prelink -aRv > > prelink: /usr/lib/libaio.so.1: Library without dependencies > > prelink: /usr/bin/vmnet-natd: Could not parse `Incorrectly built binary > > which accesses errno, h_errno or _res directly. Needs to be fixed.' > > prelink: /usr/bin/vmware-wizard: Could not parse `Incorrectly built > > binary which accesses errno, h_errno or _res directly. Needs to be > > fixed.' > > prelink: /usr/lib/openoffice/program/pkgchk.bin: Could not parse > > `/usr/lib/openoffice/program/pkgchk.bin: error while loading shared > > libraries: libsal.so.3: cannot open shared object file: No such file or > > directory' > > prelink: /usr/lib/openoffice/program/libspa641li.so: Dependency tracing > > failed > > Laying out 671 libraries in virtual address space 41000000-50000000 > > prelink: Could not find virtual address slot for /usr/lib/kfmclient.so You always seem to get some errors, usually indicating files that can't be prelinked. They normally don't matter, but maybe the last one is fatal. You could try unprelinking first, or without using the -R flag to see if you get better results. > > Which didn't look good so to see if anything happened: > > > > [root@xxxxxxx lib]# prelink -p > > 0 objects found in prelink cache `/etc/prelink.cache' I get lots of output here! Michael Young
