Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Brian C. Lane <bcl@brianlane.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building for ARM
Date: Sun, 13 Aug 2006 11:03:11 -0700	[thread overview]
Message-ID: <44DF695F.2010601@brianlane.com> (raw)
In-Reply-To: <c1bf1cf0608121653o1f5f4eb5y114c07b9889636d7@mail.gmail.com>

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

Ed Swierk wrote:
> On 8/12/06, Brian C. Lane <bcl@brianlane.com> wrote:
>> 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]

> 
> 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.


>> 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-----

  reply	other threads:[~2006-08-13 18:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-12 23:32 [Buildroot] Building for ARM Brian C. Lane
2006-08-12 23:53 ` Ed Swierk
2006-08-13 18:03   ` Brian C. Lane [this message]
2006-08-13 22:42 ` Brian C. Lane
  -- strict thread matches above, loose matches on Subject: below --
2006-08-13 15:37 NuNash

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=44DF695F.2010601@brianlane.com \
    --to=bcl@brianlane.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