[Buildroot] native toolchain compilation problem

[Buildroot] native toolchain compilation problem

[William Brodie-Tyrrell]

Hi,

I'm using buildroot to build a linux system for the AT91SAM9G20-EK board and it's working fine except that I can't get it to build the native toolchain.  The cross-compiler works perfectly.

I'm using a patched v23434 from SVN as instructed by this website:
http://www.linux4sam.org/twiki/bin/view/Linux4SAM/BuildRootBuild

The error I'm getting is this:

arm-linux-uclibcgnueabi-gcc  -O2  -O2 -Os
-I/home/william/baes/at91sam9g20/buildroot/build_arm/staging_dir/usr/include
-I/home/william/baes/at91sam9g20/buildroot/build_arm/staging_dir/include
--sysroot=/home/william/baes/at91sam9g20/buildroot/build_arm/staging_dir/
-isysroot /home/william/baes/at91sam9g20/buildroot/build_arm/staging_dir
-mtune=arm9tdmi -msoft-float -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-D_FILE_OFFSET_BITS=64 -mfloat-abi=soft  -DIN_GCC    -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition  -isystem ./include  -fPIC -g
-DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  -I. -I.
-I/home/william/baes/at91sam9g20/buildroot/toolchain_build_arm_nofpu/gcc-4.2.4/gcc
-I/home/william/baes/at91sam9g20/buildroot/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/.
-I/home/william/baes/at91sam9g20/buildroot/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/../include
-I/home/william/baes/at91sam9g20/buildroot/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/../libcpp/include
-I/home/william/baes/at91sam9g20/buildroot/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/../libdecnumber
-I../libdecnumber -DL_eprintf -fvisibility=hidden -DHIDE_EXPORTS
-c /home/william/baes/at91sam9g20/buildroot/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/libgcc2.c
-o libgcc/./_eprintf.o

