Re: s390x: glibc32 and gcc

2019-10-16 Thread Jerry James
On Wed, Oct 16, 2019 at 4:48 AM Florian Weimer wrote: > * Jerry James: > > Sorry for not cluing you in sooner. I sent email to the maintainers > > of all the packages I need to rebuild, but that didn't include you. > > I'll let you know as soon as these builds are tagged into Rawhide. > > Oh no,

Re: s390x: glibc32 and gcc

2019-10-16 Thread Florian Weimer
* Jerry James: > On Fri, Oct 11, 2019 at 5:08 AM Florian Weimer wrote: >> And did not bump soname at the same time? I suspected as much once I >> stared at the problem some more. > > Yes, that's exactly right. Okay, that makes the mpfr transition much harder, and what you did certainly looks

Re: s390x: glibc32 and gcc

2019-10-11 Thread Jerry James
On Fri, Oct 11, 2019 at 5:08 AM Florian Weimer wrote: > And did not bump soname at the same time? I suspected as much once I > stared at the problem some more. Yes, that's exactly right. > Oh, if mpfr and mpc had bumped soname at the same time, the > BuildRequires: change would not have been

Re: s390x: glibc32 and gcc

2019-10-11 Thread Florian Weimer
* Jerry James: > On Thu, Oct 10, 2019 at 12:39 AM Florian Weimer wrote: >> 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

Re: s390x: glibc32 and gcc

2019-10-10 Thread Jerry James
On Thu, Oct 10, 2019 at 12:39 AM Florian Weimer wrote: > 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

Re: s390x: glibc32 and gcc

2019-10-10 Thread Florian Weimer
* Florian Weimer: > * Jerry James: > >> On Wed, Oct 9, 2019 at 8:25 PM Jerry James 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

Re: s390x: glibc32 and gcc

2019-10-10 Thread Florian Weimer
* Jerry James: > On Wed, Oct 9, 2019 at 8:25 PM Jerry James 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

Re: s390x: glibc32 and gcc

2019-10-09 Thread Jerry James
On Wed, Oct 9, 2019 at 8:25 PM Jerry James 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

s390x: glibc32 and gcc

2019-10-09 Thread Jerry James
Hi all, I'm in the midst of the mpfr 4 rebuilds. I just tried to kick off a long chain build, the first build of which is the final gcc rebuild that will give us an mpfr 4-using gcc. Unfortunately, not all of its dependencies could be installed on s390x; root.log says: DEBUG util.py:593: No