LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Christian Zigotzky <chzigotzky@xenosoft.de>,
	Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Trevor Dickinson <rtd2@xtra.co.nz>,
	mad skateman <madskateman@gmail.com>,
	Darren Stevens <darren@stevens-zone.net>
Subject: Re: [FSL P50x0] [GIT KERNEL] [VDSO] compiling issue
Date: Fri, 20 Sep 2024 14:30:56 +1000	[thread overview]
Message-ID: <874j6bndz3.fsf@mail.lhotse> (raw)
In-Reply-To: <0C6E937D-A322-4B76-96E8-2C239241F049@xenosoft.de>

Christian Zigotzky <chzigotzky@xenosoft.de> writes:
> Hi All,
>
> The compiling of the latest Git kernel doesn’t work anymore for our FSL P5020/P5040 boards [1] since the random-6.12-rc1 updates [2].
>
> Error messages:
>
> arch/powerpc/kernel/vdso/vdso32.so.dbg: dynamic relocations are not supported
>
> make[2]: *** [arch/powerpc/kernel/vdso/Makefile:75: arch/powerpc/kernel/vdso/vdso32.so.dbg]
>
> Reverting of the vdso updates has solved the compiing issue.
>
> Could you please check the random-6.12-rc1 updates? [2]
>
> Thanks,
> Christian
>
> [1] http://wiki.amiga.org/index.php?title=X5000
>
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4a39ac5b7d62679c07a3e3d12b0f6982377d8a7d
>
> + Kernel config
>
> Link: https://raw.githubusercontent.com/chzigotzky/kernels/refs/heads/main/configs/x5000_defconfig

Your config has:

  # CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE is not set
  CONFIG_CC_OPTIMIZE_FOR_SIZE=y

But all our defconfigs use CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE. Which
explains why we didn't catch this in build testing. I've added a build
with OPTIMIZE_FOR_SIZE=y so hopefully we'll catch any similar errors in
future.

cheers


  parent reply	other threads:[~2024-09-20  4:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <de2d1e74-52e5-4d74-8228-4aaea61cad51@xenosoft.de>
2024-09-19 15:02 ` [FSL P50x0] [GIT KERNEL] [VDSO] compiling issue Christian Zigotzky
2024-09-19 15:15   ` Christophe Leroy
2024-09-20  4:30   ` Michael Ellerman [this message]
2024-09-20  4:39     ` Christophe Leroy
2024-09-19 12:29 Christian Zigotzky
2024-09-19 12:37 ` Christian Zigotzky

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=874j6bndz3.fsf@mail.lhotse \
    --to=mpe@ellerman.id.au \
    --cc=christophe.leroy@csgroup.eu \
    --cc=chzigotzky@xenosoft.de \
    --cc=darren@stevens-zone.net \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=madskateman@gmail.com \
    --cc=rtd2@xtra.co.nz \
    /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