LD_LIBRARY_PATH and GCC

2007-08-21 Thread Jason Curl
Hello, Since migrating over to 'libtool' with automake to compile my packages, on Solaris 9 and 10 we're now getting the new error: ld.so.1: /home/user/myprog: fatal: libgcc_s.so.1: open failed: No such file or directory Killed Before using libtool and using convenience libraries only, this

Re: Shared libraries build on Linux, not on Solaris 10 (gcc)

2007-08-21 Thread Jason Curl
Ralf Wildenhues wrote: * Jason Curl wrote on Fri, Aug 17, 2007 at 12:05:44AM CEST: I've just switched over to using libtool instead of using static libraries. I've installed autoconf-2.61, automake-1.10 and libtool-1.5.24. The library builds fine under Linux, but won't link under Solaris Sp

Re: LD_LIBRARY_PATH and GCC

2007-08-21 Thread Mike Frysinger
On Tuesday 21 August 2007, Jason Curl wrote: > ld.so.1: /home/user/myprog: fatal: libgcc_s.so.1: open failed: No such > file or directory > Killed the distribution should be taking care of making sure libgcc_s.so.1 is readily available (or not needed). this is an internal gcc library and has no

multilib dirs and ld.so

2007-08-21 Thread Peter O'Gorman
Hi, Albert pointed out to me yesterday that while, with 1.5.24 we now add the correct directories to sys_lib_search_path_spec, they do not get added to sys_lib_dlsearch_path_spec, resulting in libtool putting, for example, /usr/lib64 in RPATH. Red Hat have a patch for this, but it is specific to r

Re: LD_LIBRARY_PATH and GCC

2007-08-21 Thread Bob Friesenhahn
On Tue, 21 Aug 2007, Jason Curl wrote: Hello, Since migrating over to 'libtool' with automake to compile my packages, on Solaris 9 and 10 we're now getting the new error: ld.so.1: /home/user/myprog: fatal: libgcc_s.so.1: open failed: No such file or directory Killed [ stuff removed ] As

Re: Shared libraries build on Linux, not on Solaris 10 (gcc)

2007-08-21 Thread Jason Curl
Jason Curl wrote: Ralf Wildenhues wrote: * Jason Curl wrote on Fri, Aug 17, 2007 at 12:05:44AM CEST: I've just switched over to using libtool instead of using static libraries. I've installed autoconf-2.61, automake-1.10 and libtool-1.5.24. The library builds fine under Linux, but won't li

Re: Creating ONLY static libraries

2007-08-21 Thread Jason Curl
Omri Azencot wrote: Hello I am using libtool 1.5.23 during the building process, I am also using autoconf(2.61) to create the configure file. in configure.ac I used the macro AC_DISABLE_SHARED, and in the log I got the following line: checking whether to build shared libraries... no but, after

AC_PROG_LIBTOOL sets CFLAGS

2007-08-21 Thread Thien-Thi Nguyen
according to my reading of info nodes: (libtool) AC_PROG_LIBTOOL (automake) Flag Variables Ordering the shell variable CFLAGS should have no value after AC_PROG_LIBTOOL. i.e., i should expect the configure.ac fragment: echo "CFLAGS: $CFLAGS" AC_PROG_LIBTOOL echo "CFLAGS: $CFLAGS" to create

Re: AC_PROG_LIBTOOL sets CFLAGS

2007-08-21 Thread Peter O'Gorman
On Tue, 2007-08-21 at 21:49 +0200, Thien-Thi Nguyen wrote: > according to my reading of info nodes: > > (libtool) AC_PROG_LIBTOOL > (automake) Flag Variables Ordering > > the shell variable CFLAGS should have no value after AC_PROG_LIBTOOL. > i.e., i should expect the configure.ac fragment: >

Re: Creating ONLY static libraries

2007-08-21 Thread Omri Azencot
On 8/21/07, Jason Curl <[EMAIL PROTECTED]> wrote: > > >If you don't need to have the libraries installed for a convenience > >library, use "noinst_*". See: > >http://www.gnu.org/software/automake/manual/automake.html#A-Library > > > >Similarly for libtool: > >http://www.gnu.org/software/libtool/man