/home/william/baes/at91sam9g20/buildroot/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/libgcc2.c: In function '__eprintf':
/home/william/baes/at91sam9g20/buildroot/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/libgcc2.c:1973: warning: implicit declaration of function 'fprintf'
/home/william/baes/at91sam9g20/buildroot/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/libgcc2.c:1973: warning: incompatible implicit declaration of built-in function 'fprintf'
/home/william/baes/at91sam9g20/buildroot/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/libgcc2.c:1973: error: 'stderr' undeclared (first use in this function)
/home/william/baes/at91sam9g20/buildroot/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/libgcc2.c:1973: error: (Each undeclared identifier is reported only once
/home/william/baes/at91sam9g20/buildroot/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/libgcc2.c:1973: error: for each function it appears in.)
/home/william/baes/at91sam9g20/buildroot/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/libgcc2.c:1974: warning: implicit declaration of function 'fflush'
make[4]: *** [libgcc/./_eprintf.o] Error 1
make[4]: Leaving directory `/home/william/baes/at91sam9g20/buildroot/build_arm/gcc-4.2.4-target/gcc'


Looks to me like the gcc build process somehow doesn't see the built uclibc (no fprintf, no stderr) - is there something I need to change to fix that?


thanks,

-- 
William Brodie-Tyrrell

Carpe Diem - fish of the day.

<william@brodie-tyrrell.org>
http://www.brodie-tyrrell.org/

[Buildroot] native toolchain compilation problem

[Peter Korsgaard]

>>>>> "William" == William Brodie-Tyrrell <william@brodie-tyrrell.org> writes:

 William> Hi,

 William> I'm using buildroot to build a linux system for the
 William> AT91SAM9G20-EK board and it's working fine except that I
 William> can't get it to build the native toolchain.  The
 William> cross-compiler works perfectly.

 William> I'm using a patched v23434 from SVN as instructed by this website:
 William> http://www.linux4sam.org/twiki/bin/view/Linux4SAM/BuildRootBuild

 William> The error I'm getting is this:

Hmm, 23434 is half a year old, and we have had various toolchain fixes
since then. Could you try with svn head?

-- 
Bye, Peter Korsgaard

[Buildroot] native toolchain compilation problem

[William Brodie-Tyrrell]

On Wed, 25 Feb 2009 10:28:13 +0100
Peter Korsgaard <jacmet@uclibc.org> wrote:

> Hmm, 23434 is half a year old, and we have had various toolchain fixes
> since then. Could you try with svn head?

OK, I'll give it a go.  Will it be sufficient to copy over my .config
and run make oldconfig or something like that?


-- 
William Brodie-Tyrrell

Carpe Diem - fish of the day.

<william@brodie-tyrrell.org>
http://www.brodie-tyrrell.org/

[Buildroot] native toolchain compilation problem

[Peter Korsgaard]

>>>>> "William" == William Brodie-Tyrrell <william@brodie-tyrrell.org> writes:

Hi,

 >> Hmm, 23434 is half a year old, and we have had various toolchain fixes
 >> since then. Could you try with svn head?

 William> OK, I'll give it a go.  Will it be sufficient to copy over my .config
 William> and run make oldconfig or something like that?

Yes, that should be fine (depending on what that atmel patch does).

-- 
Bye, Peter Korsgaard

[Buildroot] gcc compilation issues on AT91SAM9G20

[William Brodie-Tyrrell]

OK, so I'm trying to build the latest (downloaded SVN HEAD version last
night) version of buildroot because v23434 (as indicated on
linux4sam.org) doesn't want to build a native toolchain.

The problem I'm having now is two-fold.  Firstly, the following line
appears in my .config when I run make menuconfig:
BR2_GCC_TARGET_ABI="aapcs-linux"
It causes gcc's configuration process to choke and complain about an
unknown ABI.  If I comment that out, delete the gcc build directory and
run make again, it all proceeds until I get this error:

arm-linux-uclibcgnueabi-gcc  -O2  -O2 -Os -pipe -O2
-I/home/william/baes/at91sam9g20/buildroot-head/build_arm/staging_dir/usr/include
-I/home/william/baes/at91sam9g20/buildroot-head/build_arm/staging_dir/include
--sysroot=/home/william/baes/at91sam9g20/buildroot-head/build_arm/staging_dir/
-isysroot /home/william/baes/at91sam9g20/buildroot-head/build_arm/staging_dir
-mtune=arm9tdmi -msoft-float -mfloat-abi=soft  -DIN_GCC    -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition  -isystem ./include  -fPIC -g
-DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  -I. -I.
-I/home/william/baes/at91sam9g20/buildroot-head/toolchain_build_arm_nofpu/gcc-4.2.4/gcc
-I/home/william/baes/at91sam9g20/buildroot-head/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/.
-I/home/william/baes/at91sam9g20/buildroot-head/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/../include
-I/home/william/baes/at91sam9g20/buildroot-head/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/../libcpp/include
-I/home/william/baes/at91sam9g20/buildroot-head/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/../libdecnumber
-I../libdecnumber -DL_eprintf -fvisibility=hidden -DHIDE_EXPORTS
-c /home/william/baes/at91sam9g20/buildroot-head/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/libgcc2.c
-o libgcc/./_eprintf.o

/home/william/baes/at91sam9g20/buildroot-head/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/libgcc2.c: In function '__eprintf':
/home/william/baes/at91sam9g20/buildroot-head/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/libgcc2.c:1973: warning: implicit declaration of function 'fprintf'
/home/william/baes/at91sam9g20/buildroot-head/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/libgcc2.c:1973: warning: incompatible implicit declaration of built-in function 'fprintf'
/home/william/baes/at91sam9g20/buildroot-head/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/libgcc2.c:1973: error: 'stderr' undeclared (first use in this function)
/home/william/baes/at91sam9g20/buildroot-head/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/libgcc2.c:1973: error: (Each undeclared identifier is reported only once
/home/william/baes/at91sam9g20/buildroot-head/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/libgcc2.c:1973: error: for each function it appears in.)
/home/william/baes/at91sam9g20/buildroot-head/toolchain_build_arm_nofpu/gcc-4.2.4/gcc/libgcc2.c:1974: warning: implicit declaration of function 'fflush'
make[4]: *** [libgcc/./_eprintf.o] Error 1
make[4]: Leaving directory `/home/william/baes/at91sam9g20/buildroot-head/build_arm/gcc-4.2.4-target/gcc'

Any ideas?


thanks...

-- 
William Brodie-Tyrrell

Carpe Diem - fish of the day.

<william@brodie-tyrrell.org>
http://www.brodie-tyrrell.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090226/e508b5e6/attachment.pgp>

[Buildroot] gcc compilation issues on AT91SAM9G20

[Peter Korsgaard]

>>>>> "William" == William Brodie-Tyrrell <william@brodie-tyrrell.org> writes:

Hi,

 William> OK, so I'm trying to build the latest (downloaded SVN HEAD
 William> version last night) version of buildroot because v23434 (as
 William> indicated on linux4sam.org) doesn't want to build a native
 William> toolchain.

 William> The problem I'm having now is two-fold.  Firstly, the
 William> following line appears in my .config when I run make
 William> menuconfig: BR2_GCC_TARGET_ABI="aapcs-linux"

Are you trying an EABI or OABI build? The aapcs-linux stuff is for
EABI.

 William> thanks...

We don't have a defconfig for that specific board in BR, but I just
tried the at91sam9g20dfc defconfig where I added "native toolchain in
the target filesystem", and that builds without problems.

Could you post your .config?

-- 
Bye, Peter Korsgaard

[Buildroot] gcc compilation issues on AT91SAM9G20

[William Brodie-Tyrrell]

