Unwanted shared runtime libraries getting added

Hello, I'm trying to create a library which has no shared library dependencies using the Intel compilers, but it appears Libtool might be automatically adding in some -lfoo flags that are forcing the issue. How can I tell Libtool to not add the -lfoo flags? -Ethan __

Re: Unwanted shared runtime libraries getting added

On Fri, Oct/08/2010 07:14:18PM, Ralf Wildenhues wrote: > Hello Ethan, > > * Ethan Mallove wrote on Fri, Oct 08, 2010 at 02:42:53PM CEST: > > I'm trying to create a library which has no shared library > > dependencies using the Intel compilers, but it appears Libtool

Re: Unwanted shared runtime libraries getting added

On Fri, Oct/08/2010 07:50:39PM, Ralf Wildenhues wrote: > * Ethan Mallove wrote on Fri, Oct 08, 2010 at 07:26:45PM CEST: > > On Fri, Oct/08/2010 07:14:18PM, Ralf Wildenhues wrote: > > > * Ethan Mallove wrote on Fri, Oct 08, 2010 at 02:42:53PM CEST: > > > > I'm t

Re: Unwanted shared runtime libraries getting added

l -lc -m32 -pthread -pthread -Wl,-soname -Wl,libmpi_cxx.so.0 -o .libs/libmpi_cxx.so.0.0.0 -Ethan > >On Fri, Oct 8, 2010 at 1:22 PM, Ethan Mallove >wrote: > > On Fri, Oct/08/2010 07:50:39PM, Ralf Wildenhues wrote: > > * Ethan Mallove wrote on Fri, Oct

Re: Unwanted shared runtime libraries getting added

On Mon, Oct/11/2010 07:51:20PM, Ralf Wildenhues wrote: > Hello Ethan, > > * Ethan Mallove wrote on Mon, Oct 11, 2010 at 01:59:20PM CEST: > > On Fri, Oct/08/2010 02:24:26PM, Robert Boehne wrote: > > >I think the mode=compile line doesn't tell us much a

Re: Unwanted shared runtime libraries getting added

On Mon, Oct/11/2010 09:01:56PM, Ralf Wildenhues wrote: > * Ethan Mallove wrote on Mon, Oct 11, 2010 at 08:11:19PM CEST: > > On Mon, Oct/11/2010 07:51:20PM, Ralf Wildenhues wrote: > > > * Ethan Mallove wrote on Mon, Oct 11, 2010 at 01:59:20PM CEST: > > > > $ /bin/

Re: Unwanted shared runtime libraries getting added

On Sat, Oct/16/2010 10:32:13AM, Ralf Wildenhues wrote: > * Ethan Mallove wrote on Fri, Oct 15, 2010 at 08:59:38PM CEST: > > On Mon, Oct/11/2010 09:01:56PM, Ralf Wildenhues wrote: > [...] > > > > > > This doesn't have the libraries you don't want, AFAICS

Re: Unwanted shared runtime libraries getting added

On Mon, Oct/18/2010 02:40:32PM, Ethan Mallove wrote: > On Sat, Oct/16/2010 10:32:13AM, Ralf Wildenhues wrote: > > * Ethan Mallove wrote on Fri, Oct 15, 2010 at 08:59:38PM CEST: > > > On Mon, Oct/11/2010 09:01:56PM, Ralf Wildenhues wrote: > > [...] > > > > >

Libtool can't find libgcc_s

Hi, Libtool seems to get confused about where libgcc_s is, e.g., $ /bin/sh ../../../libtool --tag=CXX --mode=link icpc -lgcc_s foo.c -o a.out libtool: link: icpc foo.c -o a.out -lgcc_s ld: skipping incompatible /usr/lib/gcc/x86_64-redhat-linux/3.4.6//libgcc_s.so when searching for -lgcc

Re: Libtool can't find libgcc_s

On Wed, Nov/10/2010 07:59:38PM, Ralf Wildenhues wrote: > Hello Ethan, > > * ethan.mall...@oracle.com wrote on Wed, Nov 10, 2010 at 07:48:14PM CET: > > Libtool seems to get confused about where libgcc_s is, e.g., > > > > $ /bin/sh ../../../libtool --tag=CXX --mode=link icpc -lgcc_s foo.c -o >

Re: Unwanted shared runtime libraries getting added

On Thu, Oct/21/2010 06:13:03AM, Ralf Wildenhues wrote: > Hello Ethan, > > * Ethan Mallove wrote on Wed, Oct 20, 2010 at 10:32:11PM CEST: > > > It looks like that gives us the link line we want, yet we still get the > > > libimf.so dependency: > > > >

1 compiler (called from 2 symbolic links) -> 2 different libtool scripts

Hello, I'm using libtool with the Sun Studio Ceres compilers, and I see a different resulting libtool script when I configure with CC=sunCC versus CC=cc (though they both point to the same executable). The Sun Studio installation has the below symbolic links: $ ls -l /opt/SUNWspro/bin/*CC l

Re: 1 compiler (called from 2 symbolic links) -> 2 different libtool scripts

