GNU bug report logs - #78411
LDADD vs. LDFLAGS

Previous Next

Package: automake;

Reported by: Bruno Haible <bruno <at> clisp.org>

Date: Tue, 13 May 2025 17:00:02 UTC

Severity: normal

Done: Karl Berry <karl <at> freefriends.org>

Bug is archived. No further changes may be made.

Full log

Message #8 received at 78411 <at> debbugs.gnu.org (full text, mbox):

From: Karl Berry <karl <at> freefriends.org>
To: bruno <at> clisp.org
Cc: 78411 <at> debbugs.gnu.org
Subject: Re: bug#78411: LDADD vs. LDFLAGS
Date: Wed, 14 May 2025 15:43:00 -0600

     If you need to link against libraries that are not found by
     @command{configure}, you can use @code{LDADD} to do so.  This variable is
    -used to specify additional objects or libraries to link with; it is
    -inappropriate for specifying specific linker flags; you should use
    -@code{AM_LDFLAGS} for this purpose.
    +used to specify additional objects or libraries to link with.
    +Libraries to link with can be indicated either as file names or
    +through @code{-L} and @code{-l} options.
    +
    +For other linker options (not @code{-L} or @code{-l}), @code{LDADD}
    +is inappropriate.  You should use @code{AM_LDFLAGS} for this purpose.

Thanks Bruno. Pushed as written. -k
This bug report was last modified 1 day ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.