On Fri, 27 Feb 2009 10:15:27 +0100
Peter Korsgaard <jacmet@uclibc.org> wrote:

> Are you trying an EABI or OABI build? The aapcs-linux stuff is for
> EABI.

EABI, though not for any particular reason other than that's what the
linux4sam-provided .config does. The gcc configure only works if I
leave the BR2_GCC_TARGET_ABI line out of the .config. The cross
compiler (when it's working) is called arm-linux-uclibcgnueabi-gcc so
perhaps I should put linux-uclibcgnueabi in the BR2_GCC_TARGET_ABI?

> We don't have a defconfig for that specific board in BR, but I just
> tried the at91sam9g20dfc defconfig where I added "native toolchain in
> the target filesystem", and that builds without problems.
> 
> Could you post your .config?

It's attached.  It's entirely possible there's something that the
linux4sam patches do that is missing from this fresh build I'm doing,
but I don't know nearly enough about buildroot to spot it.  I copied in
my old/working .config and local/AT91 directory and ran 'make oldconfig'
to update the .config.

PS: when one gets a fresh copy of HEAD from SVN, the scripts/wget.sh
file is missing.


thanks,

-- 
William Brodie-Tyrrell

Carpe Diem - fish of the day.

<william@brodie-tyrrell.org>
http://www.brodie-tyrrell.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.gz
Type: application/x-gzip
Size: 4651 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090227/a4167faa/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090227/a4167faa/attachment-0001.pgp>

[Buildroot] gcc compilation issues on AT91SAM9G20

[Peter Korsgaard]

>>>>> "William" == William Brodie-Tyrrell <william@brodie-tyrrell.org> writes:
 >> Are you trying an EABI or OABI build? The aapcs-linux stuff is for
 >> EABI.

Hi,

 William> EABI, though not for any particular reason other than that's
 William> what the linux4sam-provided .config does. The gcc configure
 William> only works if I leave the BR2_GCC_TARGET_ABI line out of the
 William> .config. The cross compiler (when it's working) is called
 William> arm-linux-uclibcgnueabi-gcc so perhaps I should put
 William> linux-uclibcgnueabi in the BR2_GCC_TARGET_ABI?

OK, the other at91sam* defconfigs in BR all seems to use OABI. I'll
check EABI.

 >> Could you post your .config?

 William> It's attached.  It's entirely possible there's something
 William> that the linux4sam patches do that is missing from this
 William> fresh build I'm doing, but I don't know nearly enough about
 William> buildroot to spot it.  I copied in my old/working .config
 William> and local/AT91 directory and ran 'make oldconfig' to update
 William> the .config.

OK, I'll take a look at it.

 William> PS: when one gets a fresh copy of HEAD from SVN, the scripts/wget.sh
 William> file is missing.

Ehh, that's because we don't have a wget.sh (and never had) - Where do
you see any references to a wget.sh?

-- 
Bye, Peter Korsgaard

[Buildroot] gcc compilation issues on AT91SAM9G20

[William Brodie-Tyrrell]

On Fri, 27 Feb 2009 11:37:25 +0100
Peter Korsgaard <jacmet@uclibc.org> wrote:

> OK, the other at91sam* defconfigs in BR all seems to use OABI. I'll
> check EABI.

OK, I'll give OABI a go.

> Ehh, that's because we don't have a wget.sh (and never had) - Where do
> you see any references to a wget.sh?

When I run make, it seems to use that to download the sources.  If it's not there, make fails while trying to download sources.  On second-look, it seems that the .config file provided by linux4sam has this line in it:

BR2_WGET="$(TOPDIR)/scripts/wget.sh $(BR2_WGET_MIRROR) --passive-ftp --retry-connrefused --waitretry=10"

So you can ignore me complaining about that...


thanks,

-- 
William Brodie-Tyrrell

Carpe Diem - fish of the day.

<william@brodie-tyrrell.org>
http://www.brodie-tyrrell.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090227/086d40c4/attachment.pgp>

[Buildroot] gcc compilation issues on AT91SAM9G20

[Peter Korsgaard]

>>>>> "William" == William Brodie-Tyrrell <william@brodie-tyrrell.org> writes:

 >> Ehh, that's because we don't have a wget.sh (and never had) - Where do
 >> you see any references to a wget.sh?

 William> When I run make, it seems to use that to download the sources.  If it's not there, make fails while trying to download sources.  On second-look, it seems that the .config file provided by linux4sam has this line in it:

 William> BR2_WGET="$(TOPDIR)/scripts/wget.sh $(BR2_WGET_MIRROR) --passive-ftp --retry-connrefused --waitretry=10"

Ahh, that must be from the atmel patch. I think I remember something
about a wget.sh in HcE's avr32 tree.

delete the BR2_WGET line in your .config and run make oldconfig and it
should be fixed.

-- 
Bye, Peter Korsgaard