From: Ned Ludd <solar@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] x86 cross devkit
Date: Sun, 18 Jun 2006 09:47:12 -0400 [thread overview]
Message-ID: <1150638433.23050.30.camel@localhost> (raw)
I have many testing environments. In one of those testing environments
I build every cross compiler known to compile. While talking with a
user yesterday I asked if having a multiarch devkit would be useful. He
said yeah. So what I've packed up a generic stage and overlaid all the
cross compilers,headers,debuggers etc/portage setting and the such.
The development environment includes support the following CTARGETS.
alpha-gentoo-linux-uclibc
alpha-unknown-linux-gnu
arm-gentoo-linux-uclibc
arm-softfloat-linux-gnu
arm-softfloat-linux-uclibc
arm-unknown-linux-gnu
armeb-gentoo-linux-uclibc
armeb-softfloat-linux-gnu
armeb-softfloat-linux-uclibc
armeb-unknown-linux-gnu
avr
bfin-elf
bfin-uclinux
cris-gentoo-linux-uclibc
dvp
ee
hppa-unknown-linux-gnu
hppa1.1-unknown-linux-gnu
hppa2.0-unknown-linux-gnu
hppa64-unknown-linux-gnu
i386-gentoo-linux-uclibc
i386-pc-linux-gnu
i686-gentoo-linux-uclibc
ia64-unknown-linux-gnu
iop
m68k-gentoo-linux-uclibc
m68k-unknown-linux-gnu
mips-gentoo-linux-uclibc
mips-unknown-linux-gnu
mips64-unknown-linux-gnu
mips64el-unknown-linux-gnu
mipsel-gentoo-linux-uclibc
mipsel-unknown-linux-gnu
msp430
nios2-elf
nios2-uclinux
powerpc-gentoo-linux-uclibc
powerpc-softfloat-linux-gnu
powerpc-softfloat-linux-uclibc
powerpc-unknown-linux-gnu
powerpc64-unknown-linux-gnu
s390-ibm-linux-gnu
s390x-ibm-linux-gnu
sh-gentoo-linux-uclibc
sh-unknown-linux-gnu
sh4-gentoo-linux-uclibc
sh4-unknown-linux-gnu
sh4eb-gentoo-linux-uclibc
sh4eb-unknown-linux-gnu
sheb-gentoo-linux-uclibc
sheb-unknown-linux-gnu
sparc-gentoo-linux-uclibc
sparc-unknown-linux-gnu
sparc64-unknown-linux-gnu
x86_64-gentoo-linux-uclibc
x86_64-pc-linux-gnu
----------------------------------------
Of those these combos thsee are known to work reasonable well in
my testing with only mips/sh4 being a bit funky in that
everything that you compile links with lib libgcc_s.so.1
alpha-unknown-linux-gnu
arm-gentoo-linux-uclibc
arm-softfloat-linux-uclibc
arm-unknown-linux-gnu
armeb-gentoo-linux-uclibc
armeb-softfloat-linux-uclibc
armeb-unknown-linux-gnu
avr
i386-gentoo-linux-uclibc
i386-pc-linux-gnu
i686-gentoo-linux-uclibc
m68k-gentoo-linux-uclibc
m68k-unknown-linux-gnu
mips-gentoo-linux-uclibc
mips-unknown-linux-gnu
mipsel-gentoo-linux-uclibc
mipsel-unknown-linux-gnu
powerpc-gentoo-linux-uclibc
powerpc-softfloat-linux-uclibc
powerpc-unknown-linux-gnu
powerpc64-unknown-linux-gnu
s390-ibm-linux-gnu
s390x-ibm-linux-gnu
sh4-gentoo-linux-uclibc
sh4-unknown-linux-gnu
sh4eb-gentoo-linux-uclibc
sh4eb-unknown-linux-gnu
sparc-unknown-linux-gnu
sparc64-unknown-linux-gnu
x86_64-pc-linux-gnu
----------------------------------------
You can fetch the 542M tarball from here
http://tinderbox.dev.gentoo.org/misc/cross/x86-cross-devkit-20060617.tar.bz2
If anybody finds this useful I can push these generic devkits
from time to time.
--
Ned Ludd <solar@gentoo.org>
Gentoo Linux
--
gentoo-embedded@gentoo.org mailing list
reply other threads:[~2006-06-18 13:48 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=1150638433.23050.30.camel@localhost \
--to=solar@gentoo.org \
--cc=gentoo-embedded@lists.gentoo.org \
/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