Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ken Werner <ken.werner@linaro.org>
To: "Eric Bénard" <eric@eukrea.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Qt 4.8 GCC 4.7 fixes
Date: Fri, 27 Apr 2012 18:19:21 +0200	[thread overview]
Message-ID: <4F9AC709.2020006@linaro.org> (raw)
In-Reply-To: <20120427145304.04e483d3@eb-e6520>

On 04/27/2012 02:53 PM, Eric Bénard wrote:
> Hi Ken,
>
> Le Fri, 27 Apr 2012 12:59:17 +0200,
> Ken Werner<ken.werner@linaro.org>  a écrit :
>
>> This change introduces two new patches to Qt 4.8. One prevents the build
>> system from using the -fuse-ld=gold GCC flag as this isn't upstream and
>> therefore not supported by many toolchains out there. The second patch
>
> ld-is-gold is a DISTRO_FEATURES wich enables gold (and thus reduce link
> time especially in qt's build) : has this patch an effect on the
> possibility to still use gold ?
>
> Eric

No, the patch doesn't prevent the toolchain from linking using gold. 
Upstream GCC+binutils supports either gold or the classic ld - a 
decision you make at the configure time of your toolchain. However, 
Debian and Ubuntu have patched their toolchains to allow the user to 
pick the desired linker using the -fuse-ld option. Technically what they 
do is a patch to the binutils which installs both the ld.bfd and ls.gold 
plus a symlink that selects the default linker. And a GCC patch that 
changes collect2 to support the -fuse-ld switch.

Regards,
Ken



  reply	other threads:[~2012-04-27 16:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 10:59 [PATCH] Qt 4.8 GCC 4.7 fixes Ken Werner
2012-04-27 11:28 ` Richard Purdie
2012-04-27 14:43   ` Khem Raj
2012-04-27 16:19   ` Ken Werner
2012-04-27 12:53 ` Eric Bénard
2012-04-27 16:19   ` Ken Werner [this message]
2012-05-01 18:53 ` Saul Wold
2012-05-01 18:55   ` Saul Wold

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=4F9AC709.2020006@linaro.org \
    --to=ken.werner@linaro.org \
    --cc=eric@eukrea.com \
    --cc=openembedded-core@lists.openembedded.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