This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Linux Foundation Collaboration Summit: The future of The GNU C Library.
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: david dot hagood at gmail dot com
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Wed, 28 Mar 2012 10:21:55 -0400
- Subject: Re: Linux Foundation Collaboration Summit: The future of The GNU C Library.
- References: <fa9e81332b9da6093d4bba9c133eacf7.squirrel@localhost>
On Wed, Mar 28, 2012 at 10:05 AM, <david.hagood@gmail.com> wrote:
> As an embedded systems developer, one thing I could ask would be to make
> cross-compiling a bit easier - as it stands, to build a cross toolchain, I
> have to:
> 1) build binutils
> 2) copy headers out of glibc
> 3) Build part of gcc
> 4) build part of glibc
> 5) build the rest of gcc
> 6) build the rest of glibc.
>
> If there were some way to refactor the process to make that a bit easier -
> even just something as simple as allowing the make for (gcc|glibc) to
> drive the make for (glibc|gcc) - that would be a great help.
>
> I realize there is a great deal of cross-coupling between GCC and glibc,
> and it will take work from both sides to help this, but in the past,
> questions like this have led to a great deal of "Ask your mother"/"Ask
> your father" style responses.
The process could certainly be made easier and more well documented.
Cheers,
Carlos.