| 1 |
On Sat, 30 Mar 2019 17:39:03 -0000 (UTC) Grant Edwards wrote: |
| 2 |
> On 2019-03-30, Andrew Savchenko <bircoph@g.o> wrote: |
| 3 |
> > On Sat, 30 Mar 2019 15:09:06 -0000 (UTC) Grant Edwards wrote: |
| 4 |
> >> On 2019-03-29, Philip Webb <purslow@××××××××.net> wrote: |
| 5 |
> >> > 190329 Grant Edwards wrote: |
| 6 |
> >> > |
| 7 |
> >> >> gcc-7.3.9-r3 is marked stable, yet it fails to build if you have the |
| 8 |
> >> >> current stable version of glibc installed (2.28-r5). |
| 9 |
> >> > |
| 10 |
> >> > I've been using Gcc-8.2.0-r6 since 170302 with Glibc-2.27-r6 : no problems. |
| 11 |
> >> |
| 12 |
> >> What I'm asking about is that 7.3.0-r3 (which is stable) won't build |
| 13 |
> >> with glibc-2.28 (which is stable). My question: is that considered a |
| 14 |
> >> bug or not? |
| 15 |
> > |
| 16 |
> > It depends on the details of the problem, but you provided no |
| 17 |
> > details to make further considerations. |
| 18 |
> |
| 19 |
> glibc 2.27 has an include file "ustat.h" which declares a library |
| 20 |
> function ustat(). glibc 2.28 does not have that include file (nor the |
| 21 |
> function, AFAICT). Any application that #includes ustat.h or calls |
| 22 |
> ustat() fails to build with glibc 2.28. |
| 23 |
|
| 24 |
migrate to statfs() or fstatfs(), that's easy. |
| 25 |
|
| 26 |
Best regards, |
| 27 |
Andrew Savchenko |
Archives