From: Michael Hunold <hunold@linuxtv.org>
To: buildroot@busybox.net
Subject: [Buildroot] error when building gcc using buildroot/toolchain
Date: Mon, 17 Dec 2007 09:47:31 +0100 [thread overview]
Message-ID: <476637A3.6010906@linuxtv.org> (raw)
In-Reply-To: <20071211222816.GI17973@aon.at>
Hello Bernhard,
thanks for your answer and sorry for the delay from my side.
on 11.12.2007 23:28 Bernhard Fischer said the following:
> Michael, please send me (in private if you prefer) your br2.config and your
> uClibc.config so i can try to reproduce this error here.
I attached the two configs to this mail.
Please note that I did one modification to buildroot. I had to add back
the possibility to select 2.6.10 kernel again. I have not tried yet to
create buildroot against a later kernel, but I'll try now and let you
know the results.
> Please note that this doesn't look like it's really uClibc related but a
> buildroot issue.
I did not notice that the original post was sent to uclibc ML rather
than buildroot ML. I changed the CC now to the buildroot ML. Thanks for
the hint.
CU
Michael.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: br2.config
Url: http://busybox.net/lists/buildroot/attachments/20071217/b5f84e90/attachment.diff
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: uclibc.config
Url: http://busybox.net/lists/buildroot/attachments/20071217/b5f84e90/attachment-0001.diff
next parent reply other threads:[~2007-12-17 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3ed55890710300456o715fd332x1f5d8bf466a54882@mail.gmail.com>
[not found] ` <14021271.post@talk.nabble.com>
[not found] ` <475E8C8E.5090402@linuxtv.org>
[not found] ` <20071211222816.GI17973@aon.at>
2007-12-17 8:47 ` Michael Hunold [this message]
2007-12-17 9:14 ` [Buildroot] error when building gcc using buildroot/toolchain Michael Hunold
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=476637A3.6010906@linuxtv.org \
--to=hunold@linuxtv.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