This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[PATCH] libtool.m4: remove (incorrect) handling of FreeBSD 1.x
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: libtool-patches at gnu dot org
- Cc: gcc-patches at gcc dot gnu dot org, Loren James Rittle <rittle at labs dot mot dot com>
- Date: Thu, 20 Jan 2011 00:01:58 +0100 (CET)
- Subject: [PATCH] libtool.m4: remove (incorrect) handling of FreeBSD 1.x
FreeBSD has been dead for way over a decade (FreeBSD 2.0 was released
in 1994) and without support for dynamic linking and shared libraries
I doubt there's a lot of software that would build at all.
In anycase, libtool's handling code to handle it is buggy and will soon
also match FreeBSD 10.0 and later which do support dynamic linking.
I think it's best to simplify libtool.m4 per the patch below.
I do not have libtool write access, so appreciate help. Let me know
how to handle this for GCC, where this should go to HEAD, 4.5 and 4.4
at least.
Thanks,
Gerald
2011-01-19 Gerald Pfeifer <gerald@pfeifer.com>
* libtool.m4: Remove handling of freebsd1* which soon would
incorrectly match FreeBSD 10.0.
Index: libtool.m4
===================================================================
--- libtool.m4 (revision 168842)
+++ libtool.m4 (working copy)
@@ -2266,10 +2266,6 @@
shlibpath_var=LD_LIBRARY_PATH
;;
-freebsd1*)
- dynamic_linker=no
- ;;
-
freebsd* | dragonfly*)
# DragonFly does not have aout. When/if they implement a new
# versioning mechanism, adjust this.
@@ -4796,10 +4792,6 @@
_LT_TAGVAR(hardcode_shlibpath_var, $1)=no
;;
- freebsd1*)
- _LT_TAGVAR(ld_shlibs, $1)=no
- ;;
-
# FreeBSD 2.2.[012] allows us to include c++rt0.o to get C++ constructor
# support. Future versions do this automatically, but an explicit c++rt0.o
# does not break anything, and helps significantly (at the cost of a little