From: Alessandro Amici <lists@b-open-solutions.it>
To: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: massive cross-builds without too much PITA
Date: Thu, 28 Oct 2004 18:21:22 +0200 [thread overview]
Message-ID: <200410281821.22486.lists@b-open-solutions.it> (raw)
In-Reply-To: <20041028054833.GP24336@parcelfarce.linux.theplanet.co.uk>
Al,
I happen to be learning how to cross-compile on Debian right now, so i can
testify that building the cross toolchain 'The Debian Way' is even easier
than you describe ;).
On Thursday 28 October 2004 07:48, Al Viro wrote:
> Building cross-toolchain is surprisingly easy these days; I'm using debian
> on build boxen and cross-compilers are not hard to do:
> apt-get build-dep binutils
> apt-get build-dep gcc-3.3
> apt-get install dpkg-cross
> apt-get source binutils
> get binutils-cross-... patch from bugs.debian.org/231707
> cd binutils-...
> apply patch
> TARGET=<target>-linux fakeroot debian/rules binary-cross
> cd ..
> dpkg -i binutils-<target>-....deb
> got linux-kernel-headers, libc6, libc6-dev and libdb1-compat for target
> dpkg-cross -a <target> -b on all of those
> dpkg -i resulting packages
> apt-get source gcc-3.3
> cd gcc-3.3-...
> GCC_TARGET=<gcc_target> debian/rules control
> GCC_TARGET=<gcc_target> debian/rules build
> GCC_TARGET=<gcc_target> fakeroot debian/rules binary
> cd ..
> dpkg -i resulting packages.
> One note: <target> here is debian platform name (e.g. ppc), but
> <gcc_target> is *gcc* idea of what that bugger is called (e.g. powerpc).
>
> IIRC, Nikita Youshchenko had pre-built debs somewhere, but they were not
> for the host I'm using (amd64/sid).
The package toolchain-source (together with dpkg-cross) makes the process even
more automatic. Detailed instructions are at:
http://people.debian.org/~debacle/cross.html
The short story is:
# apt-get toolchain-source dpkg-cross autoconf2.13 fakeroot
# tpkg-install-libc <terget>-linux # grabs, converts and install the headers
$ tpkg-make <target>-linux # no need to patch anything
$ cd binutils...
$ debuild -us -uc # no magic env variables
# dpkg -i ../binutils...deb
$ cd ../gcc...
$ debuild -us -uc
# dpkg -i ../gcc...deb
If I'm not mistaken, that's all.
> In practical terms it means no ppc64.
Sadly right! guess which platform I needed to cross compile :-/
Cheers,
Alessandro
next prev parent reply other threads:[~2004-10-28 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 5:48 massive cross-builds without too much PITA Al Viro
2004-10-28 11:36 ` Geert Uytterhoeven
2004-10-28 15:56 ` Kalin KOZHUHAROV
2004-10-28 16:58 ` Al Viro
2004-10-28 17:28 ` Geert Uytterhoeven
2004-10-28 16:21 ` Alessandro Amici [this message]
2004-10-28 16:52 ` Al Viro
2004-10-31 6:29 ` Herbert Poetzl
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=200410281821.22486.lists@b-open-solutions.it \
--to=lists@b-open-solutions.it \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.