From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] sysroot support in toolchain, use correct pathes in staging_dir
Date: Tue, 10 Apr 2007 12:39:01 +0200 [thread overview]
Message-ID: <20070410103901.GC15274@aon.at> (raw)
Hi,
This is a heads-up that i mean to correct the pathes to includes and
libs in the staging dir as suggested in bug
http://busybox.net/bugs/view.php?id=1290
Doing so is ment to ease moving the staging-dir (and it's
cross-compiler) to a different machine for re-use.
The theory of operation is that we aim to keep the positions of "normal"
desktop machines for the directory layout and also build the toolchain
with full sysroot-support to avoid trouble with hardcoded search pathes
to headers and libraries.
A preliminary incarnation which only takes care of gcc-4.x is here:
http://uclibc.org/~aldot/buildroot.mine.cow.20070406-1957.diff.bz2
(134688 Bytes)
diffstat:
toolchain/sstrip/sstrip.mk | 10
toolchain/binutils/binutils.mk | 38
toolchain/gcc/gcc-uclibc-3.x.mk | 6
toolchain/gcc/gcc-uclibc-4.x.mk | 451
toolchain/uClibc/uclibc.mk | 65
Config.in | 27
package/ncurses/ncurses.mk | 38
package/openssh/openssh.mk | 10
package/openssl/openssl.mk | 55
package/m4/m4.mk | 11
package/mpfr/mpfr.mk | 47
package/ltrace/ltrace-svn-20070406.01.autoreconf.patch | 5948 +++++
package/ltrace/ltrace.mk | 37
package/ltrace/ltrace-svn-20070406.00.patch |19000 +++++++++++++++++
package/Makefile.in | 54
package/zlib/zlib.mk | 56
package/gmp/gmp.mk | 49
Makefile | 7
18 files changed, 25681 insertions(+), 228 deletions(-)
The ltrace patch is not strictly related to the patch but i had to
pickup the latest version of it locally, fwiw.
next reply other threads:[~2007-04-10 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 10:39 Bernhard Fischer [this message]
2007-04-10 11:23 ` [Buildroot] [patch] sysroot support in toolchain, use correct pathes in staging_dir Heikki Lindholm
2007-04-10 12:08 ` Bernhard Fischer
2007-05-15 11:43 ` Bernhard Fischer
2007-06-20 11:36 ` Bernhard Fischer
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=20070410103901.GC15274@aon.at \
--to=rep.dot.nop@gmail.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