From: Nathan Chancellor <nathan@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, llvm@lists.linux.dev
Subject: Re: [arm-integrator:virt-to-pfn-v6.0-rc1 21/24] ld.lld: error: arch/powerpc/kernel/vdso/vdso32.lds:244: unknown directive: static
Date: Thu, 8 Sep 2022 08:13:22 -0700 [thread overview]
Message-ID: <YxoGkuNPskaWQgFE@dev-arch.thelio-3990X> (raw)
In-Reply-To: <CACRpkdZ29j9rzv5XkKvSKw-o4nzL7oAPdhhpfbOBTqPiSC9KUg@mail.gmail.com>
On Thu, Sep 08, 2022 at 02:28:49PM +0200, Linus Walleij wrote:
> On Tue, Sep 6, 2022 at 4:41 PM Nathan Chancellor <nathan@kernel.org> wrote:
> >
> > + Linus
> >
> > This shouldn't be clang/ld.lld specific
>
> Hmmmm dunno if it is related to the compiler, I have fixed up the patches
> I am working on in this branch and pushed it again. Maybe I fixed something
> about the powerpc, don't remember.
>
> I am essentially using the build robot as compile farm, I don't have the
> resources or time to keep all crosscompilers around neither machinery
> to do all these compiles...
With your latest branch:
$ make -skj"$(nproc)" ARCH=powerpc CROSS_COMPILE=powerpc64le-linux-gnu- mrproper powernv_defconfig arch/powerpc/kernel/vdso/
/usr/bin/powerpc64le-linux-gnu-ld:arch/powerpc/kernel/vdso/vdso64.lds:247: syntax error
It doesn't look like you surrounded virt_to_pfn() with an
'#ifndef __ASSEMBLY__', which will break inclusion of this file in
non-assembly sources (linker script is considered assembly for the sake
of preprocessing).
Cheers,
Nathan
next prev parent reply other threads:[~2022-09-08 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 15:23 [arm-integrator:virt-to-pfn-v6.0-rc1 21/24] ld.lld: error: arch/powerpc/kernel/vdso/vdso32.lds:244: unknown directive: static kernel test robot
2022-09-06 14:41 ` Nathan Chancellor
2022-09-08 12:28 ` Linus Walleij
2022-09-08 15:13 ` Nathan Chancellor [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-21 18:30 kernel test robot
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=YxoGkuNPskaWQgFE@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linus.walleij@linaro.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
/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).