From: Segher Boessenkool <segher@kernel.crashing.org>
To: Mariusz Kozlowski <m.kozlowski@tuxland.pl>
Cc: linux-usb-devel@lists.sourceforge.net, gregkh@suse.de,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
paulus@samba.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: 2.6.23-rc1-mm2
Date: Tue, 7 Aug 2007 01:12:00 +0200 [thread overview]
Message-ID: <14f932ea857d563d409cc10b570fc085@kernel.crashing.org> (raw)
In-Reply-To: <200708070034.19193.m.kozlowski@tuxland.pl>
>> It seems like things go wrong when lparmap.s is generated with
>> (DWARF) debug info; could you try building it (manually) with -g0
>> added on the end of the compile line, and see if head_64.o compiles
>> okay for you then? If so, I'll prepare a proper patch for it, I
>> have a similar one (also for lparmap!) in my queue already...
>
> Ok it worked. I had to add -g0 to Makefile under arch/powerpc/kernel
> because
> -g0 was added before -g and didn't have any effect when adding to
> Makefile
> in top dir.
Yeah, that's why I said "build lparmap.s manually" :-)
> But yes - it compiles now.
Great, I'll combine it with my other lparmap build patch then.
Thanks for the report and testing!
Segher
prev parent reply other threads:[~2007-08-06 23:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070731230932.a9459617.akpm@linux-foundation.org>
2007-08-01 8:02 ` 2.6.23-rc1-mm2 Mariusz Kozlowski
2007-08-01 8:13 ` 2.6.23-rc1-mm2 Andrew Morton
2007-08-01 8:16 ` 2.6.23-rc1-mm2 Ingo Molnar
2007-08-01 10:32 ` 2.6.23-rc1-mm2 Paul Mackerras
2007-08-02 10:14 ` 2.6.23-rc1-mm2 Mariusz Kozlowski
2007-08-03 9:39 ` 2.6.23-rc1-mm2 Kumar Gala
2007-08-06 19:12 ` 2.6.23-rc1-mm2 Segher Boessenkool
2007-08-06 19:10 ` 2.6.23-rc1-mm2 Segher Boessenkool
2007-08-01 16:36 ` 2.6.23-rc1-mm2 Greg KH
2007-08-06 19:08 ` 2.6.23-rc1-mm2 Segher Boessenkool
2007-08-06 19:34 ` 2.6.23-rc1-mm2 Mariusz Kozlowski
2007-08-06 21:25 ` 2.6.23-rc1-mm2 Segher Boessenkool
2007-08-06 22:34 ` 2.6.23-rc1-mm2 Mariusz Kozlowski
2007-08-06 23:12 ` Segher Boessenkool [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=14f932ea857d563d409cc10b570fc085@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=m.kozlowski@tuxland.pl \
--cc=paulus@samba.org \
/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).