From: "Dave Korn" <dave.korn.cygwin@googlemail.com>
To: gcc-patches@gcc.gnu.org, binutils@sourceware.org,
gdb-patches@sourceware.org, cygwin-patches@cygwin.com
Cc: kirkshorts@googlemail.com, "DJ Delorie" <dj@redhat.com>
Subject: [PATCH/libiberty] Fix PR38903 Cygwin GCC bootstrap failure [was Re: Libiberty issue vs cygwin [was Re: This is a Cygwin failure yeah?]]
Date: Sun, 18 Jan 2009 00:52:00 -0000 [thread overview]
Message-ID: <2ca21dcc0901171652s44c72ca7teb1ca6041344e4a4@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
DJ Delorie wrote:
> IIRC, that whole clause was because cygwin's dll itself linked with
> libiberty, so the auto-detect stuff needed an override to make sure
> the right files were there when you build cygwin1.dll. Otherwise, it
> would detect that cygwin had strsignal, not build it, then fail later
> when cygwin1.dll couldn't find strsignal.
>
> If cygwin no longer links with libiberty, that whole clause can
> probably go away now. As it's target-specific, I'm OK with letting
> the target maintainers have the last word about it, too.
There are no longer any references to ../libiberty/* in Cygwin's Makefile,
and indeed the libiberty subdir has been removed from the module definition
for winsup so you don't even get it in a fresh checkout any more.
Given that, I think we can remove the clause entirely. I've tested this by
doing (separate) native builds of GCC, winsup, binutils and GDB, with no
issues arising. I haven't tried cross-builds or combined source-tree builds,
but there's no reason to believe they would be affected any differently.
GCC is in stage 4, but this is target-specific and fixes a bootstrap
failure on a secondary platform.
Ok for HEAD of both gcc/ and src/ ?
libiberty/ChangeLog
* configure.ac (funcs, vars, checkfuncs): Don't munge on Cygwin,
as it no longer shares libiberty object files.
* configure: Regenerated.
cheers,
DaveK
[-- Attachment #2: libiberty-cyghack-removal-patch.diff --]
[-- Type: application/octet-stream, Size: 1296 bytes --]
Index: libiberty/configure.ac
===================================================================
--- libiberty/configure.ac (revision 143471)
+++ libiberty/configure.ac (working copy)
@@ -571,29 +571,6 @@ if test -z "${setobjs}"; then
case "${host}" in
- *-*-cygwin*)
- # The Cygwin library actually uses a couple of files from
- # libiberty when it is built. If we are building a native
- # Cygwin, and we run the tests, we will appear to have these
- # files. However, when we go on to build winsup, we will wind up
- # with a library which does not have the files, since they should
- # have come from libiberty.
-
- # We handle this by removing the functions the winsup library
- # provides from our shell variables, so that they appear to be
- # missing.
-
- # DJ - only if we're *building* cygwin, not just building *with* cygwin
-
- if test -n "${with_target_subdir}"
- then
- funcs="`echo $funcs | sed -e 's/random//'`"
- AC_LIBOBJ([random])
- vars="`echo $vars | sed -e 's/sys_siglist//'`"
- checkfuncs="`echo $checkfuncs | sed -e 's/strsignal//' -e 's/psignal//'`"
- fi
- ;;
-
*-*-mingw32*)
# Under mingw32, sys_nerr and sys_errlist exist, but they are
# macros, so the test below won't find them.
next reply other threads:[~2009-01-18 0:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 0:52 Dave Korn [this message]
2009-01-18 5:06 ` Christopher Faylor
2009-01-18 17:07 ` DJ Delorie
2009-01-18 21:38 ` Dave Korn
2009-01-18 21:58 ` DJ Delorie
2009-01-18 23:13 ` Dave Korn
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=2ca21dcc0901171652s44c72ca7teb1ca6041344e4a4@mail.gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=binutils@sourceware.org \
--cc=cygwin-patches@cygwin.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kirkshorts@googlemail.com \
/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