From: Nigel Kukard <nkukard@lbsd.net>
To: buildroot@busybox.net
Subject: [Buildroot] patches ...
Date: Tue, 18 Mar 2008 12:56:10 +0000 [thread overview]
Message-ID: <1205844970.23833.13.camel@nigel-x60> (raw)
1. confusing busybox config option description patch, busybox can be
built as shared libs, hardlinks ... etc. rename to full install.
2. kernel 2.6.24 creates a symlink to bzImage, which is copied inplace,
symlink and all, this gives an incorrect symlink deref in
binaries/uclibc/ and points to ../../x86/bzImage. Do not copy symlink in
place, follow it.
3. Ltrace version changed, cannot find the old version on any debian
mirrors.
-N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: busybox-confusing-config-option.patch
Type: text/x-patch
Size: 1369 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20080318/48d24fa2/attachment.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: deref-kernel-image.patch
Type: text/x-patch
Size: 550 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20080318/48d24fa2/attachment-0001.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ltrace-update.patch
Type: text/x-patch
Size: 586 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20080318/48d24fa2/attachment-0002.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://busybox.net/lists/buildroot/attachments/20080318/48d24fa2/attachment.pgp
reply other threads:[~2008-03-18 12:56 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=1205844970.23833.13.camel@nigel-x60 \
--to=nkukard@lbsd.net \
--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