From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Busybox 1.4.2 problems in latest buildroot
Date: Thu, 22 Mar 2007 21:34:56 +0100 [thread overview]
Message-ID: <02b401c76cc1$ad9ffde0$01c4af0a@Glamdring> (raw)
Whenever I rebuild, busybox tarball is downloaded !
Also, there is no busybox-1.4.2.config file
Would it not be a good idea the the busybox.config was
set by default to busybox-<version>.config
Best Regards
Ulf Samuelsson
reply other threads:[~2007-03-22 20:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='02b401c76cc1$ad9ffde0$01c4af0a@Glamdring' \
--to=ulf@atmel.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