linux-kernel - cross-compilers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090408003921.GA5054@ldl.fc.hp.com>
Date:	Tue, 7 Apr 2009 18:39:21 -0600
From:	Alex Chiang <achiang@...com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-ia64@...r.kernel.org
Subject: cross-compilers

Hi Andrew,

I've been using your cross-compilers here:

	http://userweb.kernel.org/~akpm/cross-compilers/

for a long time now, but they're starting to suffer from a bit of
neglect.

For example, the ia64 bundle, which used gcc 3.4.5 is now finally
too old to build 2.6.30-rc1, because of a gcc bug related to
labels.

Some of the newer bundles which use gcc 4.1.0 don't work because
of a check in:

	include/linux/compiler-gcc4.h

So my question is, do you still use those tools hosted on
kernel.org or do you have a new solution these days?

If you have a new solution, I'd like to hear it, because I found
those cross-compilers pretty useful, as I'm sure others did.

I spent most of yesterday fiddling about and managed to build an
x86_64 host, ia64 target, gcc 4.2.3, glibc 2.3.6 bundle, and it
all seems to work.

Is this something you're interested in? I could send you my
tarball (and slowly work on some of the other archs).

If so, what were the crosstool build options you used? I'm
specifically wondering about:

	- should I am for lowest common denominator host or are
	  you ok with x86_64 host

	- did you statically link the toolchain? or is it
	  dynamically linked?

Thanks.

/ac

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/