Re: s390x: glibc32 and gcc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Florian Weimer:

> * Jerry James:
>
>> On Wed, Oct 9, 2019 at 8:25 PM Jerry James <loganjerry@xxxxxxxxx> wrote:
>>> The previous build managed to grab the last build of glibc32 for
>>> s390x, it seems.  I'm going to assume that this means that s390x
>>> should be removed from the multilib_64_arches variable in the gcc
>>> spec, just so I can keep these builds going.  (There are at least 3
>>> days of builds still to go.)  If that is wrong, please let me know
>>> ASAP so I can make it right before anything lands in Rawhide.
>>
>> Sadly, simply removing s390x from multilib_64_arches was insufficient.
>>
>> In file included from /usr/include/features.h:489,
>>                  from /usr/include/bits/libc-header-start.h:33,
>>                  from /usr/include/stdio.h:27,
>>                  from ../../../../libgcc/../gcc/tsystem.h:87,
>>                  from ../../../../libgcc/libgcov.h:42,
>>                  from ../../../../libgcc/libgcov-merge.c:26:
>> /usr/include/gnu/stubs.h:8:11: fatal error: gnu/stubs-32.h: No such
>> file or directory
>>     8 | # include <gnu/stubs-32.h>
>>       |           ^~~~~~~~~~~~~~~~
>> compilation terminated.
>> make[5]: *** [Makefile:920: _gcov_merge_add.o] Error 1
>>
>>
>> So does that mean that glibc has to be rebuilt first, with s390 and
>> s390x removed from biarcharches?
>
> Sorry, I wasn't aware that you were trying to rebuild gcc this week.  I
> spoke to Jakub about the glibc32 change, and he had no objections.
>
> It's not clear how you are handling the transition.  Why do you need to
> change GCC build requirements?  Did anyone request this?
>
> I would have expected a run-time-only compat-mpfr library with the old
> soname, so that GCC keeps working until it is rebuilt.

Anyway, I tweaked gcc.spec some more, and the build has no processed
past the critical point.  We'll see if the paths are correct in the
end. 8-/

We might still do further changes on s390x, but this can hopefully wait
until after the mpfr transition.

Thanks,
Florian
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux