From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org, sam@ravnborg.org
Subject: Re: [PATCH] Fix linking modules against crtsavres.o
Date: Thu, 16 Oct 2008 18:15:31 +0200 [thread overview]
Message-ID: <20081016161531.GA5299@mx.loc> (raw)
In-Reply-To: <547FA711-EB43-4F0A-B69D-AE7C9557AC37@kernel.crashing.org>
On Thu, Oct 16, 2008 at 11:07:27AM -0500, Kumar Gala wrote:
>
> On Oct 16, 2008, at 10:24 AM, Grant Likely wrote:
>
>> On Thu, Oct 09, 2008 at 09:51:25PM +0200, Bernhard Reutner-Fischer
>> wrote:
>>> Hi,
>>>
>>> [ http://bugzilla.kernel.org/show_bug.cgi?id=11143 has it all]
>> This patch solves the problem for me. Without it building modules
>> before the kernel proper fails to find crtsavres.o when linking.
I did not install the .o nor it's prerequisites so only fixed building
modules in tree. For building external modules these
LDFLAGS_MODULE_PREREQ would need to be installed too, as noted by Olaf
in the bug. I do not need them to be installed myself, so please take
care of it if you have time to do so.
>> Ben, Paul or Sam, could you please look at this and make comment
>> if it is the right approach?
>>
>> I also agree that this should be back ported to the stable series
>>
>> (Note: for some reason this patch did *not* show up in patchwork).
>
> because it was sent as an attachment.
Indeed. Sorry for that..
next prev parent reply other threads:[~2008-10-16 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 19:51 [PATCH] Fix linking modules against crtsavres.o Bernhard Reutner-Fischer
2008-10-16 15:24 ` Grant Likely
2008-10-16 16:07 ` Kumar Gala
2008-10-16 16:15 ` Bernhard Reutner-Fischer [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-23 19:36 Yuri Frolov
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=20081016161531.GA5299@mx.loc \
--to=rep.dot.nop@gmail.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sam@ravnborg.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).