Is there any reason to provide symlinks for any libraries other that librexx.so and librexxapi.so? I can't think of any reason why the other libraries need to be available to developers or dlopen. But I might be missing something.
David Ashley On 10/19/2010 10:15 PM, Mark Miesfeld wrote: > On Tue, Oct 19, 2010 at 6:06 PM, Mark Miesfeld<[email protected]> wrote: > >> 1.) The dlopen test fails under 4.1.0 from trunk and works with the >> released 4.0.1, on Fedora Core 13 64-bit >> >> 2.) Building the external binaries for the test suite fails under >> 4.1.0 from trunk and works with the released 4.0.1 > Both of these problems are fixed by creating symlinks in /usr/lib64 to > the the libraries in /usr/lib64/ooRexx. > > Creating the file: /etc/ld.so.conf.d/ooRexx.conf with contents of: > /usr/lib64/ooRexx fixes the dlopen problem, but not the build problem > in the test suite. > > -- > Mark Miesfeld > > ------------------------------------------------------------------------------ > 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
