public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: Trevor Woerner <twoerner@gmail.com>
Subject: Re: Building a static toolchain ?
Date: Wed, 31 Mar 2010 21:31:00 -0000	[thread overview]
Message-ID: <201003312331.24377.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <v2jf415e2731003311408p92fcf6bcte34bcc5e42810a5a@mail.gmail.com>

On Wednesday 31 March 2010 23:08:36 Trevor Woerner 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'?

Woohoo... Stop!
We're speaking of building the toolchain components statically!
That is: gcc and binutils, period. (yes, and gdb if you want).

The glibc that is built with the toolchain is not what we are speaking
about! And this is this glibc that has a 'minimum supported kernel
version'.

But I have to agree that it gets messy to speak about this stuff! ;-)

> 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)?

See above, irrelevant, we're speaking a bout the *host* C library, not
the target's C library.

Hope this makes it clear. :-) (BTW, I just saw Khem answered the same).

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'



--
For unsubscribe information see http://sourceware.org/lists.html#faq

  parent reply	other threads:[~2010-03-31 21:31 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
2010-03-31 21:22             ` Khem Raj
2010-03-31 21:23               ` Trevor Woerner
2010-03-31 21:31             ` Yann E. MORIN [this message]
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=201003312331.24377.yann.morin.1998@anciens.enib.fr \
    --to=yann.morin.1998@anciens.enib.fr \
    --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).