This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Standardized instructions for cross-compiling toolchain?
- From: Andrew Haley <aph at redhat dot com>
- To: Michael Habibi <mikehabibi at gmail dot com>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Wed, 4 May 2016 18:40:19 +0100
- Subject: Re: Standardized instructions for cross-compiling toolchain?
- Authentication-results: sourceware.org; auth=none
- References: <CAOsp8o-fVfAjgez9ttRw0+ckm+MKOomAXnwURcGmCV+AsMX=oA at mail dot gmail dot com> <572A2247 dot 2020003 at redhat dot com> <CAOsp8o-qYO95SGj+mNsqVhak8gU4ECo8UMhByd+fyeN+iGJrJw at mail dot gmail dot com> <572A2747 dot 7020105 at redhat dot com> <CAOsp8o8rFi88Azs5QOUe-1KvjB0xrjfGYHf5T6Z09-0riQdPNg at mail dot gmail dot com>
On 05/04/2016 06:36 PM, Michael Habibi wrote:
> Thanks again. I will look into using a prebuilt libc. If I were to do
> those steps, do I only need to do a single gcc build with the sysroot
> pointing to the root filesystem + new libc libraries? Or is there any
> special bootstrapping or anything I would need to do?
You want the target libraries and the target headers. Apart from
that it should just work. Of course, there are always some
exceptions.
I often just mount an image of the entire target filesystem and use
that. Sure, that's excessive, but at least you know there is
nothing missing.
Andrew.