[gentoo-user] Re: Stable gcc:7.3.0 won't build with stable glibc
On 2019-03-31, William Hubbs wrote: > I would say you are left with two options. You can either file a bug > against the third party library and ask them to make the changes > (maybe providing patches) or the harder option would be to migrate > away from that library. Ideally, convincing the third part library > authors to make those changes would be best because it would benefit > all of their consumers. The easy option is to use (unstable) gcc 7.3.0-r6. It biulds with glibc-2.28, and it will cleanly compile the library. [This is what I'm doing.] What I was asking about was whether it would be appropriate to file a Gentoo bug against the gcc 7.3.0-r3 (stable) ebuild because it won't build with the current stable glibc. I'm sure the library will build with gcc-8 in the near future, but I need to build it now. :) -- Grant
Re: [gentoo-user] Re: Stable gcc:7.3.0 won't build with stable glibc
On Sun, Mar 31, 2019 at 01:57:31AM -, Grant Edwards wrote: > On 2019-03-30, Andrew Savchenko wrote: > > On Sat, 30 Mar 2019 17:39:03 - (UTC) Grant Edwards wrote: > > > >> glibc 2.27 has an include file "ustat.h" which declares a library > >> function ustat(). glibc 2.28 does not have that include file (nor the > >> function, AFAICT). Any application that #includes ustat.h or calls > >> ustat() fails to build with glibc 2.28. > > > > migrate to statfs() or fstatfs(), that's easy. > > It would be if it was my code that needs to change. It isn't. It's a > third party library. I would say you are left with two options. You can either file a bug against the third party library and ask them to make the changes (maybe providing patches) or the harder option would be to migrate away from that library. Ideally, convincing the third part library authors to make those changes would be best because it would benefit all of their consumers. William signature.asc Description: Digital signature
[gentoo-user] Re: Stable gcc:7.3.0 won't build with stable glibc
On 2019-03-30, Andrew Savchenko wrote: > On Sat, 30 Mar 2019 17:39:03 - (UTC) Grant Edwards wrote: > >> glibc 2.27 has an include file "ustat.h" which declares a library >> function ustat(). glibc 2.28 does not have that include file (nor the >> function, AFAICT). Any application that #includes ustat.h or calls >> ustat() fails to build with glibc 2.28. > > migrate to statfs() or fstatfs(), that's easy. It would be if it was my code that needs to change. It isn't. It's a third party library. -- Grant
Re: [gentoo-user] Re: Stable gcc:7.3.0 won't build with stable glibc
On Sat, 30 Mar 2019 17:39:03 - (UTC) Grant Edwards wrote: > On 2019-03-30, Andrew Savchenko wrote: > > On Sat, 30 Mar 2019 15:09:06 - (UTC) Grant Edwards wrote: > >> On 2019-03-29, Philip Webb wrote: > >> > 190329 Grant Edwards wrote: > >> > > >> >> gcc-7.3.9-r3 is marked stable, yet it fails to build if you have the > >> >> current stable version of glibc installed (2.28-r5). > >> > > >> > I've been using Gcc-8.2.0-r6 since 170302 with Glibc-2.27-r6 : no > >> > problems. > >> > >> What I'm asking about is that 7.3.0-r3 (which is stable) won't build > >> with glibc-2.28 (which is stable). My question: is that considered a > >> bug or not? > > > > It depends on the details of the problem, but you provided no > > details to make further considerations. > > glibc 2.27 has an include file "ustat.h" which declares a library > function ustat(). glibc 2.28 does not have that include file (nor the > function, AFAICT). Any application that #includes ustat.h or calls > ustat() fails to build with glibc 2.28. migrate to statfs() or fstatfs(), that's easy. Best regards, Andrew Savchenko pgp2ce2n9eV32.pgp Description: PGP signature
[gentoo-user] Re: Stable gcc:7.3.0 won't build with stable glibc
On 2019-03-30, Andrew Savchenko wrote: > On Sat, 30 Mar 2019 15:09:06 - (UTC) Grant Edwards wrote: >> On 2019-03-29, Philip Webb wrote: >> > 190329 Grant Edwards wrote: >> > >> >> gcc-7.3.9-r3 is marked stable, yet it fails to build if you have the >> >> current stable version of glibc installed (2.28-r5). >> > >> > I've been using Gcc-8.2.0-r6 since 170302 with Glibc-2.27-r6 : no problems. >> >> What I'm asking about is that 7.3.0-r3 (which is stable) won't build >> with glibc-2.28 (which is stable). My question: is that considered a >> bug or not? > > It depends on the details of the problem, but you provided no > details to make further considerations. glibc 2.27 has an include file "ustat.h" which declares a library function ustat(). glibc 2.28 does not have that include file (nor the function, AFAICT). Any application that #includes ustat.h or calls ustat() fails to build with glibc 2.28. > In general it would be considered a bug. > >> One might think that the 7.3.0-r3 ebuild should require >> gblic < 2.28. Is one allowed to tweak ebuilds like that without >> bumping the revision? >> >> FWIW 7.3.0-r6 does build and works fine for my application which won't >> build with gcc-8 -- so it's purely an academic question. > > It's better to fix your application. Fixing problem revealed by gcc > update is usually not hard. My application uses a third-party open-source library for which I'm not a maintainer. That library contains code that can't be built with gcc 8.2. For various logistical reasons, I'm reluctant to make changes to that code. [It creates headaches and extra work down the road...] -- Grant
Re: [gentoo-user] Re: Stable gcc:7.3.0 won't build with stable glibc
On Sat, 30 Mar 2019 15:09:06 - (UTC) Grant Edwards wrote: > On 2019-03-29, Philip Webb wrote: > > 190329 Grant Edwards wrote: > > > >> gcc-7.3.9-r3 is marked stable, yet it fails to build if you have the > >> current stable version of glibc installed (2.28-r5). > > > > I've been using Gcc-8.2.0-r6 since 170302 with Glibc-2.27-r6 : no problems. > > What I'm asking about is that 7.3.0-r3 (which is stable) won't build > with glibc-2.28 (which is stable). My question: is that considered a > bug or not? It depends on the details of the problem, but you provided no details to make further considerations. In general it would be considered a bug. > One might think that the 7.3.0-r3 ebuild should require > gblic < 2.28. Is one allowed to tweak ebuilds like that without > bumping the revision? > > FWIW 7.3.0-r6 does build and works fine for my application which won't > build with gcc-8 -- so it's purely an academic question. It's better to fix your application. Fixing problem revealed by gcc update is usually not hard. Best regards, Andrew Savchenko pgp_X6SIW88OD.pgp Description: PGP signature
[gentoo-user] Re: Stable gcc:7.3.0 won't build with stable glibc
On 2019-03-29, Philip Webb wrote: > 190329 Grant Edwards wrote: > >> gcc-7.3.9-r3 is marked stable, yet it fails to build if you have the >> current stable version of glibc installed (2.28-r5). > > I've been using Gcc-8.2.0-r6 since 170302 with Glibc-2.27-r6 : no problems. What I'm asking about is that 7.3.0-r3 (which is stable) won't build with glibc-2.28 (which is stable). My question: is that considered a bug or not? One might think that the 7.3.0-r3 ebuild should require gblic < 2.28. Is one allowed to tweak ebuilds like that without bumping the revision? FWIW 7.3.0-r6 does build and works fine for my application which won't build with gcc-8 -- so it's purely an academic question. -- Grant
