From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [RPi4] Enable GTK3 on Buildroot
Date: Wed, 2 Jun 2021 22:26:32 +0200 [thread overview]
Message-ID: <20210602222632.73390af3@gmx.net> (raw)
In-Reply-To: <20210602112346.472e95a5@windsurf.home>
Hello Derek,
On Wed, 2 Jun 2021 11:23:46 +0200, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Hello,
>
> On Tue, 1 Jun 2021 15:21:29 -0600
> Derek T <derek.tata1@gmail.com> wrote:
>
> > I am trying to enable GTK3 on Buildroot to deploy to a Raspberry Pi 4, and
> > having trouble initializing the Xorg server with an HDMI display. The
> > persistent error seems to be an undefined symbol while loading
> > fbturbo_drv.so. I tried manually loading the libraries in the config file,
> > which helped with some of the undefined symbol errors, but the symbol
> > "fbdevHWSave" has continued to throw an error. I have a Weston daemon
> > running on the device, and on boot a desktop screen shows up on the
> > display.
>
> If you already have Weston up and running, why are you not using the
> Wayland backend of Gtk3 ? It seems more logical than trying to get
> X.org working.
Despite the suggestion that there are better solutions than fbturbo on RPi4
your problem should be fixed by the buildroot patch
'[v1] package/x11r7/xdriver_xf86-video-fbturbo: fix driver loading' (see [1])...,
thanks for providing the buildroot config file to reproduce the failure...
Regards,
Peter
[1] https://patchwork.ozlabs.org/project/buildroot/patch/20210602201529.6210-1-ps.report at gmx.net/
>
> Best regards,
>
> Thomas
next prev parent reply other threads:[~2021-06-02 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 21:21 [Buildroot] [RPi4] Enable GTK3 on Buildroot Derek T
2021-06-02 9:23 ` Thomas Petazzoni
2021-06-02 20:26 ` Peter Seiderer [this message]
2021-06-02 20:35 ` Arnout Vandecappelle
2021-06-03 14:27 ` Derek T
2021-06-06 8:11 ` Yann E. MORIN
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=20210602222632.73390af3@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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