Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Austin <brian.austin@cirrus.com>
To: buildroot@busybox.net
Subject: [Buildroot] EABI toolchains do not free init in busybox
Date: Tue, 15 May 2007 06:15:41 -0500	[thread overview]
Message-ID: <1179227741.17486.52.camel@localhost.localdomain> (raw)

Hello,

I have been building gcc-4.1.1, 4.1.2, 4.2 toolchains for ARM9 EABI with
2.6.20.4 kernel headers from buildroot. I am using daily snapshots of
uClibc as well.

I have tried busybox 1.2.0, 1.4.1, and 1.5.0,  same results.

the files are built in EABI format as well

they build fine and compile all lf my code and generate a ramdisk.

kernel boots, but init does not let go and bring me to a shell.

Has anyone had any success with building EABI toolchains for ARM9 from
buildroot?

I can post my uclibc and buildroot configs if needed.

Thanks,

Brian

             reply	other threads:[~2007-05-15 11:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 11:15 Brian Austin [this message]
2007-05-16  7:35 ` [Buildroot] EABI toolchains do not free init in busybox Konstantin Kletschke
2007-05-16  7:58   ` Brian Austin
     [not found] <00e301c79723$c1caa040$2600a8c0@engineering5>
2007-05-15 13:15 ` Brian Austin

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=1179227741.17486.52.camel@localhost.localdomain \
    --to=brian.austin@cirrus.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