* Denis Fateyev:
> Thank you, all variants work fine.
>
> Now I have another issue with "nfdump" package, probably for the same
> reason: a build flag interference.
>
> I use '-fPIC' in LDFLAGS to make "configure" happy:
> https://src.fedoraproject.org/rpms/nfdump/blob/rawhide/f/nfdump.spec#_49
-
Thank you, all variants work fine.
Now I have another issue with "nfdump" package, probably for the same
reason: a build flag interference.
I use '-fPIC' in LDFLAGS to make "configure" happy:
https://src.fedoraproject.org/rpms/nfdump/blob/rawhide/f/nfdump.spec#_49
I suspect that this flag presen
On 08/02/2022 21:41, Florian Weimer wrote:
CFLAGS?=-O2 -Wall -g -D_FORTIFY_SOURCE=2 -fstack-protector -fPIC
LDFLAGS?=-Wl,-z,now -Wl,-z,relro -Wl,-soname,libscrypt.so.0
-Wl,--version-script=libscrypt.version
Can be easily fixed by changing ?= with +=.
--
Sincerely,
Vitaly Zaitsev (vit...@eas
* Denis Fateyev:
> For example, "libscrypt" package issue is filled here:
> https://bugzilla.redhat.com/show_bug.cgi?id=2046062
> The library in the package was actually built, but the build results are
> different under
> various GCC versions — as shown in the "nm" dump below.
>
> Has anybody a
Hello all,
Recently, I have found that with GCC version bump in F36 some of my
packages are stopped to build, or stopped to build properly during the
planned package rebuild.
They were fine under F35 — but apparently there are some changes in newer
GCC that affected them.
For example, "libscrypt
