Just an additional headsup as we are on the topic of "LTO fun"; it seems like
any Go packages utilizing cgo/the external linker seems to be just broken with
LTO.
The error looks like:
net._cgo_3c1cec0c9a4e_C2func_getaddrinfo: relocation target
_cgo_3c1cec0c9a4e_C2func_getaddrinfo not defined
Ple
On Sat, Dec 25, 2021 at 11:51:49AM +0100, Morten Linderud via arch-dev-public
wrote:
> Just an additional headsup as we are on the topic of "LTO fun"; it seems like
> any Go packages utilizing cgo/the external linker seems to be just broken with
> LTO.
>
> The error looks like:
> net._cgo_3c1cec0
Allan McRae via arch-dev-public on Fri,
2021/12/24 18:01:
> This fix for the strip issue is for people to add CFLAGS+="
> -ffat-lto-objects" to their PKGBUILDs if they use LTO and contain a .a
> or .o archive. This affects ~300 packages in our repos (~2.5%). I will
> create a TODO list.
Do y
On Sat, Dec 25, 2021, 22:01 Christian Hesse via arch-dev-public <
arch-dev-public@lists.archlinux.org> wrote:
> Allan McRae via arch-dev-public on
> Fri,
> 2021/12/24 18:01:
> > This fix for the strip issue is for people to add CFLAGS+="
> > -ffat-lto-objects" to their PKGBUILDs if they use LTO a
"Jan Alexander Steffens (heftig)" on Sat, 2021/12/25
22:07:
> On Sat, Dec 25, 2021, 22:01 Christian Hesse via arch-dev-public <
> arch-dev-public@lists.archlinux.org> wrote:
>
> > Allan McRae via arch-dev-public on
> > Fri,
> > 2021/12/24 18:01:
> > > This fix for the strip issue is for people
