From: Daniel Ng <daniel_ng11@lycos.com>
To: buildroot@busybox.net
Subject: [Buildroot] Changing the mk file in a package
Date: Thu, 15 Feb 2007 04:32:39 +0000 (UTC) [thread overview]
Message-ID: <loom.20070215T051448-924@post.gmane.org> (raw)
Hi,
I'm adding a new package to buildroot. Following the standard docco I add a new
package directory and the relevant config.in and xxx.mk file.
I've noticed that if I make changes to xxx.mk I have to do a 'make clean' then
a 'make' ie. a full rebuild. Otherwise if I just try to run 'make' after
changing xxx.mk, I get the following error from fakeroot-
# Use fakeroot so mkcramfs believes the previous fakery
/home/dng/linuxppc/gcc-4.0.2_uclibc/usr/bin/fakeroot \
-i /home/dng/linuxppc/gcc-4.0.2_uclibc/fakeroot.env \
-s /home/dng/linuxppc/gcc-4.0.2_uclibc/fakeroot.env -- \
/home/ppcroot/swdev/buildroot-dng/build_powerpc/cramfs-1.1/mkcramfs -q -
b \
/home/ppcroot/swdev/buildroot-
dng/build_powerpc/root /home/ppcroot/swdev/buildroot-dng/rootfs.powerpc.cramfs
Swapping filesystem endian-ness
mkcramfs: mmap failed: /home/ppcroot/swdev/buildroot-
dng/build_powerpc/root/usr/usr/local
make: *** [cramfsroot] Error 8
-but my new package has nothing to do with mmap!
If I do a full rebuild, I don't get the above problem. But the fully rebuild
takes about 30 minutes! Is there a way to get a more sensible 'make' behaviour,
so that I can avoid having to do these full rebuilds?
Cheers,
Daniel
next reply other threads:[~2007-02-15 4:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 4:32 Daniel Ng [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-16 0:20 [Buildroot] changing the mk file in a package Daniel Ng
2007-02-16 7:15 ` Philippe Ney
2007-02-16 7:32 ` Alexander Rigbo
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=loom.20070215T051448-924@post.gmane.org \
--to=daniel_ng11@lycos.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