search for: ac_link_iflese

...execstack -fstack-protector-strong -pie -lssh -lopenbsd-compat -lutil -lz -lcrypt -lresolv > /usr/bin/ld: unrecognized option '-Wl,-z,relro' That's a slightly different problem: -Wl is a gcc flag that means "pass the following flag through to the linker". Since AC_LINK_IFLESE uses $CC and not $LD, this works in configure, but apparently bare ld does not understand -Wl. The only way I can think of right now to fix that is to manually invoke $LD inside the test macro. Lemme have a bit more of a think. -- Darren Tucker (dtucker at dtucker.net) GPG key 11EAA6FA / A86E 3...

...-pie -lssh -lopenbsd-compat -lutil -lz -lcrypt -lresolv >>> /usr/bin/ld: unrecognized option '-Wl,-z,relro' >> >> That's a slightly different problem: -Wl is a gcc flag that means >> "pass the following flag through to the linker". Since AC_LINK_IFLESE >> uses $CC and not $LD, this works in configure, but apparently bare ld >> does not understand -Wl. The only way I can think of right now to fix >> that is to manually invoke $LD inside the test macro. Lemme have a >> bit more of a think. > > Looking into autoconf...

On Thu, Jun 07, 2018 at 06:14:42PM -0700, PGNet Dev wrote: > On 6/7/18 6:08 PM, Darren Tucker wrote: > > Well the intent is you should be able to set CC and LD to whatever you > > want as long as they work. In this case, the OSSH_CHECK_LDFLAG_LINK > > test invokes autoconf's AC_LINK_IFELSE with uses CC not LD. I'm not > > sure what to do about it yet though. I