Re: Qt question: GNU_PROPERTY_1_NEEDED_INDIRECT_EXTERN_ACCESS

Ionen Wolkens <[email protected]> Sun, 19 Apr 2026 12:47:44 -0400
Newsgroups	gmane.linux.gentoo.devel
Message-ID	<aeUHMJAcRLFaEOrX@eversor>
On Sun, Apr 19, 2026 at 12:37:38PM -0400, Ionen Wolkens wrote:
> On Sun, Apr 19, 2026 at 05:13:26PM +0100, Sam James wrote:
> > Andrey Grozin <[email protected]> writes:
> > 
> > > Hello *,
> > >
> > > I'm trying to resurrect master-pdf-editor (this is a proprietary
> > > binary program, non-commercial use is allowed for free). The newest
> > > version 5.9.98 uses Qt6, not Qt5 like older versions. I've prepared an
> > > ebuild for this version (it RDEPENDS on very many libraries). But I
> > > get
> > >
> > > grozin@localhost ~/H4/corr4/yaf $ mpe5 lb0.pdf
> > > 13:09:47 19.04.26  Main:  Open one window: 1
> > > warning: direct reference to protected function
> > > `_ZN7QWidget11changeEventEP6QEvent' in `/usr/lib64/libQt6Widgets.so.6'
> > > may break pointer equality
> > > /opt/master-pdf-editor-5/masterpdfeditor5:
> > > _ZN7QWidget11changeEventEP6QEvent: /usr/lib64/libQt6Widgets.so.6:
> > > error due to GNU_PROPERTY_1_NEEDED_INDIRECT_EXTERN_ACCESS
> > >
> > > Googling GNU_PROPERTY_1_NEEDED_INDIRECT_EXTERN_ACCESS I see that many
> > > users have this problem, mostly on arch, e.g.
> > >
> > > https://github.com/slint-ui/slint/issues/7174
> > > https://github.com/PrismLauncher/PrismLauncher/issues/991
> > > https://qt-project.atlassian.net/browse/QTBUG-115261
> > > https://github.com/juzzlin/Heimer/issues/255
> > >
> > > It seems qtbase in Gentoo (and arch) is compiled in a way that makes
> > > it incompatible with binary programs compiled for other distros.
> > 
> > Qt upstream recommends we use this and I think they plan to make it the
> > default for Qt 7. It improves load time.
> > 
> > > Is there any way to overcome this problem? After a long struggle for a
> > > Qt6 version of master-pdf-editor we at last have it, but it does not
> > > run...
> > >
> > 
> > I don't have any ideas for a workaround other than using a Flatpak.
> 
> Actually kind of surprised this is the first time I hear of this
> considering we made the switch without rebuilding everything,
> meaning packages built against regular Qt started using it without
> a rebuild and didn't complain? Or am I missing something?
> 
> Think there are other prebuilts using it too, like google-chrome's
> qt6 plugin (is it broken?).
> 
> Maybe it's something specifically with how this was built like
> maybe it used a old binutils or something similar, not that we
> can do much about it either way.

Well, if could figure out exactly what makes it fail/work then
maybe could convince upstream to adjust their build. All kind of
a pain without the source to test though.

> 
> That aside I (personally) wouldn't think much of shipping bundled
> libraries if it's unusable with system's anyway.

-- 
ionen
signature.asc (application/pgp-signature, 525 B)