qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH, RFC] ld flag --warn-common
Date: Sun, 7 Sep 2008 15:30:03 +0300	[thread overview]
Message-ID: <f43fc5580809070530o44406d6dl6a1a55c6247db8d@mail.gmail.com> (raw)
In-Reply-To: <cef699d70809070450p53179948l58bab9adade41109@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 642 bytes --]

On 9/7/08, Ben Taylor <bentaylor.solx86@gmail.com> wrote:
> On Sun, Sep 7, 2008 at 4:24 AM, Blue Swirl <blauwirbel@gmail.com> wrote:
>  > Hi,
>  >
>  > These trivial patches enable linker flag --warn-common and fix the
>  > warnings caused by enabling the flag.
>  >
>  > I think on some platforms (Solaris?) the linker used by gcc is not GNU
>  > ld. If this is true, the patch would break compilation on those hosts
>  > and logic in configure would need to be more complex. Please confirm.
>
>
> yes, Solaris does not use gnu ld, it uses it's own linker.

Could you test if with this patch applied, "other ld" is printed when
configuring?

[-- Attachment #2: ld_warn_common.diff --]
[-- Type: plain/text, Size: 568 bytes --]

  reply	other threads:[~2008-09-07 12:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-07  8:24 [Qemu-devel] [PATCH, RFC] ld flag --warn-common Blue Swirl
2008-09-07 11:50 ` Ben Taylor
2008-09-07 12:30   ` Blue Swirl [this message]
2008-09-09 15:14     ` Ben Taylor
2008-09-09 15:56       ` Blue Swirl
2008-09-09 16:46         ` Blue Swirl
2008-09-19 16:37 ` Kirill A. Shutemov
2008-09-20  7:49   ` Blue Swirl
2008-09-21 21:14     ` Kirill A. Shutemov
2008-09-22 16:24       ` Blue Swirl
2008-09-22 16:39         ` Kirill A. Shutemov
2008-09-22 17:16           ` 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=f43fc5580809070530o44406d6dl6a1a55c6247db8d@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).