From: Josh Henderson <digitalpeer@digitalpeer.com>
To: Trevor Woerner <twoerner@gmail.com>, crossgcc@sourceware.org
Subject: Re: Building a static toolchain ?
Date: Wed, 31 Mar 2010 21:18:00 -0000 [thread overview]
Message-ID: <g2o3530b0eb1003311418o8ce501acm6d880703b1e8740a@mail.gmail.com> (raw)
In-Reply-To: <v2jf415e2731003311408p92fcf6bcte34bcc5e42810a5a@mail.gmail.com>
I can add a few more comments. In my case I have a variety of distros
that have incompatible glibc versions. To lessen the burden of
maintaining multiple toolchain builds, a single static gcc gets the
job done. However, be aware that gcc RAM usage is considerably higher
when compiling.
On 3/31/10, Trevor Woerner <twoerner@gmail.com> wrote:
> Okay, thanks so much for the information!
>
> Just out of curiosity:
>
> 1. Since newer glibc's are compatible with older glibc's (but not the
> other way around) is it not possible to take the latest glibc and
> lower the 'minimum supported kernel version'?
>
> 2. If you have built your toolchain statically linked to an older
> glibc then wouldn't it would mean you couldn't compile programs which
> use newer system calls (e.g. futex, inotify)?
>
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
>
>
--
Sent from my mobile device
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2010-03-31 21:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 17:46 M P
2010-03-24 19:44 ` Yann E. MORIN
2010-03-24 20:04 ` Josh Henderson
2010-03-25 22:24 ` Yann E. MORIN
2010-03-31 20:37 ` Trevor Woerner
2010-03-31 20:50 ` Dimitry Andric
2010-03-31 21:08 ` Trevor Woerner
2010-03-31 21:18 ` Josh Henderson [this message]
2010-03-31 21:22 ` Khem Raj
2010-03-31 21:23 ` Trevor Woerner
2010-03-31 21:31 ` Yann E. MORIN
2010-03-31 21:26 ` Yann E. MORIN
2010-04-01 9:43 ` Dimitry Andric
2010-04-01 18:53 ` Khem Raj
2010-04-01 19:05 ` Marc Kleine-Budde
2010-04-01 20:29 ` Dimitry Andric
2010-04-05 0:31 Arnaud Lacombe
2010-04-10 10:50 ` Yann E. MORIN
2010-04-10 17:10 ` Arnaud Lacombe
2010-04-10 17:20 ` Yann E. MORIN
2010-04-10 17:28 ` Yann E. MORIN
2010-04-10 21:35 ` Yann E. MORIN
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=g2o3530b0eb1003311418o8ce501acm6d880703b1e8740a@mail.gmail.com \
--to=digitalpeer@digitalpeer.com \
--cc=crossgcc@sourceware.org \
--cc=twoerner@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).