On Thu, Jul/24/2008 04:43:08PM, Andreas F?rber wrote: > Hello, > > Am 24.07.2008 um 16:31 schrieb Ethan Mallove: > >> I'm using libtool with the Sun Studio Ceres compilers, and I >> see a different resulting libtool script when I configure >> with CC=sunCC vers

Re: 1 compiler (called from 2 symbolic links) -> 2 different libtool scripts

On Thu, Jul/24/2008 09:51:20AM, Peter O'Gorman wrote: > Ethan Mallove wrote: > > Hello, > > > > I'm using libtool with the Sun Studio Ceres compilers, and I > > see a different resulting libtool script when I configure > > with CC=sunCC versus CC

Re: 1 compiler (called from 2 symbolic links) -> 2 different libtool scripts

On Mon, Aug/04/2008 10:06:59PM, Ralf Wildenhues wrote: > * Ethan Mallove wrote on Thu, Jul 24, 2008 at 06:17:05PM CEST: > > On Thu, Jul/24/2008 09:51:20AM, Peter O'Gorman wrote: > > > Ethan Mallove wrote: > > > > Is it possible the libtool macros do things

$ORIGIN support for Libtool

Hi, I am using the run-time linker $ORIGIN variable with Libtool in an apparently unsupported way to create relocatable objects. After Libtool generates a "libtool" script, I am commenting out the below lines: func_fatal_help "\`$destdir' must be an absolute directory name" func_fatal_error "on

Libtool attempts to link 64-bit lib on a -m32 compile (using Pathscale C++)

Hello, Libtool is trying to link in 64-bit libs on a -m32 compile with the Pathscale C++ compiler. E.g., /bin/sh ../../../libtool --tag=CXX --mode=link pathCC -O3 -DNDEBUG -Wall -m32 -Wundef -Wno-long-long -finline-functions -fexceptions -pthread -export-dynamic -fexceptions -o libmpi_

Re: Libtool attempts to link 64-bit lib on a -m32 compile (using Pathscale C++)

On Thu, Mar/12/2009 07:49:02PM, Ralf Wildenhues wrote: > Hello Ethan, > > * Ethan Mallove wrote on Thu, Mar 12, 2009 at 05:25:50PM CET: > > Libtool is trying to link in 64-bit libs on a -m32 compile with the > > Pathscale C++ compiler. E.g., > > > > /bin/sh ..

Re: Libtool attempts to link 64-bit lib on a -m32 compile (using Pathscale C++)

On Fri, Mar/13/2009 03:24:17PM, Coleman Kane wrote: > On Fri, 2009-03-13 at 13:11 -0500, Ethan Mallove wrote: > > On Thu, Mar/12/2009 07:49:02PM, Ralf Wildenhues wrote: > > > Hello Ethan, > > > > > > * Ethan Mallove wrote on Thu, Mar 12, 2009 at 05:25:50PM CE

Re: Libtool attempts to link 64-bit lib on a -m32 compile (using Pathscale C++)

On Fri, Mar/13/2009 03:59:04PM, Coleman Kane wrote: > On Fri, 2009-03-13 at 14:44 -0500, Ethan Mallove wrote: > > On Fri, Mar/13/2009 03:24:17PM, Coleman Kane wrote: > > > On Fri, 2009-03-13 at 13:11 -0500, Ethan Mallove wrote: > > > > On Thu, Mar/12/2009 07:

Libtool strips out -tp=k8-32 PGI compiler flag in link mode

Hello, I am trying to use Libtool with the PGI compilers in 32-bit mode (using the -tp=k8-32 flag). In link mode, Libtool seems to be stripping out the -tp=k8-32 compiler flag, which results in a compiler error: $ make /bin/sh ../../../../libtool --tag=CC --mode=link pgcc -O -DNDEBUG -tp=k8-3

Re: Libtool strips out -tp=k8-32 PGI compiler flag in link mode

GS seems to do the trick, e.g., $ make AM_CFLAGS='-Wc,-tp=k8-32' > > Cheers, > Ralf > > Allow through -tp=* at link time, for pgcc. > > * libltdl/config/ltmain.m4sh (func_mode_link): Portlant Group > pgcc uses `-tp=PROCESSOR' for target pro

Re: Libtool strips out -tp=k8-32 PGI compiler flag in link mode

; > Allow through -tp=* at link time, for pgcc. > > > > * libltdl/config/ltmain.m4sh (func_mode_link): Portlant Group > > pgcc uses `-tp=PROCESSOR' for target processor selection; allow > > the flag through at link time. > > Report by Ethan Mallove.

Re: Libtool attempts to link 64-bit lib on a -m32 compile (using Pathscale C++)

I'm running into a similar problem, but the -L/usr/lib workaround doesn't help in this case. Same pathCC, but on SuSE 10 (not SuSE 9). The error is basically this: $ make ... libtool: link: pathCC ... -lpscrt /usr/lib64/gcc/x86_64-suse-linux/4.1.2/libstdc++.so -m32 ... /usr/lib64/gcc/x86_