From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Yuri Frolov <yfrolov@ru.mvista.com>,
rep.dot.nop@gmail.com, linuxppc-dev@lists.ozlabs.org,
linux-kbuild@vger.kernel.org
Subject: Re: [patch] powerpc: build modules outside the kernel tree fails, if it was built using O=
Date: Sat, 26 Sep 2009 07:57:32 +1000 [thread overview]
Message-ID: <1253915852.7103.531.camel@pasglop> (raw)
In-Reply-To: <20090925194557.GA3323@merkur.ravnborg.org>
On Fri, 2009-09-25 at 21:45 +0200, Sam Ravnborg wrote:
> On Thu, Sep 24, 2009 at 03:28:11PM +0400, Yuri Frolov wrote:
> > Hello,
> >
> > here is a corresponding bug: http://bugzilla.kernel.org/show_bug.cgi?id=11143
> > This patch should correctly export crtsavres.o in order to make O= option working.
> > Please, consider to apply.
>
> Hi Yuri.
>
> I like the way you do the extra link in Makefile.modpost.
> But you need to redo some parts as per comments below.
> >
> > Fix linking modules against crtsavres.o
>
> Please elaborate more on what this commit does.
It's a support file that needs to be linked against every module
(aka libgcc like) and thus needs to be built before any module.
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: rep.dot.nop@gmail.com, Yuri Frolov <yfrolov@ru.mvista.com>,
linuxppc-dev@lists.ozlabs.org, linux-kbuild@vger.kernel.org
Subject: Re: [patch] powerpc: build modules outside the kernel tree fails, if it was built using O=
Date: Sat, 26 Sep 2009 07:57:32 +1000 [thread overview]
Message-ID: <1253915852.7103.531.camel@pasglop> (raw)
In-Reply-To: <20090925194557.GA3323@merkur.ravnborg.org>
On Fri, 2009-09-25 at 21:45 +0200, Sam Ravnborg wrote:
> On Thu, Sep 24, 2009 at 03:28:11PM +0400, Yuri Frolov wrote:
> > Hello,
> >
> > here is a corresponding bug: http://bugzilla.kernel.org/show_bug.cgi?id=11143
> > This patch should correctly export crtsavres.o in order to make O= option working.
> > Please, consider to apply.
>
> Hi Yuri.
>
> I like the way you do the extra link in Makefile.modpost.
> But you need to redo some parts as per comments below.
> >
> > Fix linking modules against crtsavres.o
>
> Please elaborate more on what this commit does.
It's a support file that needs to be linked against every module
(aka libgcc like) and thus needs to be built before any module.
Cheers,
Ben.
next prev parent reply other threads:[~2009-09-25 21:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 11:28 [patch] powerpc: build modules outside the kernel tree fails, if it was built using O= Yuri Frolov
2009-09-24 11:28 ` Yuri Frolov
2009-09-25 1:12 ` Benjamin Herrenschmidt
2009-09-25 1:12 ` Benjamin Herrenschmidt
2009-09-25 4:39 ` Sam Ravnborg
2009-09-25 4:39 ` Sam Ravnborg
2009-09-25 9:39 ` Yuri Frolov
2009-09-25 9:39 ` Yuri Frolov
2009-09-25 19:45 ` Sam Ravnborg
2009-09-25 19:45 ` Sam Ravnborg
2009-09-25 21:57 ` Benjamin Herrenschmidt [this message]
2009-09-25 21:57 ` Benjamin Herrenschmidt
2009-09-25 22:01 ` Sam Ravnborg
2009-09-25 22:01 ` Sam Ravnborg
2009-09-26 12:45 ` Yuri Frolov
2009-09-26 12:45 ` Yuri Frolov
2009-09-30 13:50 ` Yuri Frolov
2009-09-30 13:50 ` 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=1253915852.7103.531.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rep.dot.nop@gmail.com \
--cc=sam@ravnborg.org \
--cc=yfrolov@ru.mvista.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.