From: <music@linuxconsole.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: <crossgcc@sourceware.org>
Subject: Re: using crossgcc with old glibc
Date: Mon, 30 Jan 2012 18:38:00 -0000 [thread overview]
Message-ID: <fd970f86e0bb7611f04a0b767bfcddd0@localhost> (raw)
In-Reply-To: <CAMKF1sprUmCM=Q=sAwNF-0PAJqMb97S8B3ha2hqc-m_SGGLoYg@mail.gmail.com>
I tried it with
CT_BINUTILS_EXTRA_CONFIG_ARRAY="LDFLAGS=-all-static"
and
CT_CC_EXTRA_CONFIG_ARRAY="LDFLAGS=-static"
into crosstool-ng config
but if failed when building gcc with a lot of g++ undefined reference
errors
I will build my toolchain with the oldest glibc, then I could export it
on every computer.
Thanks.
On Sat, 28 Jan 2012 14:37:45 -0800, Khem Raj <raj.khem@gmail.com>
wrote:
> On Sat, Jan 28, 2012 at 1:24 PM, <music@linuxconsole.org> wrote:
>>
>> is there a way to use my toolchain on this older system ?
>
> build statically linked toolchain
>
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
--
For unsubscribe information see http://sourceware.org/lists.html#faq
prev parent reply other threads:[~2012-01-30 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-28 21:24 music
2012-01-28 22:38 ` Khem Raj
2012-01-30 18:38 ` music [this message]
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=fd970f86e0bb7611f04a0b767bfcddd0@localhost \
--to=music@linuxconsole.org \
--cc=crossgcc@sourceware.org \
--cc=raj.khem@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).