[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: -soname passed directly to the compiler
From: |
tom fogal |
Subject: |
Re: -soname passed directly to the compiler |
Date: |
Tue, 15 Feb 2011 10:34:44 -0700 |
Hi, sorry for the slow response.
Ralf Wildenhues <address@hidden> writes:
> * tom fogal wrote on Sun, Feb 13, 2011 at 10:23:30PM CET:
> > A package we're converting to the autotools is having an issue
> > building a library; it seems to think gcc supports a -soname
> > option.
> >
> > /bin/sh ../libtool --tag=CC --mode=link mpicc -I/home/tfogal/sw/includ
> e
> > -L/home/tfogal/sw/lib -o libH5Part.la -rpath
> > /home/tfogal/dev/install-h5part/lib H5Part.lo H5PartAttrib.lo H5Block.lo
> > H5BlockReadWrite.lo H5MultiBlock.lo H5MultiBlockReadWrite.lo -lhdf5
> > mpicc -shared .libs/H5Part.o .libs/H5PartAttrib.o .libs/H5Block.o
> > .libs/H5BlockReadWrite.o .libs/H5MultiBlock.o .libs/H5MultiBlockReadWrite
> .o
> > -L/home/tfogal/sw/lib /home/tfogal/shigeru/lib/libhdf5.a -lc -soname
> > libH5Part.so.0 -o .libs/libH5Part.so.0.0.0
> > gcc: libH5Part.so.0: No such file or directory
> > gcc: unrecognized option '-soname'
>
> > ltmain.sh (GNU libtool) 1.5.26 Debian 1.5.26-4+lenny1 (1.1220.2.493 2008/02
> /01
> > 16:58:18)
>
> Hmm, even libtool 1.5.26 should be detecting mpicc as gcc but
> apparently it isn't. You could look in config.log to find out why.
> I'd really really suggest using a newer Libtool though [. . .]
Just wanted to follow up for the archives. I upgraded libtool but hit
lots of strange issues. Ended up upgrading both autoconf and automake
too, which of course were also a few years old.
I was still hitting issues, now with libtool trying to execute "X--gcc"
or something like that; it seemed to be a common problem, from google
searches, yet nobody had a concrete answer. I'm afraid I don't either:
my solution was to stash my current changes and `git clean -df'. I
don't version control configure, aclocal.m4, config.* etc., and so this
got me a virgin tree.
At that point 'libtoolize --copy --force && autoreconf -vi' got me a
working build system. There must have been some sort of state which
was not getting overwritten from the above w/o cleaning out the whole
tree, but I do not know what it was, exactly.
HTH someone finding this thread,
-tom