From: Randy Dunlap <rdunlap@infradead.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
PowerPC <linuxppc-dev@lists.ozlabs.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: powerpc{32,64} randconfigs
Date: Tue, 27 Apr 2021 18:31:55 -0700 [thread overview]
Message-ID: <fe9e2c87-60fb-0f15-f9d9-17d70930ff9a@infradead.org> (raw)
In-Reply-To: <c973768b-8fe5-a5a4-ccfc-ebc109b6eb80@infradead.org>
On 4/20/21 11:45 PM, Randy Dunlap wrote:
> On 4/20/21 11:37 PM, Christophe Leroy wrote:
>>
>>
>> Le 21/04/2021 à 01:31, Randy Dunlap a écrit :
>>> --- linux-next-20210420.orig/arch/powerpc/kernel/vdso64/Makefile
>>> +++ linux-next-20210420/arch/powerpc/kernel/vdso64/Makefile
>>> @@ -30,7 +30,7 @@ ccflags-y := -shared -fno-common -fno-bu
>>> asflags-y := -D__VDSO64__ -s
>>> targets += vdso64.lds
>>> -CPPFLAGS_vdso64.lds += -P -C -U$(ARCH)
>>> +CPPFLAGS_vdso64.lds += -P -C -U$(SRCARCH)
>>
>> Maybe it would be better to do -Upowerpc like in VDSO32
>>
>
> OK, thanks for getting that done. :)
>
>>> # link rule for the .so file, .lds has to be first
>>> $(obj)/vdso64.so.dbg: $(src)/vdso64.lds $(obj-vdso64) $(obj)/vgettimeofday.o FORCE
>>> --- linux-next-20210420.orig/arch/powerpc/Makefile
Just to wrap this up, I got this method working also.
Thanks for all of your help, Christophe.
--
~Randy
next prev parent reply other threads:[~2021-04-28 1:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 23:31 powerpc{32,64} randconfigs Randy Dunlap
2021-04-21 6:03 ` Christophe Leroy
2021-04-21 6:12 ` Christophe Leroy
2021-04-21 6:37 ` Christophe Leroy
2021-04-21 6:45 ` Randy Dunlap
2021-04-28 1:31 ` Randy Dunlap [this message]
2021-04-21 7:15 ` Michael Ellerman
2021-04-21 10:08 ` Masahiro Yamada
2021-04-27 23:45 ` Randy Dunlap
2022-03-02 16:14 ` Christophe Leroy
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=fe9e2c87-60fb-0f15-f9d9-17d70930ff9a@infradead.org \
--to=rdunlap@infradead.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kbuild@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).