* Ethan Mallove wrote on Fri, Dec 10, 2010 at 07:41:20PM CET:
> On Thu, Oct/21/2010 06:13:03AM, Ralf Wildenhues wrote:
> > Pass -Wc,-static-intel instead.
>
> This works like a charm for shared libraries, but for standalone
> executables I get an error like this:
>
> ...
> icc: command line w
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:
> > >
> > > $ /bin/sh ../../../libtool --tag=CC --mo
Hi Ethan,
Den 2010-11-08 21:39 skrev Ethan A Mallove:
> On 10/21/10 00:13, 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:
$
On 10/21/10 00:13, 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:
$ /bin/sh ../../../libtool --tag=CC --mode=link icpc -O3 -DNDEBUG -Wall -static
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:
> >
> > $ /bin/sh ../../../libtool --tag=CC --mode=link icpc -O3 -DNDEBUG -Wall
> > -static-intel -m64 -finline-fun
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:
> > [...]
> > > >
> > > > This doesn't have the libraries yo
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. So a workaround
> > > (using internal deta
* 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. So a workaround
> > (using internal details, but fairly safe) would be to use
> > libmpi_cxx_la_LIBTOOLFL
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/sh ../../../libtool --tag=CXX --m
* 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/sh ../../../libtool --tag=CXX --mode=link icpc -O3 -DNDEBUG
> > > -Wall -static-intel -m32 -fi
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 about what happens
> > > when
> > >mode
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 about what happens
> > when
> >mode=link - post what you get on the "libtool --mode=link" command.
>
>
On Fri, Oct/08/2010 02:24:26PM, Robert Boehne wrote:
>I think the mode=compile line doesn't tell us much about what happens when
>mode=link - post what you get on the "libtool --mode=link" command.
$ /bin/sh ../../../libtool --tag=CXX --mode=link icpc -O3 -DNDEBUG -Wall
-static-intel
I think the mode=compile line doesn't tell us much about what happens when
mode=link - post what you get on the "libtool --mode=link" command.
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 08, 20
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 trying to create a library which has no
* 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 trying to create a library which has no shared library
> > > dependencies using the Intel compilers, b
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 might
> > be automatically addi
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 might
> be automatically adding in some -lfoo flags that are forcing the
> issue. How can I tel
On Fri, Oct 08, 2010 at 08:42:53AM -0400, Ethan Mallove wrote:
> 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
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
__
20 matches
Mail list logo
