linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	"R.T.Dickinson" <rtd2@xtra.co.nz>,
	mad skateman <madskateman@gmail.com>,
	Darren Stevens <darren@stevens-zone.net>
Subject: [FSL P50x0] [GIT KERNEL] [VDSO] compiling issue
Date: Thu, 19 Sep 2024 14:37:15 +0200	[thread overview]
Message-ID: <e88a2c52-a163-47f0-80a4-1ba7c99d251b@xenosoft.de> (raw)
In-Reply-To: <f6f41112-e9ee-4cc5-b487-74e82e866e94@xenosoft.de>

On 19 September 2024 at 2:29 pm, Christian Zigotzky wrote:
> 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



  reply	other threads:[~2024-09-20  0:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 12:29 [FSL P50x0] [GIT KERNEL] [VDSO] compiling issue Christian Zigotzky
2024-09-19 12:37 ` Christian Zigotzky [this message]
     [not found] <de2d1e74-52e5-4d74-8228-4aaea61cad51@xenosoft.de>
2024-09-19 15:02 ` Christian Zigotzky
2024-09-19 15:15   ` Christophe Leroy
2024-09-20  4:30   ` Michael Ellerman
2024-09-20  4:39     ` 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=e88a2c52-a163-47f0-80a4-1ba7c99d251b@xenosoft.de \
    --to=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;
as well as URLs for NNTP newsgroup(s).