Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Gaël PORTAY" <gael.portay@gmail.com>
Cc: "Samuel Martin" <s.martin49@gmail.com>,
	"Gaël PORTAY" <gael.portay@rtone.fr>,
	"Mahyar Koshkouei" <mahyar.koshkouei@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/rpi-userland: package is deprecated
Date: Thu, 25 Jul 2024 12:15:37 +0200	[thread overview]
Message-ID: <20240725121537.7f987369@windsurf> (raw)
In-Reply-To: <D2YJ1IQ4XJ62.17GIHGKSB1ZYE@gmail.com>

Hello Gaël,

On Thu, 25 Jul 2024 11:53:45 +0200
Gaël PORTAY <gael.portay@gmail.com> wrote:

> Well, I have no idea to be honest.
> 
> All I know for now is that I was able to make it works on pi5 with
> qt5webengine (v3d is supposed to support pi4/5, vc4 is supposed to
> support the former pi); but mesa cannot be built on pi 1/zero for now as
> it requires support for Neon and BCM2835 has no support for it.

Well, then we need to figure out this before declaring rpi-userland as
obsolete/deprecated. Indeed, not having support for the older RPi
platforms is a problem.

> But first, I am fixing the last issues with qt5webengine on ARM 32-bit
> using raspberrypi3_qt5we_defconfig and I am making the package more
> robust. I will sent the patch once I have the time to write the commit
> messages. And thank you very much for your fixes!

Yeah, I spent quite a lot of time during the recent Buildroot hackathon
to fix the build of qt5webengine. For ARM 32-bit, it was building
entirely all the way to point of linking QtWebEngine.so, where the
linker was simply returning an error (non zero exit code), but without
spitting any error message. I downgraded to an older version of
binutils just to check, and exact same behavior. I ran "strace" on the
linker, and it does write the libQtWebEngine.so file, apparently
entirely and then at some point it decides something is wrong, and it
deletes it and exits with an error. I couldn't figure out what was
happening.

Best regards,

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

  reply	other threads:[~2024-07-25 10:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23 21:20 [Buildroot] [PATCH 0/2] rpi-utils replaces rpi-userland Gaël PORTAY
2024-07-23 21:20 ` [Buildroot] [PATCH 1/2] package/rpi-utils: new package Gaël PORTAY
2024-07-24 16:21   ` Thomas Petazzoni via buildroot
2024-07-25  8:05     ` Gaël PORTAY
2024-07-25  8:10       ` Thomas Petazzoni via buildroot
2024-07-25  9:43         ` Gaël PORTAY
2024-07-25 10:05           ` Waldemar Brodkorb
2024-07-25 10:16             ` Thomas Petazzoni via buildroot
2024-07-25 10:21             ` Gaël PORTAY
2024-07-23 21:20 ` [Buildroot] [PATCH 2/2] package/rpi-userland: package is deprecated Gaël PORTAY
2024-07-24 16:21   ` Thomas Petazzoni via buildroot
2024-07-25  9:53     ` Gaël PORTAY
2024-07-25 10:15       ` Thomas Petazzoni via buildroot [this message]
2024-07-25 11:05         ` Gaël PORTAY
2024-07-25 14:59           ` Thomas Petazzoni via buildroot
2024-07-31 11:42             ` Gaël PORTAY

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=20240725121537.7f987369@windsurf \
    --to=buildroot@buildroot.org \
    --cc=gael.portay@gmail.com \
    --cc=gael.portay@rtone.fr \
    --cc=mahyar.koshkouei@gmail.com \
    --cc=s.martin49@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox