Thank you two for the answer.
YOUNG, MICHAEL A. wrote on Sat, Jan 26, 2019 at 12:53:18PM +0000:
The problem is your gcc build requires libgcc_s.so.1 which is the
i386
version; the x86_64 version is libgcc_s.so.1()(64bit) . So something has
gone wrong in your build process.
Eh, even after reading this I was doubting you, but that appears to be
true... I guess asking rpm to add a couple of parenthesis after 32bit
lib requires to at least look like 64bit libs require and not a simple
file require would be asking too much, I never noticed it worked like
this for 32bit libs :/
And rightly enough rpm -qp --requires of "my" gcc does have both
libgcc_s.so.1 while fc30's libgcc.x86_64 only requires the x86_64
version; interesting given the src.rpm is the same.
I've extracted the rpm and am not quite sure where the auto requires
comes from, actually? I thought there was a script doing basically ldd
on each executable (as described on the rpm website[1]), but nothing in
the gcc package seems to require libgcc_s - what am I missing?
I can't see anything obviously different between both build logs, either
copr's[2] or koji's[3] (caution: files are 10MB (compressed) and 55MB
respectively); the logs are too different to diff because of parallel
build but at least lines containing "libgcc_s" are similar enough...
[1]
http://ftp.rpm.org/max-rpm/s1-rpm-depend-auto-depend.html
[2]
https://copr-be.cloud.fedoraproject.org/results/martinetd/gcc9/fedora-29-...
[3]
https://kojipkgs.fedoraproject.org//packages/gcc/9.0.1/0.1.fc30/data/logs...
Will look into how autodepends works a bit more, I'm curious why this is
different.
Thanks,
--
Dominique