From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Build errors on mainline kernel
Date: Sun, 11 Aug 2013 23:02:28 -0700 [thread overview]
Message-ID: <20130812060228.GA8608@us.ibm.com> (raw)
In-Reply-To: <1376286123.2066.7.camel@concordia>
Michael Ellerman [michael@ellerman.id.au] wrote:
| On Fri, 2013-08-09 at 11:24 -0700, Sukadev Bhattiprolu wrote:
| > I am tryng to compile clean mainline kernel with a few different config files
| > and running into errors with some configs.
| >
| > I am building on RHEL6.3 with following binaries:
| >
| > gcc (GCC) 4.4.6 20120305 (Red Hat 4.4.6-4)
| > GNU ld version 2.20.51.0.2-5.34.el6 20100205
| > binutils-2.20.51.0.2-5.34.el6.ppc64
| > binutils-devel-2.20.51.0.2-5.34.el6.ppc64
| >
| > I am getting the error with several files and configs, but other configs
| > (eg: ppc64_defconfig, pmac32_defconfig) build fine.
| >
| > For instance, with latest mainline kernel (commit 6c2580c) and ppc64_defconfig, I get:
|
| Here you say ppc64_defconfig ..
That was a stupid typo. ppc64_defconfig works.
|
| > make O=linux-obj mrproper
| > make O=linux-obj ppc64e_defconfig
|
| But here you say ppc64e_defconfig ?
ppc64e_defconfig fails (checked again now).
next prev parent reply other threads:[~2013-08-12 6:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 18:24 Build errors on mainline kernel Sukadev Bhattiprolu
2013-08-09 23:47 ` Kumar Gala
2013-08-10 1:01 ` Sukadev Bhattiprolu
[not found] ` <20130810010119.GA29407__43692.6458766267$1376096568$gmane$org@us.ibm.com>
2013-08-10 7:15 ` Andreas Schwab
2013-08-10 16:45 ` Sukadev Bhattiprolu
2013-08-10 17:47 ` Andreas Schwab
2013-08-12 5:42 ` Michael Ellerman
2013-08-12 6:02 ` Sukadev Bhattiprolu [this message]
2013-08-13 2:23 ` Michael Ellerman
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=20130812060228.GA8608@us.ibm.com \
--to=sukadev@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.au \
/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).