From: Andrew Morton <akpm@osdl.org>
To: David Howells <dhowells@redhat.com>
Cc: Al Viro <viro@ftp.linux.org.uk>,
David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, axboe@suse.de
Subject: Re: linux/compat.h includes asm/signal.h causing problems
Date: Tue, 3 Oct 2006 10:01:36 -0700 [thread overview]
Message-ID: <20061003100136.e38553ff.akpm@osdl.org> (raw)
In-Reply-To: <12989.1159878079@warthog.cambridge.redhat.com>
On Tue, 03 Oct 2006 13:21:19 +0100
David Howells <dhowells@redhat.com> wrote:
> Al Viro <viro@ftp.linux.org.uk> wrote:
>
> > I do, it's not a problem...
>
> Actually, I was asking for myself. Can I grab a copy?
>
x86 binaries:
http://userweb.kernel.org/~akpm/sparc-cross.tar.bz2
http://userweb.kernel.org/~akpm/sparc64-cross.tar.bz2
script to run them:
#!/bin/sh
if [ x$ARCH == x ]
then
echo '$ARCH' unset
exit 1
fi
if [ x$J == x ]
then
J=256
fi
if [ x"$DISTCC_HOSTS" != x ]
then
DISTCC="distcc"
fi
XARCH="$ARCH-unknown-linux-gnu"
I=vmlinux
[ $ARCH = alpha ] && CT=gcc-4.1.0-glibc-2.3.6
[ $ARCH = arm ] && CT=gcc-3.4.5-glibc-2.3.6
[ $ARCH = i386 ] && CT=gcc-4.1.0-glibc-2.3.6 && XARCH=i686-unknown-linux-gnu && I=bzImage
[ $ARCH = ia64 ] && CT=gcc-3.4.5-glibc-2.3.6
[ $ARCH = m68k ] && CT=gcc-4.1.0-glibc-2.3.6
[ $ARCH = mips ] && CT=gcc-3.4.5-glibc-2.3.6
[ $ARCH = powerpc ] && CT=gcc-4.1.0-glibc-2.3.6 && XARCH=powerpc-405-linux-gnu
[ $ARCH = s390 ] && CT=gcc-4.1.0-glibc-2.3.6
[ $ARCH = sh ] && CT=gcc-3.4.5-glibc-2.3.6 && XARCH=sh4-unknown-linux-gnu
[ $ARCH = sparc ] && CT=gcc-4.1.0-glibc-2.3.6
[ $ARCH = sparc64 ] && CT=gcc-3.4.5-glibc-2.3.6
[ $ARCH = x86_64 ] && CT=gcc-4.0.2-glibc-2.3.6 && I=bzImage
[ $ARCH = parisc ] && CT=gcc-4.0.2-glibc-2.3.6 && I=bzImage
if [ $# -eq 0 ]
then
WHAT="$I modules"
else
WHAT="$*"
fi
PATH=$PATH:/opt/crosstool/$CT/$XARCH/bin export PATH
export CROSS_COMPILE=/opt/crosstool/$CT/$XARCH/bin/$XARCH-
export CC="$DISTCC /opt/crosstool/$CT/$XARCH/bin/$XARCH-gcc"
if [ "$ECHO" != "" ]
then
echo CROSS_COMPILE=$CROSS_COMPILE CC=\"$CC\" make -j$J $* CC=\"$CC\" $WHAT
else
nice -20 make -j$J $* CC="$CC" $WHAT 2>/tmp/log-$ARCH || FAILED=1
fi
cat /tmp/log-$ARCH
[ "$FAILED" != "" ] && echo "**FAILED**"
prev parent reply other threads:[~2006-10-03 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 20:14 David Miller
2006-10-02 20:50 ` Andrew Morton
2006-10-02 21:04 ` David Miller
2006-10-02 21:18 ` David Miller
2006-10-03 9:45 ` David Howells
2006-10-03 10:54 ` Al Viro
2006-10-03 12:21 ` David Howells
2006-10-03 17:01 ` Andrew Morton [this message]
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=20061003100136.e38553ff.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ftp.linux.org.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome