gprolog not respecting LDFLAGS

[Keri Harris]

Hi

When building gprolog-1.5.0 a number of binaries are linked without respecting LDFLAGS:

x86_64-pc-linux-gnu-gcc  -O2 -pipe -frecord-gcc-switches -fcommon -fno-strict-aliasing -Wno-char-subscripts  -o pl_config pl_config.c

x86_64-pc-linux-gnu-gcc  -O2 -pipe -frecord-gcc-switches -fcommon -fno-strict-aliasing -Wno-char-subscripts -o gplc top_comp.c -lm

x86_64-pc-linux-gnu-gcc  -O2 -pipe -frecord-gcc-switches -fcommon -fno-strict-aliasing -Wno-char-subscripts  -o cpp_headers cpp_headers.c

x86_64-pc-linux-gnu-gcc  -O2 -pipe -frecord-gcc-switches -fcommon -fno-strict-aliasing -Wno-char-subscripts -o hexgplc hexfilter.c

x86_64-pc-linux-gnu-gcc  -O2 -pipe -frecord-gcc-switches -fcommon -fno-strict-aliasing -Wno-char-subscripts -o wam2ma wam2ma.o wam_parser.o

x86_64-pc-linux-gnu-gcc  -O2 -pipe -frecord-gcc-switches -fcommon -fno-strict-aliasing -Wno-char-subscripts -o ma2asm ma2asm.o ma2asm_inst.o ma_parser.o

The binaries above in src/EnginePl are missing LDFLAGS due to a typo in the Makefile (LFLAGS vs LDFLAGS); the other binaries are missing LDFLAGS in the $CC invocation.

Attached is a patch that I've been using on Gentoo Linux.

Thanks

Keri

gprolog-1.5.0-ldflags.patch
Description: Text Data