Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Koenraad lelong <buildroot@de-brouwerij.be>
To: buildroot@busybox.net
Subject: [Buildroot] Known working versions ?
Date: Thu, 14 Dec 2006 20:54:51 +0100	[thread overview]
Message-ID: <4581AC0B.9000307@de-brouwerij.be> (raw)
In-Reply-To: <F38DEABE0E171746B133C1ABBD142D97060DC057@radmail.Radstone.Local>

Martyn Welch schreef:
> Hi Koenraad,
> 
> I've been having the same problems.
> 
> I found that busybox would fail with "Implicit declaration of 'bzero'"
> in tar.c. I decided to try rebuilding with tar disabled in the busybox
> configuration. It compiled, but then when I tried the image, busybox
> seemed to be mistaking 'init' for hdparm, infact everything I tried
> seemed to be mistaken for hdparm!
> 
> I managed to get the image to aleast get to a prompt by building bash
> into the image. I'm currently trying a build without busybox to see if I
> can get a larger image working with buildroot.
> 
> If it's any help, I've set buildroot to use:
> 
> Gcc 3.4.6
> Bunutils 2.16.91.0.7
> Linux 2.6.19
> Yesterdays (11 Dec06) snapshots of Busybox and uClibc.
> 
> Martyn 
> 
...
Thanks for your suggestions. In the meantime I started from scratch, did 
a checkout again and then did "make defconfig", which I found in a post 
from the mailinglist. Now "make" completes successfully.
I'm going to explore further.
Thanks again,
Koenraad Lelong.

  reply	other threads:[~2006-12-14 19:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 11:31 [Buildroot] Known working versions ? Martyn Welch
2006-12-14 19:54 ` Koenraad lelong [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-12 10:09 Koenraad lelong
2006-12-12 10:50 ` Bernhard Fischer

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=4581AC0B.9000307@de-brouwerij.be \
    --to=buildroot@de-brouwerij.be \
    --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