From: Johannes Stezenbach <js@sig21.net>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: crossgcc@sourceware.org
Subject: Re: gold vs. CT_STATIC_TOOLCHAIN
Date: Wed, 14 Dec 2011 11:15:00 -0000 [thread overview]
Message-ID: <20111214111524.GA27754@sig21.net> (raw)
In-Reply-To: <201112140109.21263.yann.morin.1998@anciens.enib.fr>
On Wed, Dec 14, 2011 at 01:09:21AM +0100, Yann E. MORIN wrote:
> Johannes, All,
>
> On Friday 02 December 2011 14:24:50 Johannes Stezenbach wrote:
> > with CT_STATIC_TOOLCHAIN ./scripts/build/binutils/binutils.sh
> > adds -all-static to LDFLAGS. However, -all-static is a libtool
> > option and gold is not libtoolized. Maybe cg-ng should just
> > disable gold when CT_STATIC_TOOLCHAIN is selected?
>
> It works here for me:
>
> $ file bin/armeb-unknown-linux-uclibcgnueabi-ld.gold
> bin/armeb-unknown-linux-uclibcgnueabi-ld.gold: ELF 64-bit LSB executable,
> x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 2.6.18,
> not stripped
>
> So, it is a statically-linked executable, exactly what we wanted.
>
> How does it break for you?
I didn't save the log so I'd have to rebuild to find out
(which I'll do asap), but IIRC it was similar to
$ gcc foo.c -all-static
gcc: error: unrecognized option ‘-all-static’
In case it matters, I used the newest available binutils,
(IIRC binutils-2.21.53 in ct-ng-1.13.2, and now 2.22
with ct-ng from hg.
Thanks
Johannes
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2011-12-14 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 13:25 Johannes Stezenbach
2011-12-13 17:23 ` Johannes Stezenbach
2011-12-13 22:32 ` Yann E. MORIN
2011-12-14 0:09 ` Yann E. MORIN
2011-12-14 11:15 ` Johannes Stezenbach [this message]
2011-12-14 11:43 ` Johannes Stezenbach
2012-01-16 23:22 ` Yann E. MORIN
2012-01-18 12:01 ` Johannes Stezenbach
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=20111214111524.GA27754@sig21.net \
--to=js@sig21.net \
--cc=crossgcc@sourceware.org \
--cc=yann.morin.1998@anciens.enib.fr \
/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).