* Steffen Dettmer wrote on Mon, Jan 25, 2010 at 12:06:11PM CET:
> On Mon, Jan 25, 2010 at 8:25 AM, Murray S. Kucherawy wrote:
> > I've got a package that first builds a library and then a
> > binary that links to the library. The binary build references
> > it via:
> >
> > progname_LIBADD = ../lib
On Mon, 25 Jan 2010, Murray S. Kucherawy wrote:
The resulting gcc command:
gcc -std=gnu99 -pthread -I/usr/include -g -O2 -pthread -o .libs/opendkim
opendkim-opendkim.o opendkim-opendkim-ar.o opendkim-opendkim-arf.o
opendkim-opendkim-crypto.o opendkim-opendkim-db.o opendkim-opendkim-lua.o
ope
> -Original Message-
> From: Bob Friesenhahn [mailto:bfrie...@simple.dallas.tx.us]
> Sent: Monday, January 25, 2010 10:37 AM
> To: Murray S. Kucherawy
> Cc: Peter Johansson; automake@gnu.org
> Subject: RE: libtool issue in a Makefile.am reference
>
> > Anything
On Mon, 25 Jan 2010, Murray S. Kucherawy wrote:
LIBADD is for libraries. For programs use
progname_LDADD = ../libdirectory/libraryname.la
Sorry, I was in fact using progname_LDADD already. Should've cut-and-pasted
instead of manually transcribing.
Anything else I could try?
You could te
> -Original Message-
> From: automake-bounces+msk=cloudmark@gnu.org [mailto:automake-
> bounces+msk=cloudmark@gnu.org] On Behalf Of Peter Johansson
> Sent: Monday, January 25, 2010 5:10 AM
> To: automake@gnu.org
> Subject: Re: libtool issue in a Makefile.am refe
On 1/25/10 2:25 AM, Murray S. Kucherawy wrote:
I've got a package that first builds a library and then a binary that links to
the library. The binary build references it via:
progname_LIBADD = ../libdirectory/libraryname.la
LIBADD is for libraries. For programs use
progname_LDADD = ../l
Hi!
On Mon, Jan 25, 2010 at 8:25 AM, Murray S. Kucherawy wrote:
> I've got a package that first builds a library and then a
> binary that links to the library. The binary build references
> it via:
>
> progname_LIBADD = ../libdirectory/libraryname.la
I'm not sure if we do it correctly, but we'd
I've got a package that first builds a library and then a binary that links to
the library. The binary build references it via:
progname_LIBADD = ../libdirectory/libraryname.la
A previous version of the library was installed in /usr/local/lib. Some other
things autoconf discovers causes -L/us