This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Apologies to Mr. Bigga."ng" (Peter?), All,
On Thursday 30 April 2009 08:56:23 ng@piments.com wrote:[ALL ] checking build system type... i686-build_pc-linux-gnu
[ALL ] checking host system type... arm-unknown-linux-gnueabi
[ERROR] checking sysdep dirs... configure: error: The arm is not supported.
[ERROR] Build failed in step 'Installing C library headers'
it seems odd that I am having so many errors since updating to 1.4.0 ,
Here's what I see on a fresh untar of the 1.4.0 release tarball, in the C library menu:
--8<-- Begin quote --8<-- C library (glibc) ---> glibc version (2.9) ---> Retrieval method (Released tarball) ---> *** glibc/eglibc common options *** () extra config (NEW) () Extra config params (READ HELP) (NEW) () extra target CFLAGS (NEW) () gcc extra flags (NEW) [ ] Use the ports addon (NEW) () Extra addons (NEW) Minimum supported kernel version (Same as kernel headers (default)) ---> *** Common C library options *** Threading implementation to use: (nptl) ---> --8<-- End quote --8<--
So, clearly, the "Use the ports addon" entry is there.
The only glitch you will encounter is that, for glibc 2.8 and above, there are *no* released tarballs for the ports addon, so you'll have to use: "CVS checkout" as the "Retrieval method".
my initial installation of ct-ng 1.3.9 went beautifully and compiled the
There was no such thing as crosstool-NG-1.3.9. The latest release in the 1.3 series was 1.3.4.
I wanted to use the versions posted by Alexandre Biggin as being a
Please do him a favour: his name is BIGGA, not BIGGIN.
Also, in the documentation, it is stated that you can use the pre-configured toolchains. The list of available toolchains, besides being available on the site, can be obtained with: ct-ng list-samples
To set-up for such a toolchain, call something like: ct-ng the-tool-chain-name ct-ng build
I was able to do the above since I had read the brief text in help and overview. I don't recall either of these refering to requiring addons for ARM builds nor the need to use a cvs pull to get it to build.
You can get some help with: ct-ng help
and the README points you to reading the files docs/overview.txt and docs/known-issues.txt .
Regards, Yann E. MORIN.
-- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |