From: Randy Dunlap <randy.dunlap@oracle•com>
To: Boaz Harrosh <bharrosh@panasas•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for November 18
Date: Tue, 14 Dec 2010 13:59:17 -0800 [thread overview]
Message-ID: <20101214135917.5b5a73e5.randy.dunlap@oracle.com> (raw)
In-Reply-To: <4CE92F96.7000002@panasas.com>
On Sun, 21 Nov 2010 16:41:26 +0200 Boaz Harrosh wrote:
> On 11/19/2010 01:33 AM, Stephen Rothwell wrote:
> > Hi Boaz,
> >
> > On Thu, 18 Nov 2010 17:25:22 +0200 Boaz Harrosh <bharrosh@panasas•com> wrote:
> >>
> >> The uml build from:
> >> http://kisskb.ellerman.id.au/kisskb/target/2979/
> >>
> >> is failing compilation like:
> >> LD .tmp_vmlinux1
> >> /opt/crosstool/gcc-4.2.3-glibc-2.3.6/i386-unknown-linux-gnu/lib/gcc/i386-unknown-linux-gnu/4.2.3/../../../../i386-unknown-linux-gnu/bin/ld:arch/um/kernel/vmlinux.lds:231: parse error
> >> collect2: ld returned 1 exit status
> >> KSYM .tmp_kallsyms1.S
> >> /opt/crosstool/gcc-4.2.3-glibc-2.3.6/i386-unknown-linux-gnu/bin/i386-unknown-linux-gnu-nm: '.tmp_vmlinux1': No such file
> >> No valid symbol.
> >> make[1]: *** [.tmp_kallsyms1.S] Error 1
> >> make: *** [sub-make] Error 2
> >> make failed, trying to bisect ..
> >>
> >> It looks like a build environment setup problem because it's fine here
> >> (for x86_64 at least.) Who is the person responsible for the above URL
> >> compilation please?
> >
> > I am (at least partially) responsible for that build environment.
> >
> > We only started getting that build failure with next-20101115 (it may
> > have been present before then but masked by other build failures), and
> > our build system hasn't changed in quite some time ... In fact, before
> > next-20100915, the um i386 build used to succeed.
> >
> > The build we are doing is 32 bit (not 64 bit). We are in the process of
> > getting a newer tool chain, but I am not sure when that will happen.
>
> Hi Stephen, thank you for your reply
>
> So... Every x86_64 box is also a potential of an x86_32 cross compilation
> environment, right?. Almost because for instance in Fedora 12 I had to:
> yum install glibc-devel.i686
> for it to work (On top of the regular Kernel development packages)
>
> So I tried:
> []$ make ARCH=um SUBARCH=i386 KBUILD_OUTPUT=.build_i386_um defconfig
> []$ make ARCH=um SUBARCH=i386 KBUILD_OUTPUT=.build_i386_um
>
> And it all worked very nice just as with x86_64.
> What is you box environment? Distro, Arch, version of gcc-for-i386 ...?
> I would like to help resolve it. Since I decided that I should be watching
> out for ARCH=um, before breakage is put into Linus tree, like the last 4
> Kernels.
>
> Meanwhile I have setup a cron job for every-night to checkout linux-next
> and "make". As a backup for above, until it is fixed.
>
> Anything else I can contribute to this cause?
>From my small testing, it looks like ARCH=um "defconfig" is about the only
config that comes close to building reliably. allmodconfig/allyesconfig and
several randconfig attempts all failed with many horrible errors.
Is that about right?
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-12-14 21:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 2:42 linux-next: Tree for November 18 Stephen Rothwell
2010-11-18 15:25 ` Boaz Harrosh
2010-11-18 23:33 ` Stephen Rothwell
2010-11-21 14:41 ` Boaz Harrosh
2010-12-14 21:59 ` Randy Dunlap [this message]
2010-12-15 12:47 ` Boaz Harrosh
2010-11-18 17:25 ` linux-next: Tree for November 18 (netfilter) Randy Dunlap
2010-11-18 18:32 ` Patrick McHardy
2010-11-22 12:14 ` KOVACS Krisztian
2010-11-22 12:28 ` KOVACS Krisztian
2010-11-22 16:19 ` Randy Dunlap
2010-12-15 22:55 ` Patrick McHardy
2010-11-19 11:46 ` linux-next: Tree for November 18 Zimny Lech
-- strict thread matches above, loose matches on Subject: below --
2009-11-18 6:23 Stephen Rothwell
2008-11-18 6:17 Stephen Rothwell
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=20101214135917.5b5a73e5.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=bharrosh@panasas$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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