From: "Kim Strøger" <ks@sfktech.com>
To: buildroot@busybox.net
Subject: [Buildroot] Can not build toolchain for arm or armed
Date: Wed, 24 Oct 2007 13:18:30 +0200 [thread overview]
Message-ID: <471F2A06.6060206@sfktech.com> (raw)
In-Reply-To: <20071022132753.GA27339@cloud.net.au>
Sorry for the delay....was out of the office for a bit.
Yes I did try to disable the threading, but then I got an error about an
abject neeeded threading, so I enable it again.
So once more I started all over. Just want to build the uclibc with
buildroot.
ARCH=armed
Threads=disable.
Kernel=none
Builtroot svn version: 20319
I have attach the full config file.
But I still end up with this.
make[2]: Leaving directory
`/home/cz2/Crossdev/buildroot/toolchain_build_armeb/gcc-4.2.1-initial/gcc'
make[1]: Leaving directory
`/home/cz2/Crossdev/buildroot/toolchain_build_armeb/gcc-4.2.1-initial'
touch
/home/cz2/Crossdev/buildroot/toolchain_build_armeb/gcc-4.2.1-initial/.installed
/usr/bin/make MAKE="/usr/bin/make -j1" -C
/home/cz2/Crossdev/buildroot/toolchain_build_armeb/uClibc-0.9.29 \
PREFIX= \
DEVEL_PREFIX=/ \
RUNTIME_PREFIX=/ \
HOSTCC="/usr/bin/gcc" \
all
make[1]: Entering directory
`/home/cz2/Crossdev/buildroot/toolchain_build_armeb/uClibc-0.9.29'
/usr/bin/gcc -DCURSES_LOC="<ncurses.h>" -DLOCALE -MM *.c > .depend
2>/dev/null || :
make[2]: `conf' is up to date.
CC ldso/ldso/ldso.oS
cc1: error: unrecognized command line option "-mfdpic"
make[1]: *** [ldso/ldso/ldso.oS] Error 1
make[1]: Leaving directory
`/home/cz2/Crossdev/buildroot/toolchain_build_armeb/uClibc-0.9.29'
make: ***
[/home/cz2/Crossdev/buildroot/toolchain_build_armeb/uClibc-0.9.29/lib/libc.a]
Error 2
Help......?????
Thanks, Kim S.
Hamish Moffatt wrote:
> 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
>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: .config
Url: http://busybox.net/lists/buildroot/attachments/20071024/01fd2705/attachment.diff
prev parent reply other threads:[~2007-10-24 11:18 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
2007-10-24 11:18 ` Kim Strøger [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=471F2A06.6060206@sfktech.com \
--to=ks@sfktech.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