From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [PATCH build, libgo, classpath] Remove freebsd1 from libtool.m4 macros and config.rpath.
Date: Sun, 13 Feb 2011 21:00:00 -0000 [thread overview]
Message-ID: <20110213210026.GC32642@gmx.de> (raw)
In-Reply-To: <20110213114641.GJ26711@gmx.de>
[ moving from gcc-patches ]
* Ralf Wildenhues wrote on Sun, Feb 13, 2011 at 12:46:42PM CET:
> I'm applying this patch to remove freebsd1 handling from Libtool macros
> and config.rpath, in order to avoid problems when FreeBSD 10 releases.
> This just pulls in Gerald's patch which has been applied to upstream
> Libtool, regenerates all stuff,
[...]
This syncs the change from GCC to src and rebuilds all related files for
binutils and gdb.
Thanks,
Ralf
ChangeLog:
2011-02-13 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Import from Libtool and gnulib:
2011-01-27 Gerald Pfeifer <gerald@pfeifer.com>
Prepare for supporting FreeBSD 10.
* config.rpath: Remove handling of freebsd1* which soon would
match FreeBSD 10.0.
2011-01-20 Gerald Pfeifer <gerald@pfeifer.com> (tiny change)
Remove support for FreeBSD 1.x.
* libtool.m4 (_LT_LINKER_SHLIBS)
(_LT_SYS_DYNAMIC_LINKER): Remove handling of freebsd1* which
soon would incorrectly match FreeBSD 10.0.
bfd/ChangeLog:
2011-02-13 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
* configure: Regenerate.
gas/ChangeLog:
2011-02-13 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
* configure: Regenerate.
ld/ChangeLog:
2011-02-13 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
* configure: Regenerate.
opcodes/ChangeLog:
2011-02-13 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
* configure: Regenerate.
binutils/ChangeLog:
2011-02-13 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
* configure: Regenerate.
gprof/ChangeLog:
2011-02-13 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
* configure: Regenerate.
Index: libtool.m4
===================================================================
RCS file: /cvs/src/src/libtool.m4,v
retrieving revision 1.22
diff -u -r1.22 libtool.m4
--- libtool.m4 9 Jan 2010 21:11:31 -0000 1.22
+++ libtool.m4 13 Feb 2011 20:01:20 -0000
@@ -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
Index: config.rpath
===================================================================
RCS file: /cvs/src/src/config.rpath,v
retrieving revision 1.2
diff -u -r1.2 config.rpath
--- config.rpath 13 Mar 2008 19:27:44 -0000 1.2
+++ config.rpath 13 Feb 2011 20:01:20 -0000
@@ -284,9 +284,6 @@
dgux*)
hardcode_libdir_flag_spec='-L$libdir'
;;
- freebsd1*)
- ld_shlibs=no
- ;;
freebsd2.2*)
hardcode_libdir_flag_spec='-R$libdir'
hardcode_direct=yes
@@ -448,8 +445,6 @@
;;
dgux*)
;;
- freebsd1*)
- ;;
freebsd*)
;;
gnu*)
parent reply other threads:[~2011-02-13 21:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20110213114641.GJ26711@gmx.de>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110213210026.GC32642@gmx.de \
--to=ralf.wildenhues@gmx.de \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).