From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/gcc: 4.3.1
Date: Fri, 20 Jun 2008 18:40:16 +0200 [thread overview]
Message-ID: <20080620164016.GA15878@mx.loc> (raw)
In-Reply-To: <6a2e33620806200906h5b27d157s551782a16eb00a36@mail.gmail.com>
On Fri, Jun 20, 2008 at 06:06:17PM +0200, Fathi Boudra wrote:
>>
>> If there are problems then it would make more sense to fixup 4.3.1, really.
>>
>
>I agree but there's no clue so far:
>btw, it's against libc and not uclibc.
Don't get me wrong, but i'm not interrested in glibc in this context.
> I tried against uclibc but I
>have another build failure.
That would be more interresting, yes.
What thing are you targeting? I could try a CHRP32 defconfig from the
kernel, or is there some config that would actually run on e.g. qemu?
next prev parent reply other threads:[~2008-06-20 16:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 19:06 [Buildroot] svn commit: trunk/buildroot/toolchain/gcc: 4.3.1 jacmet at uclibc.org
2008-06-20 15:50 ` Fathi Boudra
2008-06-20 15:56 ` Bernhard Fischer
2008-06-20 16:06 ` Fathi Boudra
2008-06-20 16:40 ` Bernhard Fischer [this message]
2008-06-20 18:32 ` Peter Korsgaard
2008-06-20 18:50 ` Fathi Boudra
2008-06-20 20:13 ` Fathi Boudra
2008-06-21 12:51 ` Bernhard Fischer
2008-06-25 19:22 ` Fathi Boudra
2008-06-21 12:21 ` Bernhard Fischer
2008-06-20 18:24 ` Peter Korsgaard
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=20080620164016.GA15878@mx.loc \
--to=rep.dot.nop@gmail.com \
--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