On Sat, Sep 20, 2014 at 6:46 AM, Warren Young wrote:
> Just stepping back a bit, some linkers are more tolerant than others about
> the order of flags and such. Libraries that land in standard locations
> like /usr/lib also obscure this issue, by rendering irrelevant an
> improperly-placed or -c
On Sat, Sep 20, 2014 at 6:16 AM, Bob Friesenhahn <
bfrie...@simple.dallas.tx.us> wrote:
> A library is not a linker flag so it does not belong in LDFLAGS. Look into
> using a 'LIBADD' type option instead.
>
> Thanks for pointing me in the right direction.
The bad line in my Makefile.am has now be
On 9/19/2014 17:16, Bob Friesenhahn wrote:
On Sat, 20 Sep 2014, Robert Parker wrote:
AM_LDFLAGS = -lmhash
A library is not a linker flag so it does not belong in LDFLAGS. Look
into using a 'LIBADD' type option instead.
This problem seems to be a 'feature' of gcc because the same error
happe
On Sat, 20 Sep 2014, Robert Parker wrote:
Here is my Makefile.am
AM_CFLAGS=-Wall -Wextra
bin_PROGRAMS=pwordsaver
pwordsaver_SOURCES=pwordsaver.c fileutil.c fileutil.h
AM_LDFLAGS = -lmhash
A library is not a linker flag so it does not belong in LDFLAGS.
Look into using a 'LIBADD' type option
