Skip to contentSkip to conversation

Building for ARM

Buildroot Brian C. Lane 2 participants 4 messages Aug 12, 2006 – Aug 13, 2006

lore
Share & tools
lore
#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I am trying to build a basic system for ARM to use with qemu. I have successfully doen this for i386 so all the tools are in place.

1. I configured buildroot for armeb and the ARM926 processor and then built the basic filesystem and tools (I have also tried with arm instead of armeb).

2. I configured kernel 2.6.12.6 for ARM (make ARCH="arm" menuconfig) and selected Versatile for the ARM system type (qemu supports this and Integrator)

3. I added the buildroot tools to the beginning of the path and try to compile the kernel with:

export PATH=../buildroot/build_armeb/staging_dir/bin:$PATH make CROSS-COMPILE="armeb-linux-" ARCH="arm" bzImage

I get this result:

CC arch/arm/kernel/asm-offsets.s
cc1: error: invalid option ?little-endian?
cc1: error: invalid option ?apcs?
cc1: error: invalid option ?no-sched-prolog?
cc1: error: invalid option ?abi=apcs-gnu? arch/arm/kernel/asm-offsets.c:1: error: bad value (armv4) for -march= switch arch/arm/kernel/asm-offsets.c:1: error: bad value (arm9tdmi) for -mtune= switch

It is acting like the compiler doesn't support arm, but I obviously set the PATH and CROSS-COMPILE to point to the buildroot tools.

Does anyone have any idea of what I'm doing wrong? I've also done a bunch of googleing and haven't come up with a decent howto for building a basic system (coverage of uclibc, busybox and buildroot are great, but none seem to talk about the kernel).

Thanks,

Brian

- --
- ---[Office 72.2F]--[Outside 70.8F]--[Server 86.2F]--[Coaster 72.2F]---
Linux Software Developer http://www.brianlane.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Remember Lexington Green!

iD8DBQFE3mUMIftj/pcSws0RAgc5AJ9vYQKixGR9Irk/b7prQBOUIaDECgCghMwO nrXIo1CQoMItua5NvuEwNWw=
=+r66
-----END PGP SIGNATURE-----

#1 lore raw

:??o???jp?jw?rV????jw??l+???!?]y?ay???????h?[-??^m?"?x??????Z??v????(???z?^???z\"?????<???????????)]j??o?-j???????<??? ?H#?<??j??nX??v??????"?????.???j?!????G???j??}???sW?????????)?*'?+m???v&?q?^??+?{??'h?????\??5z???)?jX???b?y???^v????sW?????????)?*'i?

#2 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 6 lines · Ed Swierk
Quoted 5 lines · Brian C. Lane

3. I added the buildroot tools to the beginning of the path and try to compile the kernel with:

export PATH=../buildroot/build_armeb/staging_dir/bin:$PATH make CROSS-COMPILE="armeb-linux-" ARCH="arm" bzImage

[snip]

Quoted 5 lines

Not sure if this is the cause of your problem, but adding a relative pathname to PATH doesn't seem like a good idea. Try PATH=$(pwd)/../buildroot/build_armeb/staging_dir/bin:$PATH instead.

Very good point. I've switched to using an absolute path.

Quoted 8 lines
Quoted 4 lines

Does anyone have any idea of what I'm doing wrong? I've also done a bunch of googleing and haven't come up with a decent howto for building a basic system (coverage of uclibc, busybox and buildroot are great, but none seem to talk about the kernel).

The various kernel makefiles under the targets directory are instructive; I created a fairly generic linux kernel makefile based on those. See the attached patch if you want to try it out for yourself.

Thanks for the patch -- After changing your ppc references to arm it almost works :) It compiles most of the kernel without complaint but is now stopping in rtc-lib.c with a complaint about cmpxchg:

drivers/built-in.o: In function `drm_lock_take':
rtc-lib.c:(.text+0x86920): undefined reference to cmpxchg' drivers/built-in.o: In function drm_lock_free':

I probably don't have the kernel configured quite right.

Brian

- --
- ---[Office 71.6F]--[Outside 83.5F]--[Server 85.4F]--[Coaster 71.5F]---
Linux Software Developer http://www.brianlane.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Remember Lexington Green!

iD8DBQFE32lfIftj/pcSws0RAtSKAJwKzm6zGo/0Euxylr3w6xBMHRJPRgCcDzS6 A+BKy6/fZWaPMoLt+0O2wGs=
=HxY/
-----END PGP SIGNATURE-----

#3 lore raw
In reply to Brian C. Lane

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 3 lines · Brian C. Lane

export PATH=../buildroot/build_armeb/staging_dir/bin:$PATH make CROSS-COMPILE="armeb-linux-" ARCH="arm" bzImage

This should have been CROSS_COMPILE with an underscore. But even with that it wasn't compiling correctly, until I discovered the defconfig make targets. Using the versatile_defconfig target worked. Now I just have to get qemu to run it without crashing.

Thanks for the help,

Brian

- --
- ---[Office 73.1F]--[Outside 75.4F]--[Server 86.8F]--[Coaster 73.1F]---
Linux Software Developer http://www.brianlane.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Remember Lexington Green!

iD8DBQFE36rVIftj/pcSws0RAhD8AJ9DQtZ9jg909CTe44gq8B+Gt5DvBACZAWix UbVuZcN/XN2YIG4MrXReIRY=
=8We5
-----END PGP SIGNATURE-----