tall target
subsequently follows up with an:
lockf /tmp/${lockfile} rsync -a ${sandbox}/ ${deployment_dir}/
To perform the actual placement of the installed files safely in the
shared deployment directory, which would be used for building the
package.
Both the .la files and the .pc files
es, I often need to add -no-undefined to
LDFLAGS, as well, or else libtool only generates static libs.
--
Coleman Kane
___
http://lists.gnu.org/mailman/listinfo/libtool
ct-v20z-13 2.6.5-7.308-smp #1 SMP Mon Dec 10 11:36:40 UTC 2007
> x86_64 x86_64 x86_64 GNU/Linux
> $ cat /etc/SuSE-release
> SUSE LINUX Enterprise Server 9 (x86_64)
> VERSION = 9
> PATCHLEVEL = 4
>
> Is this a bug?
>
> -Ethan
>
--
Coleman Kane
___
http://lists.gnu.org/mailman/listinfo/libtool
On Thu, 2009-03-12 at 19:54 +0100, Ralf Wildenhues wrote:
> Hello Coleman,
>
> * Coleman Kane wrote on Thu, Mar 12, 2009 at 07:22:31PM CET:
> >
> > Libtool doesn't perform much low-level investigation of the library file
> > types, nor does it rewrite pat
lding a shared library automatically hardcodes DIR
> # into the library and all subsequent libraries and executables linked
> # against it.
> hardcode_automatic=no
>
> # Set to yes if linker adds runtime paths of dependent libraries
> # to runtime path list.
> inherit_rpath=no
>
> # Whether libtool must link a program against all its dependency libraries.
> link_all_deplibs=unknown
>
> # Fix the shell variable $srcfile for the compiler.
> fix_srcfile_path=""
>
> # Set to "yes" if exported symbols are required.
> always_export_symbols=no
>
> # The commands to list exported symbols.
> export_symbols_cmds="\$NM \$libobjs \$convenience | \$global_symbol_pipe |
> \$SED 's/.* //' | sort | uniq > \$export_symbols"
>
> # Symbols that should not be listed in the preloaded symbols.
> exclude_expsyms="_GLOBAL_OFFSET_TABLE_|_GLOBAL__F[ID]_.*"
>
> # Symbols that must always be exported.
> include_expsyms=""
>
> # Commands necessary for linking programs (against libraries) with templates.
> prelink_cmds=""
>
> # Specify filename containing input files.
> file_list_spec=""
>
> # How to hardcode a shared library path into an executable.
> hardcode_action=immediate
>
> # The directories searched by this compiler when creating a shared library.
> compiler_lib_search_dirs="/ws/ompi-tools/pathscale/3.2/lib/3.2/32"
>
> # Dependencies to place before and after the objects being linked to
> # create a shared library.
> predep_objects=""
> postdep_objects="/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../lib/crti.o
> /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/32/crtbeginS.o
> /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/32/crtendS.o
> /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../lib/crtn.o"
> predeps=""
> postdeps="-lpthread -lpscrt -lmv -lmpath
> -L/ws/ompi-tools/pathscale/3.2/lib/3.2/32
> -L/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/32
> -L/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3
> -L/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../x86_64-suse-linux/lib/../lib
>
> -L/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../x86_64-suse-linux/lib
> -L/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../lib
> -L/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../.. -L/lib/../lib
> -L/usr/lib/../lib -lpthread -lpscrt -lmv -lmpath -lstdc++ -lm -lgcc_s_32 -lc
> -lgcc_s_32"
>
> # The library search path used internally by the compiler when linking
> # a shared library.
> compiler_lib_search_path="-L/ws/ompi-tools/pathscale/3.2/lib/3.2/32"
>
> # ### END LIBTOOL TAG CONFIG: CXX
> em162155 $ ../../../libtool --version
> ltmain.sh (GNU libtool) 2.2.6
> Written by Gordon Matzigkeit , 1996
>
> Copyright (C) 2008 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> em162155 $ ls -ld /lib* /usr/lib*
> drwxr-xr-x 12 root root 4096 2008-05-19 12:22 /lib
> drwxr-xr-x 5 root root 4096 2008-05-19 12:23 /lib64
> drwxr-xr-x 55 root root 16384 2008-11-06 13:11 /usr/lib
> drwxr-xr-x 69 root root 28672 2008-07-17 13:27 /usr/lib64
>
> >
> > I wonder: if you do the build with g++, then GNU ld will probably just
> > skip over the wrong libstdc++ and keep searching until it finds the 32
> > bit one later in the search path, right?
> >
> > Can you work around the issue by adding -L/usr/lib32 early in LDFLAGS?
> >
>
> I'll give that a try.
>
> -Ethan
>
>
> > Thanks,
> > Ralf
It thinks your host system is "x86_64-unknown-linux-gnu".
Maybe you need --host=i386-unknown-linux-gnu in your configure args?
--
Coleman Kane
___
http://lists.gnu.org/mailman/listinfo/libtool
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:49:02PM, Ralf Wildenhues wrote:
> > > > Hello Ethan,
> > >
