From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] GIT or SVN
Date: Fri, 20 Jun 2008 15:18:25 +0200 [thread overview]
Message-ID: <87tzfo8cta.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <485B6CF6.7040901@cetrtapot.si> (Hinko Kocevar's message of "Fri\, 20 Jun 2008 10\:40\:22 +0200")
>>>>> "Hinko" == Hinko Kocevar <hinko.kocevar@cetrtapot.si> writes:
Hi,
Hinko> I've been looking for recent gcc for the cris arch as I was
Hinko> seeing gcc internal errors when compiling kernel or openssl
Hinko> source with gcc 4.2.3 or 4.2.4. With gcc 4.3.1 gcc internal
Hinko> errors went away, so I'm really glad I found the GIT tree!
Notice that 4.3.1 also has issues (on i686 atleast):
http://kerneltrap.org/Linux/Compiler_Oops
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-06-20 13:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 10:23 [Buildroot] GIT or SVN Hinko Kocevar
2008-06-19 10:53 ` Hinko Kocevar
2008-06-19 11:13 ` Bernhard Fischer
2008-06-19 11:54 ` Hinko Kocevar
2008-06-19 12:03 ` Bernhard Fischer
2008-06-19 12:20 ` Hinko Kocevar
2008-06-19 13:25 ` Hinko Kocevar
2008-06-19 19:09 ` Peter Korsgaard
2008-06-20 8:36 ` Bernhard Fischer
2008-06-20 8:40 ` Hinko Kocevar
2008-06-20 12:57 ` Bernhard Fischer
2008-06-20 13:15 ` Hinko Kocevar
2008-06-20 13:24 ` Bernhard Fischer
2008-06-23 10:10 ` Hinko Kocevar
2008-06-20 13:26 ` Hinko Kocevar
2008-06-20 14:11 ` [Buildroot] cris Bernhard Fischer
2008-06-20 14:30 ` Peter Korsgaard
2008-06-20 15:03 ` Bernhard Fischer
2008-06-23 7:27 ` Hinko Kocevar
2008-06-23 8:50 ` Hinko Kocevar
2008-06-23 13:06 ` Bernhard Fischer
2008-06-23 14:48 ` Hinko Kocevar
2008-06-23 13:03 ` Bernhard Fischer
2008-06-23 14:41 ` Hinko Kocevar
2008-06-23 14:46 ` Bernhard Fischer
2008-06-23 14:54 ` Hinko Kocevar
2008-06-23 15:01 ` Bernhard Fischer
2008-07-30 2:39 ` Ralph Siemsen
2008-06-20 13:18 ` Peter Korsgaard [this message]
2008-07-30 8:20 ` [Buildroot] GIT or SVN Hinko Kocevar
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=87tzfo8cta.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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