search for: ldflags_orig

Displaying 4 results from an estimated 4 matches for "ldflags_orig".

Did you mean: cflags_orig
2006 Nov 19
2
SSL flags (was Re: [nut-commits] svn commit r593 - branches/deb_fixes_for_trunk)
Peter, Any objections to adding this to the trunk? When I run 'ldd upsc' without this patch, it lists the OpenSSL libraries, and the default ./configure setting is to not use OpenSSL. - Charles > Log: > If we are not using SSL_CFLAGS or SSL_LDFLAGS, do not add the OpenSSL libraries > to all of the binaries. > > > Modified: branches/deb_fixes_for_trunk/configure.in >
2009 Dec 15
1
patch for m4/nut_check_libnetsnmp.m4
...2009-12-15 11:12:15.291295000 -0800 @@ -9,7 +9,8 @@ if test -z "${nut_have_libnetsnmp_seen}"; then nut_have_libnetsnmp_seen=yes - dnl save CFLAGS and LDFLAGS + dnl save CPPFLAGS CFLAGS and LDFLAGS + CPPFLAGS_ORIG="${CFLAGS}" CFLAGS_ORIG="${CFLAGS}" LDFLAGS_ORIG="${LDFLAGS}" @@ -38,6 +39,7 @@ fi AC_MSG_CHECKING(for Net-SNMP headers) + CPPFLAGS="${CPPFLAGS} ${CFLAGS}" AC_TRY_CPP([#include <net-snmp/net-snmp-config.h>], [AC_MSG_RESULT(yes) ], @@ -49,7 +51,8 @@ LIBNETSNMP_LDFLAGS="${LDFLAGS}"...
2008 Feb 21
0
m4 scripts ignore user-supplied CFLAGS and LDFLAGS
...m embedded firmware. And one of the authors complained about NUT script for checking ssl library ignoring supplied CFLAGS and LDFLAGS with the desired include and library paths. I checked several scripts in m4 folder and all of them do something like this: CFLAGS_ORIG="${CFLAGS}" LDFLAGS_ORIG="${LDFLAGS}" CFLAGS="" LDFLAGS="..." at the beginning. Is it for purpose? Why not check first with the user-supplied variables? I'm not very good in all this autotools magic so please forgive me if this whole thing is dumb :) P.S. What is the "righ...
2008 Feb 23
0
Fwd: m4 scripts ignore user-supplied CFLAGS and LDFLAGS
...hors complained about NUT script for checking > ssl library ignoring supplied CFLAGS and LDFLAGS with the > desired include and library paths. > I checked several scripts in m4 folder and all of them do > something like this: > > CFLAGS_ORIG=3D"${CFLAGS}" > LDFLAGS_ORIG=3D"${LDFLAGS}" > > CFLAGS=3D"" > LDFLAGS=3D"..." > > at the beginning. Is it for purpose? Why not check first with > the user-supplied variables? > > I'm not very good in all this autotools magic so please > forgive me if thi...