From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] Can not build toolchain for arm.
Date: Mon, 22 Oct 2007 23:27:53 +1000 [thread overview]
Message-ID: <20071022132753.GA27339@cloud.net.au> (raw)
In-Reply-To: <471C7798.3030005@sfktech.com>
On Mon, Oct 22, 2007 at 12:12:40PM +0200, Kim Str?ger wrote:
> Kuten Ivan wrote:
> > Kim Str?ger wrote:
> >> I am trying to build just the toolchain for the arm processor, using
> >> buildroot: At revision 20315
> >> but I am stock with this error ??
> >>
> >> /home/cz2/Crossdev/buildroot/toolchain_build_arm/gcc-4.2.1/libmudflap/mf-runtime.c:2124:
> >> error: '__mf_biglock' undeclared (first use in this function)
> >> make[5]: *** [pth/mf-runtime.lo] Error 1
> >> make[5]: Leaving directory
> >> `/home/cz2/Crossdev/buildroot/toolchain_build_arm/gcc-4.2.1-final/arm-linux-uclibc/libmudflap'
> >
> > Please provide your .config
> > I have built 4.2.1 armv4 920t with soft-float and without soft-float successfully.
> my .config
How about config.log from somewhere in
/home/cz2/Crossdev/buildroot/toolchain_build_arm/gcc-4.2.1-final/arm-linux-uclibc/libmudflap ?
I built gcc-4.2.1 + armeb + soft-float + oabi last week ok.
Did you tweak your uClibc configuration at all, eg to disabling
threading?
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2007-10-22 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-21 12:02 [Buildroot] svn commit: trunk/buildroot/package/lsof vanokuten at uclibc.org
2007-10-22 9:53 ` [Buildroot] Can not build toolchain for arm Kim Strøger
2007-10-22 12:01 ` Kuten Ivan
2007-10-22 10:12 ` Kim Strøger
2007-10-22 13:27 ` Hamish Moffatt [this message]
2007-10-24 11:18 ` [Buildroot] Can not build toolchain for arm or armed Kim Strøger
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=20071022132753.GA27339@cloud.net.au \
--to=hamish@cloud.net.au \
--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