On 02.10.2020 20:33, Jeff Law wrote:
> I would suggest looking for any uses of -fPIE when compiling the C/C++
> sources. PIE allows local binding for some object acceses (and again,
> its local binding of objects that runs afoul of key aspects of the QT
> libraries).
Nothing here.
Full build
On 10/2/20 6:31 AM, Vitaly Zaitsev via devel wrote:
On 01.10.2020 22:48, Jeff Law wrote:
What you want to do to fix this is force -fPIC into the build flags.
That inhibits local symbol resolution and the copy relocs that are so
problematical for QT. You can see examples of how to do this in
On 10/2/20 10:01 AM, Jeff Law wrote:
On 10/2/20 6:31 AM, Vitaly Zaitsev via devel wrote:
On 01.10.2020 22:48, Jeff Law wrote:
What you want to do to fix this is force -fPIC into the build flags.
That inhibits local symbol resolution and the copy relocs that are so
problematical for QT. You
On 10/2/20 6:31 AM, Vitaly Zaitsev via devel wrote:
On 01.10.2020 22:48, Jeff Law wrote:
What you want to do to fix this is force -fPIC into the build flags.
That inhibits local symbol resolution and the copy relocs that are so
problematical for QT. You can see examples of how to do this in
On 01.10.2020 22:48, Jeff Law wrote:
> What you want to do to fix this is force -fPIC into the build flags.
> That inhibits local symbol resolution and the copy relocs that are so
> problematical for QT. You can see examples of how to do this in the
> clementine package.
Telegram Desktop
On 9/30/20 10:20 AM, Vitaly Zaitsev via devel wrote:
On 30.09.2020 15:39, Robert-André Mauchin wrote:
I have an issue with both Clementine and Strawberry (a fork of Clementine)
in F33 and above, users reported that disabling LTO fixes the problem.
I have the same issue with Telegram Desktop:
On 9/30/20 10:20 AM, Vitaly Zaitsev via devel wrote:
On 30.09.2020 15:39, Robert-André Mauchin wrote:
I have an issue with both Clementine and Strawberry (a fork of Clementine)
in F33 and above, users reported that disabling LTO fixes the problem.
I have the same issue with Telegram Desktop:
On 9/30/20 7:39 AM, Robert-André Mauchin wrote:
On Tuesday, 18 August 2020 17:12:02 CEST Jeff Law wrote:
So we're at a point where the F33 FTBFS issues related to LTO that I'm aware
of
have been resolved (by opting the package out of LTO). I still expect
some LTO issues will pop up as
On 30.09.2020 15:39, Robert-André Mauchin wrote:
> I have an issue with both Clementine and Strawberry (a fork of Clementine)
> in F33 and above, users reported that disabling LTO fixes the problem.
I have the same issue with Telegram Desktop:
https://bugzilla.redhat.com/show_bug.cgi?id=1880290
On 9/30/20 9:25 AM, Zbigniew Jędrzejewski-Szmek wrote:
I pushed the following to fix build of sems:
https://src.fedoraproject.org/rpms/sems/c/beef747b4641429459065bd39dbea447405f33e9?branch=master
Not my package, and the code is a bit iffy, so it's quite likely that
the problem is in the
I pushed the following to fix build of sems:
https://src.fedoraproject.org/rpms/sems/c/beef747b4641429459065bd39dbea447405f33e9?branch=master
Not my package, and the code is a bit iffy, so it's quite likely that
the problem is in the package... Just letting you know in case you're still
looking
On 9/30/20 7:39 AM, Robert-André Mauchin wrote:
On Tuesday, 18 August 2020 17:12:02 CEST Jeff Law wrote:
So we're at a point where the F33 FTBFS issues related to LTO that I'm aware
of
have been resolved (by opting the package out of LTO). I still expect
some LTO issues will pop up as
On Tuesday, 18 August 2020 17:12:02 CEST Jeff Law wrote:
> So we're at a point where the F33 FTBFS issues related to LTO that I'm aware
> of
have been resolved (by opting the package out of LTO). I still expect
> some LTO issues will pop up as packages fix things like missing
> dependencies,
On Thu, 2020-08-20 at 11:42 +0200, Vitaly Zaitsev via devel wrote:
> On 18.08.2020 17:12, Jeff Law wrote:
> > So we're at a point where the F33 FTBFS issues related to LTO that I'm
> > aware of
> > have been resolved (by opting the package out of LTO). I still expect
> > some LTO
> > issues
On 18.08.2020 17:12, Jeff Law wrote:
> So we're at a point where the F33 FTBFS issues related to LTO that I'm aware
> of
> have been resolved (by opting the package out of LTO). I still expect some
> LTO
> issues will pop up as packages fix things like missing dependencies, cmake
> macros,
On Tue, 2020-08-18 at 17:21 +0100, Tomasz Kłoczko wrote:
> On Tue, 18 Aug 2020 at 16:12, Jeff Law wrote:
> [..]
> > My focus is now turning to the packages with LTO opt-outs. I'll be
> > extracting
> > bug reports for upstream (primarily GCC), trying simple workarounds for old
> > style
> >
On Tue, 18 Aug 2020 at 16:12, Jeff Law wrote:
[..]
> My focus is now turning to the packages with LTO opt-outs. I'll be
> extracting
> bug reports for upstream (primarily GCC), trying simple workarounds for
> old style
> symbol versioning, identifying backports from upstream GCC that allow us
So we're at a point where the F33 FTBFS issues related to LTO that I'm aware of
have been resolved (by opting the package out of LTO). I still expect some LTO
issues will pop up as packages fix things like missing dependencies, cmake
macros, etc. I continue to be available to investigate
18 matches
Mail list logo
