From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Problem building avahi
Date: Thu, 06 Jan 2011 14:19:47 +0100 [thread overview]
Message-ID: <87aajegoek.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20110106135549.7f6ef437@surf> (Thomas Petazzoni's message of "Thu, 6 Jan 2011 13:55:49 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
Thomas> Ok, good. At least this has exhibited an interesting bug of
Thomas> Buildroot that we'll have to fix.
>>
>> Yeah.
Thomas> Something like "grep -v" the lines that have already been changed to
Thomas> start with $(STAGING_DIR)/usr ?
We could simply skip lines that already contain STAGING_DIR/usr - E.G.
$(SED) -e '/$(subst /,\/,$(STAGING_DIR)/usr)/b' -e "s:\(['= ]\)/usr:..
>> For such a special situation, I would prefer to we tell users to do it
>> with BR2_ROOTFS_POST_BUILD_SCRIPT instead.
Thomas> On x86, it's fairly usual to have the kernel inside the root
Thomas> filesystem, and embedded x86 systems are quite common. So this
Thomas> feature could be seen as sufficiently useful to be integrated
Thomas> into BR.
But u-boot on x86 isn't common, right?
Thomas> Something like:
Thomas> config BR2_LINUX_KERNEL_INSTALL_TO_ROOTFS
Thomas> bool "Install kernel image in rootfs"
Thomas> default y if BR2_i386 || BR2_x86_64
Thomas> help
Thomas> Copy the generated kernel image to the /boot directory
Thomas> in the root filesystem
Ahh, for non-uImage stuff - Yes, that's fine.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2011-01-06 13:19 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
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 [this message]
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=87aajegoek.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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