| 1 |
On Sat, 30 Mar 2019 15:09:06 -0000 (UTC) Grant Edwards wrote: |
| 2 |
> On 2019-03-29, Philip Webb <purslow@××××××××.net> wrote: |
| 3 |
> > 190329 Grant Edwards wrote: |
| 4 |
> > |
| 5 |
> >> gcc-7.3.9-r3 is marked stable, yet it fails to build if you have the |
| 6 |
> >> current stable version of glibc installed (2.28-r5). |
| 7 |
> > |
| 8 |
> > I've been using Gcc-8.2.0-r6 since 170302 with Glibc-2.27-r6 : no problems. |
| 9 |
> |
| 10 |
> What I'm asking about is that 7.3.0-r3 (which is stable) won't build |
| 11 |
> with glibc-2.28 (which is stable). My question: is that considered a |
| 12 |
> bug or not? |
| 13 |
|
| 14 |
It depends on the details of the problem, but you provided no |
| 15 |
details to make further considerations. In general it would be |
| 16 |
considered a bug. |
| 17 |
|
| 18 |
> One might think that the 7.3.0-r3 ebuild should require |
| 19 |
> gblic < 2.28. Is one allowed to tweak ebuilds like that without |
| 20 |
> bumping the revision? |
| 21 |
> |
| 22 |
> FWIW 7.3.0-r6 does build and works fine for my application which won't |
| 23 |
> build with gcc-8 -- so it's purely an academic question. |
| 24 |
|
| 25 |
It's better to fix your application. Fixing problem revealed by gcc |
| 26 |
update is usually not hard. |
| 27 |
|
| 28 |
Best regards, |
| 29 |
Andrew Savchenko |
Archives