Ok, I have to admit that I don't exactly know how this works, but it does.
I am running Fedora 13 x86_64. The ooRexx libraries are installesion /usr/lib64/ooRexx. ldconfig was run during the rpm install with no command line options. The cache file for ldconfig does NOT contain any reference to ooRexx shared libraries and there are no links from /usr/lib64/ooRexx to /usr/lib64 or /usr/lib. But everything still seems to work. ooRexx runs just fine and I can build auxiliary shared libraries that link to the ooRexx libraries just fine. But I did find something related to this that might shed some light on why this is working. There are a LOT of subdirectories in /usr/lib64, maybe as many as 50 or 60. Practically none of the shared libraries in those subdirectories are listed in the ldconfig cache file. And all the applications for those shared libraries also seem to work. So there must be some other mechanism at work here that we are not aware of. I will do some more research to see if I can figure this out. BTW - it bothers me that no one seems to have done any testing of the rpm builds I have been doing except me. It make me wonder why I am going to all this work. David Ashley On 10/19/2010 12:15 PM, Erico Mendonca wrote: >>>> On 10/19/2010 at 01:31 PM, in message > <[email protected]>, Mark Miesfeld > <[email protected]> wrote: >>> No, they do not. In the postinstall section of the RPM spec file we run >>> ldconfig after all the files have been installed. ldconfig is smart enough >> to >>> look in all the subdirs of /usr/lib and put them in the library search path >> as >>> well. >> >> That doesn't seem to be the case though. I thought that ldconfig >> might do that, but it doesn't seem to do that. >> >> Fedora Core 13 64-bit specifically didn't work. But, I only did a >> quick test, maybe there was some other reason the interpreter wouldn't >> run. >> >> Doing a Google search also seemed to point to the conclusion that >> symbolic links needed to be created. I started with debian >> documentation though, where the writers seem to be adverse to stating >> things simply.<grin> > I don't have a Fedora machine at hand, but the behaviour should be the same > on all modern Linuxes. > > The problem is, you still need to tell ldconfig the "extra paths" to scan. It > only scans /usr/lib and /lib by default. Just create a file at > /etc/ld.so.conf.d containing the extra path. > > For example, create "/etc/ld.so.conf.d/oorexx" containing the following line: > > /usr/lib/ooRexx > > run "ldconfig" to re-create the library cache and you're done. You can check > if it worked by issuing "ldconfig -p | grep rexx". > > There should be no need to create symlinks manually. > > > > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------------ Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
