From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-next@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: linux-next: s390 build failure
Date: Fri, 20 Mar 2009 11:33:24 +0100 [thread overview]
Message-ID: <20090320113324.638a5cb8@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20090320100021.GB6256@elte.hu>
On Fri, 20 Mar 2009 11:00:22 +0100
Ingo Molnar <mingo@elte.hu> wrote:
> Btw., my cross-build scripts fail on s390 on latest -git, with:
>
> Assembler messages:
> FATAL: can't create scripts/mod/.tmp_empty.o: Invalid bfd target
> make[3]: *** [scripts/mod/empty.o] Error 2
> make[3]: *** Waiting for unfinished jobs....
Haven't seen this yet.
> have i made some mistake in setting them up? I have this cross build
> environment:
>
> aldebaran:~/linux/linux> /opt/crossgcc/cross/bin/s390-linux-gcc -v
> Using built-in specs.
> Target: s390-linux
> Configured with: /home/mingo/work/projects/crossgcc/gcc/configure
> --target=s390-linux --enable-targets=all
> --prefix=/opt/crossgcc/cross --enable-languages=c --without-headers
> --enable-sjlj-exceptions --with-system-libunwind --disable-nls
> --disable-threads --disable-shared --disable-libmudflap
> --disable-libssp --disable-libgomp --disable-decimal-float
> --enable-checking=release
> Thread model: single
> gcc version 4.3.3 20081123 (prerelease) (GCC)
> aldebaran:~/linux/linux> /opt/crossgcc/cross/bin/s390-linux-ld -v
> GNU ld (GNU Binutils) 2.19
ah, it's probably that you specified --target=s390-linux , that will
build a 32 bit compiler, not a 64 bit one. You probably want
s390x-ibm-linux. That gcc version can build both 32 and 64 bit binaries.
Latest cross compiler I have on my notebook that works:
heiko@osiris:~> s390x-ibm-linux-gcc-4.3.1 -v
Using built-in specs.
Target: s390x-ibm-linux
Configured with: ../gcc-4.3.1/configure --prefix=/home/heiko/cross/
--disable-nls --disable-checking --enable-languages=c
--target=s390x-ibm-linux --disable-threads --disable-shared
--without-headers --disable-libmudflap --disable-libssp
--disable-multilib --disable-libunwind-exceptions --disable-libgomp
--disable-werror --program-prefix=s390x-4.3.1-
Thread model: single gcc
version 4.3.1 (GCC)
heiko@osiris:~> s390x-4.3.1-ld -v
GNU ld (Linux/GNU Binutils) 2.19.51.0.1.20090106
> and i use:
>
> CROSS="CROSS_COMPILE=$ARCH-linux-"
>
> make O=$BUILDDIR $CROSS ARCH=$ARCH mrproper defconfig
>
> where ARCH=s390 in this case.
should work.
next prev parent reply other threads:[~2009-03-20 10:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 23:42 linux-next: s390 build failure Stephen Rothwell
2009-03-20 8:24 ` Heiko Carstens
2009-03-20 10:00 ` Ingo Molnar
2009-03-20 10:33 ` Heiko Carstens [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-19 23:53 Stephen Rothwell
2008-06-20 3:52 Stephen Rothwell
2008-06-20 7:58 ` Cornelia Huck
2008-06-23 15:22 ` Cornelia Huck
2008-06-23 22:13 ` Greg KH
2008-06-20 2:42 Stephen Rothwell
2008-06-20 11:42 ` Jens Axboe
2008-06-21 8:07 ` Heiko Carstens
2008-06-26 9:14 ` Jens Axboe
2008-06-20 11:51 ` Martin Schwidefsky
2008-05-12 8:03 Stephen Rothwell
2008-05-12 16:49 ` Greg KH
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=20090320113324.638a5cb8@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=schwidefsky@de.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).