From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Joel Stanley <joel@jms.id.au>
Cc: "Bernd Kuhls" <bernd.kuhls@t-online.de>,
"Cédric Le Goater" <clg@kaod.org>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/pixman: fix powerpc64le build
Date: Tue, 26 Jul 2022 22:19:49 +0200 [thread overview]
Message-ID: <20220726221949.73378442@windsurf> (raw)
In-Reply-To: <20220719102724.6adf0242@windsurf>
Hello Joel,
Do you have some updates on this pixman issue?
Thanks a lot!
Thomas Petazzoni
On Tue, 19 Jul 2022 10:27:24 +0200
Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote:
> Hello Joel,
>
> On Tue, 19 Jul 2022 07:46:03 +0000
> Joel Stanley <joel@jms.id.au> wrote:
>
> > There's a few build failures going around due to nonsense
> > configurations. In most cases the config has BR2_powerpc64le=y without
> > selecting a CPU.
>
> "Not selecting a CPU" is not possible. There is always a CPU within the:
>
> choice
> prompt "Target Architecture Variant"
> default BR2_generic_powerpc
> help
> Specific CPU variant to use
>
> ...
> endchoice
>
> that will be selected. However...
>
> > This defaults us to BR2_powerpc_970=y, which is a CPU
> > that isn't supported to run ppc64le.
>
> ... it seems like some of them are selectable on ppc64le, even though
> they do not make sense.
>
> > The fix is to only allow CPUs that support ppc64le to be configured
> > for that platform. I've prepared some patches that I'm running though
> > CI now, and I'll send them out once they're tested.
>
> Excellent! Looking forward to it!
>
> > If my changes don't fix this pixman issue then we can use the
> > BR2_POWERPC_CPU_HAS_ALTIVEC to force AltiVec/VMX off when we know the
> > CPU does not support it.
>
> But there's still a weird thing going on: pixman has a configure.ac
> check that compiles a small test program to verify if VMX support is
> available... and it concludes it is, but the actual pixman code then
> fails to build.
>
> Thanks for your feedback!
>
> Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-26 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 14:21 [Buildroot] [PATCH 1/1] package/pixman: fix powerpc64le build Bernd Kuhls
2022-07-18 12:14 ` Thomas Petazzoni via buildroot
2022-07-19 7:46 ` Joel Stanley
2022-07-19 8:27 ` Thomas Petazzoni via buildroot
2022-07-26 20:19 ` Thomas Petazzoni via buildroot [this message]
[not found] <20220708142150.234611-1-bernd.kuhls__17925.5718061299$1657290142$gmane$org@t-online.de>
2022-10-30 21:48 ` Bernd Kuhls
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=20220726221949.73378442@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd.kuhls@t-online.de \
--cc=clg@kaod.org \
--cc=joel@jms.id.au \
--cc=thomas.petazzoni@bootlin.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.