From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem building avahi
Date: Thu, 6 Jan 2011 12:32:38 +0100 [thread overview]
Message-ID: <20110106123238.1c227155@surf> (raw)
In-Reply-To: <D473AD103FC84CD18D1AF9AB6EAE9D2B@WSA.local>
On Thu, 6 Jan 2011 12:11:26 +0100
"Andreas Stahl" <a.stahl@wsa-electronic.de> wrote:
> I build in /usr/buildroot-2010.11 for some historical reason, but not
> as root. The buildroot directory belongs to the devel group and i'm a
> member of this group.
Ok, good. At least this has exhibited an interesting bug of Buildroot
that we'll have to fix.
> Ok, I now extracted buildroot to /opt/buildroot-2010.11 and everything
> works now. Thanks for that hint!
Great.
> Hmm, the uImage now is in output/images and got not copied to
> output/target/boot/ and is not in the rootfs.tar ?
No. On non-x86 embedded systems it's not very usual to have the kernel
image *inside* the root filesystem. It's usually flashed separatly from
the root filesystem image.
However, if there is demand for such a feature, we could certainly add
an option to the kernel build process.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-01-06 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 14:20 [Buildroot] Problem building avahi Andreas Stahl
2011-01-05 16:10 ` Thomas Petazzoni
2011-01-06 11:11 ` Andreas Stahl
2011-01-06 11:32 ` Thomas Petazzoni [this message]
2011-01-06 12:33 ` Peter Korsgaard
2011-01-06 12:55 ` Thomas Petazzoni
2011-01-06 13:19 ` Quotient Remainder
2011-01-06 13:19 ` Peter Korsgaard
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=20110106123238.1c227155@surf \
--to=thomas.petazzoni@free-electrons.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