How to ignore dependency_libs? (Was: Libtool adding libraries differently than needed with compiler wrappers)

libraries. Is there a way to tell libtool to ignore dependency_libs value in the .la files of any libraries that are linked in? Thx.John Cary On Fri, 22 Apr 2011, John R. Cary wrote: We have a project using libtool on a Cray-XT4 using pathscale. For compiling in parallel, we are supposed to use

Re: Libtool adding libraries differently than neededwith compilerwrappers

-lstdc++, then I get clean compile ( no multiple inclusion warning). I do not know how to configure libtool to remove it by itself. This may be your issue as well. Thanks, Nitin. -Original Message- From: libtool-bounces+nkapoor=sensis@gnu.org [mailto:libtool-bounces+nkapoor=sen

Re: Libtool adding libraries differently than needed with compilerwrappers

@gnu.org [mailto:libtool-bounces+nkapoor=sensis@gnu.org] On Behalf Of John R. Cary Sent: Friday, April 22, 2011 9:17 AM To: libtool@gnu.org Subject: Libtool adding libraries differently than needed with compilerwrappers We have a project using libtool on a Cray-XT4 using pathscale. For compiling in

Libtool adding libraries differently than needed with compiler wrappers

We have a project using libtool on a Cray-XT4 using pathscale. For compiling in parallel, we are supposed to use the compiler wrapper, in this case ftn, that adds various libraries. A particular complexity is that one has to switch libraries between front and back end nodes, and this is done with

Re: Problem with libtool adding -pthread

On 11/28/10 10:25 AM, Ralf Wildenhues wrote: Hello John, * John R. Cary wrote on Sun, Nov 28, 2010 at 03:02:48PM CET: I am tring to link with libtool using the compiler wrappers on a Cray and with pgi. At final link, libtool inserts the flag, -pthread, which causes the compiler to fail. This

Re: Problem with libtool adding -pthread

System information below On 11/28/10 7:02 AM, John R. Cary wrote: I am trying to link with libtool using the compiler wrappers on a Cray and with pgi. At final link, libtool inserts the flag, -pthread, which causes the compiler to fail. This is shown below. Is there some way around this

Problem with libtool adding -pthread

I am tring to link with libtool using the compiler wrappers on a Cray and with pgi. At final link, libtool inserts the flag, -pthread, which causes the compiler to fail. This is shown below. Is there some way around this? Also, while the original link line contains -L/opt/fftw/3.2.2/lib -lfft

Re: Disabling library dependency tracking?

postdep_objects=.*$/postdep_objects=/g" -e "s/link_all_deplibs=.*$/link_all_deplibs=no/g" libtool.2; sed -e "s?-L/opt/fftw/3.2.1/lib??g" -e "s?/opt/fftw/3.2.1/lib??g" libtool; ;; esac rm -f libtool.1 libtool.2; ] ) Happy holidays to all! Joh

Disabling library dependency tracking?

I see lots of traffic on this subject, but I do not know how to solve my particular situation. On the Cray XT4 we use compiler wrappers to handle to cross-compile situation, where one cannot have static libs on the back-end nodes. My understanding is that the wrapper takes care of the need for m

Re: rpath in later versions of libtool (fwd)

I forgot to cc the listJohn Cary -- Tech-X Corp., 5621 Arapahoe Ave, Suite A, Boulder CO 80303 c...@txcorp.com, p 303-448-0727, f 303-448-7756 -- Forwarded message -- Date: Sat, 08 Aug 2009 15:14:54 -0600 From: John R. Cary To: Bob Friesenhahn Subject: Re: rpath in later

rpath in later versions of libtool

I am running: iter.cary$ autoconf --version; automake --version; libtool --version autoconf (GNU Autoconf) 2.63 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv2+: GNU GPL version 2 or later This is free software: you are free to c

LD_RUN_PATH and openmpi's mpicxx

libtool uses LD_RUN_PATH on Linux to pass the runtime link dirs. Unfortunately, OpenMPI's mpicxx ignores the envvar, does not pass it through to g++. Is there a way around this on the libtool end? E.g., some way of forcing use of -Wl,-rpath? ThxJohn Cary -- Tech-X Corp., 5621 Arapahoe Ave

Re: Fortran libraries on the Blue Gene with mpi

Ralf Wildenhues wrote: login5.intrepid$ ./config.guess ./config.guess: unable to guess system type [...] config.guess timestamp = 2009-02-03 uname -m = 4400 uname -r = 4.0 uname -s = iainfo2 uname -v = 3.0 /bin/arch = ppc64 UNAME_MACHINE = 4400 UNAME_

Re: Fortran libraries on the Blue Gene with mpi

Hi Ralf, Ralf Wildenhues wrote: Hello John, OK. That's fairly easy to support in Libtool then: the only thing we need to get right is to turn off shared library support completely for BG/L. I gave the wrong impression. This is a BG/P. My previous reference to the compilers was bec

Re: Fortran libraries on the Blue Gene with mpi

Ralf Wildenhues wrote: Hello John, * John R. Cary wrote on Mon, Apr 13, 2009 at 10:19:49PM CEST: I am trying to link some Fortran code on the Blue Gene (P) using the xl compilers. Probably Libtool needs to be ported fully to this system first, or, just the name matching be adjusted

Fortran libraries on the Blue Gene with mpi

I am trying to link some Fortran code on the Blue Gene (P) using the xl compilers. My configure script uses AC_PROG_LIBTOOL and within that script I see checking for Fortran libraries of mpixlf95_r... -L/opt/ibmcmp/xlsmp/bg/1.7/bglib -L/opt/ibmcmp/xlmass/bg/4.4/bglib -L/opt/ibmcmp/xlf/bg/11

Re: Now --tag=F77 has disappeared

Hi Ralf, You minimal example works. I will review our setup and see what I missed. Thanks...John Ralf Wildenhues wrote: [ adding bug-automake ] Hello John, * John R. Cary wrote on Wed, Mar 25, 2009 at 05:07:17PM CET: Thanks, Ralf, for your latest patch. I applied this to automake

Now --tag=F77 has disappeared

Thanks, Ralf, for your latest patch. I applied this to automake-1.10.2. Now --tag=FC shows up for FC code, but there is no tag for F77 (.F, .f) code. The F77 stanza looks analogous to the FC stanza, so not sure what is happening. Perhaps only when a directory has bot F77 and FC code? Not su

Re: How to use compiler wrappers

. Thanks...John Ralf Wildenhues wrote: Hello John, * John R. Cary wrote on Sun, Mar 22, 2009 at 04:50:20PM CET: I am in a situation where due to flakey compilers (pgi) I had to write a compiler wrapper such that if code does not compile, I reduce the optimization level, then try again. My way

How to use compiler wrappers

I am in a situation where due to flakey compilers (pgi) I had to write a compiler wrapper such that if code does not compile, I reduce the optimization level, then try again. My way of dealing with this is to create a compiler wrapper as a wrapper.sh.in file with c...@cc@ and so forth so that a