From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Build breakage on OpenSolaris: --warn-common
Date: Sat, 1 Nov 2008 16:03:01 +0200 [thread overview]
Message-ID: <f43fc5580811010703m5e405b4t2ecab1619d4f1a1e@mail.gmail.com> (raw)
In-Reply-To: <A2D63949-62B4-4F4D-BD69-4E9816140F28@web.de>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
On 11/1/08, Andreas Färber <andreas.faerber@web.de> wrote:
>
> Am 31.10.2008 um 22:27 schrieb Blue Swirl:
>
>
> > On 10/31/08, Andreas Färber <andreas.faerber@web.de> wrote:
> >
> > > The following addition to configure at r5241 causes linking to fail on
> > > OpenSolaris/amd64:
> > >
> > > if ld --version 2>/dev/null | grep -q "GNU ld" ; then
> > > LDFLAGS="$LDFLAGS -Wl,--warn-common"
> > > fi
> > >
> > > Contrary to Solaris 10, OpenSolaris does use GNU ld. Might --warn-common
> > > require an ld version newer than 2.15, or is this platform-dependent?
> > >
> >
> > According to binutils changelog, --warn-common was added in 1993, so
> > maybe the platform breaks that. What does your ld print with ld
> > --version?
> >
>
> GNU ld version 2.15
> Copyright 2002 Free Software Foundation, Inc.
> This program is free software; [...]
>
> So definitely past 1993. Any thoughts what to check for?
>
>
> >
> >
> > > Previously I had also reported that Solaris 10's grep rejects -q. Could
> we
> > > use `grep "GNU ld" >/dev/null 2>/dev/null` instead?
> > >
> >
> > Sure.
> >
>
> I'll prepare a patch for that part then.
Does this one work?
[-- Attachment #2: fix_solaris_warn_common.diff --]
[-- Type: plain/text, Size: 639 bytes --]
next prev parent reply other threads:[~2008-11-01 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 21:08 [Qemu-devel] Build breakage on OpenSolaris: --warn-common Andreas Färber
2008-10-31 21:27 ` Blue Swirl
2008-11-01 13:28 ` Andreas Färber
2008-11-01 14:03 ` Blue Swirl [this message]
2008-11-01 14:43 ` Andreas Färber
2008-11-01 14:51 ` Blue Swirl
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=f43fc5580811010703m5e405b4t2ecab1619d4f1a1e@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).