summaryrefslogtreecommitdiffstats
path: root/sys/netpfil/ipfw/ip_fw2.c
diff options
context:
space:
mode:
authoremaste <emaste@FreeBSD.org>2017-04-03 01:57:03 +0000
committeremaste <emaste@FreeBSD.org>2017-04-03 01:57:03 +0000
commiteb236decaacbbaaa57d6eedc028e512cb945a2e0 (patch)
tree735bc53860626836857324991e9b20ce4e91860f /sys/netpfil/ipfw/ip_fw2.c
parentf03cd44ca41ffaacbad1f0958f1ccae209f60e4e (diff)
downloadFreeBSD-src-eb236decaacbbaaa57d6eedc028e512cb945a2e0.zip
FreeBSD-src-eb236decaacbbaaa57d6eedc028e512cb945a2e0.tar.gz
MFC r316029: lld: hack version and help output for compatibility with libtool
GNU libtool checks the output from invoking the linker with --version and --help, in order to determine the linker "flavour" and the command- ine arguments to use for various link operations (e.g. generating shared libraries). To detect GNU ld it looks for the strings "GNU" and "supported targets:.*elf". Since LLD is compatible with GNU ld we include those same strings to fool libtool. Quoting from a comment in the change: This is somewhat ugly hack, but in reality, we had no choice other than doing this. Considering the very long release cycle of Libtool, it is not easy to improve it to recognize LLD as a GNU compatible linker in a timely manner. Even if we can make it, there are still a lot of "configure" scripts out there that are generated by old version of Libtool. We cannot convince every software developer to migrate to the latest version and re-generate scripts. So we have this hack. Upstream LLVM revisions r298532, r298568, r298591 Sponsored by: The FreeBSD Foundation
Diffstat (limited to 'sys/netpfil/ipfw/ip_fw2.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud