From: Christian Eggers <wgnetz@freenet.de>
To: buildroot@busybox.net
Subject: [Buildroot] Tool building problem EABI+PXA270
Date: Fri, 20 Mar 2009 07:49:32 +0100 [thread overview]
Message-ID: <200903200749.32358.wgnetz@freenet.de> (raw)
>Try the following changes, thing work fine here for me, also with
>gcc-4.3.2 built for PXA270/300.
>
>> # Automatically generated make config: don't edit
>> # Tue Mar 17 13:25:58 2009
>
>[...]
>
>> BR2_xscale=y
>> # BR2_iwmmxt is not set
>> BR2_ARM_TYPE="ARM_XSCALE"
>> # BR2_ARM_OABI is not set
>> BR2_ARM_EABI=y
>> BR2_ARCH="arm"
>> BR2_ENDIAN="LITTLE"
>> BR2_GCC_TARGET_TUNE="xscale"
>> BR2_GCC_TARGET_ABI="aapcs-linux"
>
># BR2_xscale is not set
>BR2_iwmmxt=y
>BR2_ARM_TYPE="ARM_IWMMXT"
># BR2_ARM_OABI is not set
>BR2_ARM_EABI=y
>BR2_ARCH="arm"
>BR2_ENDIAN="LITTLE"
>BR2_GCC_TARGET_TUNE="iwmmxt"
>BR2_GCC_TARGET_ARCH="iwmmxt"
/home/christian/buildroot-r25712/toolchain_build_arm/gcc-4.3.3/libgcc/../gcc/crtstuff.c: In function '__do_global_dtors_aux':
/home/christian/buildroot-r25712/toolchain_build_arm/gcc-4.3.3/libgcc/../gcc/crtstuff.c:306: error: '__DTOR_LIST__' undeclared (first use in this function)
/home/christian/buildroot-r25712/toolchain_build_arm/gcc-4.3.3/libgcc/../gcc/crtstuff.c:306: error: (Each undeclared identifier is reported only once
/home/christian/buildroot-r25712/toolchain_build_arm/gcc-4.3.3/libgcc/../gcc/crtstuff.c:306: error: for each function it appears in.)
make[2]: *** [crtbegin.o] Fehler 1
make[2]: Leaving directory `/home/christian/buildroot-r25712/toolchain_build_arm/gcc-4.3.3-initial/arm-linux-uclibc/libgcc'
make[1]: *** [all-target-libgcc] Fehler 2
make[1]: Leaving directory `/home/christian/buildroot-r25712/toolchain_build_arm/gcc-4.3.3-initial'
make: *** [/home/christian/buildroot-r25712/toolchain_build_arm/gcc-4.3.3-initial/.compiled] Fehler 2
I've the same problem building an ARM EABI toolchain. The GCC build error happens with buildroot-2009.02 (gcc-4.3.2) and current SVN (25712, gcc-4.3.3). The
result is equal for xscale, iwmmxt and arm920t.
Ater each change in menuconfg I've deleted the toolchain_build_arm/ subdir. Is this sufficient?
regards
Christian
next reply other threads:[~2009-03-20 6:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 6:49 Christian Eggers [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-18 11:23 [Buildroot] Tool building problem EABI+PXA270 Per-Henrik Lundblom
2009-03-18 11:47 ` Daniel Mack
2009-03-18 12:25 ` Per-Henrik Lundblom
2009-03-18 12:30 ` Daniel Mack
[not found] ` <20090318131349.GD27893@whatever.nu>
2009-03-18 13:25 ` Daniel Mack
2009-03-18 14:25 ` Per-Henrik Lundblom
2009-03-18 14:46 ` Daniel Mack
2009-03-18 15:53 ` Per-Henrik Lundblom
2009-03-19 8:39 ` Daniel Mack
2009-03-24 12:37 ` Per-Henrik Lundblom
2009-03-24 13:11 ` Daniel Mack
2009-03-24 13:19 ` Per-Henrik Lundblom
2009-03-24 13:29 ` Daniel Mack
2009-03-24 13:53 ` Per-Henrik Lundblom
2009-03-24 14:39 ` Daniel Mack
2009-03-24 14:46 ` Per-Henrik Lundblom
2009-03-18 12:31 ` Sven Neumann
2009-03-18 13:09 ` Per-Henrik Lundblom
[not found] ` <37c712e0903180742k6dbee6a4q48e3a4e023089e0@mail.gmail.com>
2009-03-18 14:54 ` Per-Henrik Lundblom
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=200903200749.32358.wgnetz@freenet.de \
--to=wgnetz@freenet.de \
--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