From: Dirk Behme <dirk.behme@googlemail.com>
To: lvcargnini@ieee.org
Cc: OMAP <Linux-omap-open-source@linux.omap.com>
Subject: Re: Problems compiling gcc-4.1.0
Date: Sat, 15 Jul 2006 07:06:32 +0200 [thread overview]
Message-ID: <44B877D8.4050907@gmail.com> (raw)
In-Reply-To: <ae36f8040607141045p5669198ci65d28617d466bbed@mail.gmail.com>
Luís Cargnini wrote:
> i have modified ../gcc-4.1.0/gcc/config/arm/t-linux and added
> -Dinhibit_libc
> -D__gthr_posix_h
> what should i do ???
Maybe you should use an other (working?) toolchain?
Building gcc 4.1.0 with crosstool-0.42
http://kegel.com/crosstool/
using crosstool's
eval `cat arm.dat gcc-4.1.0-glibc-2.3.2.dat` sh all.sh --notest
configuration works for me (except ALSA optimization issue [1]).
Or if you like prebuild toolchain
http://www.codesourcery.com/gnu_toolchains/arm/
Regards
Dirk
[1] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27363
prev parent reply other threads:[~2006-07-15 5:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 17:45 Problems compiling gcc-4.1.0 Luís Cargnini
2006-07-14 17:46 ` Luís Cargnini
2006-07-15 5:06 ` Dirk Behme [this message]
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=44B877D8.4050907@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=Linux-omap-open-source@linux.omap.com \
--cc=lvcargnini@ieee.org \
/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