From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] uClibc/gcc build problems?
Date: Thu, 30 Nov 2006 17:51:43 +0100 [thread overview]
Message-ID: <20061130165143.GA2156@aon.at> (raw)
In-Reply-To: <456F0A76.9060501@computing.dundee.ac.uk>
On Thu, Nov 30, 2006 at 04:44:38PM +0000, Peter Mendham wrote:
>I am attempting to build buildroot revision 16738 (the latest at the
>time of writing) for a powerpc. It seems to hit a snag during the
>compilation of gcc. I don't think my configuration makes any difference
>at this stage of play, but if it does: I went with almost all the
>default options apart from software FP, I remooved the hdparm and sudo
>packages and added DHCP client support, I answered all of the prompts
>during make (is there an MMU etc.) with the default options. The
>relevant (I hope) portion of the output from the make is given below.
>
>I don't really know where to start with this. Any help greatly appreciated.
wrong list. Ping andersee on the uclibc list that he caused this with
r16733 ;)
meanwhile, svn diff -r16732:16733 | patch -R -p0
makes it compile again..
HTH,
prev parent reply other threads:[~2006-11-30 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 16:44 [Buildroot] uClibc/gcc build problems? Peter Mendham
2006-11-30 16:51 ` Bernhard Fischer [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=20061130165143.GA2156@aon.at \
--to=rep.nop@aon.at \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.