From: Ingo Molnar <mingo@elte.hu>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
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:00:22 +0100 [thread overview]
Message-ID: <20090320100021.GB6256@elte.hu> (raw)
In-Reply-To: <20090320092410.30d2bac3@osiris.boeblingen.de.ibm.com>
* Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> On Fri, 20 Mar 2009 10:42:08 +1100
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > The linux-next build for s390 allnoconfig failed like this:
> >
> > In file included from arch/s390/include/asm/tlb.h:29,
> > from arch/s390/mm/pgtable.c:25:
> > arch/s390/include/asm/smp.h:95: error: redefinition of 'smp_send_stop'
> > include/linux/smp.h:125: error: previous definition of 'smp_send_stop' was here
> >
> > Caused by commit d1dedb52acd98bd5e13e1ff4c4d045d58bbd16fe ("panic, smp:
> > provide smp_send_stop() wrapper on UP too") from the tip-core tree.
>
> Ingo, could you pick up the patch below?
Applied, thanks guys!
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....
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
and i use:
CROSS="CROSS_COMPILE=$ARCH-linux-"
make O=$BUILDDIR $CROSS ARCH=$ARCH mrproper defconfig
where ARCH=s390 in this case.
Ingo
next prev parent reply other threads:[~2009-03-20 10:00 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 [this message]
2009-03-20 10:33 ` Heiko Carstens
-- 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=20090320100021.GB6256@elte.hu \
--to=mingo@elte.hu \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--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).