| 1 |
On Sun, Mar 31, 2019 at 01:57:31AM -0000, Grant Edwards wrote: |
| 2 |
> On 2019-03-30, Andrew Savchenko <bircoph@g.o> wrote: |
| 3 |
> > On Sat, 30 Mar 2019 17:39:03 -0000 (UTC) Grant Edwards wrote: |
| 4 |
> > |
| 5 |
> >> glibc 2.27 has an include file "ustat.h" which declares a library |
| 6 |
> >> function ustat(). glibc 2.28 does not have that include file (nor the |
| 7 |
> >> function, AFAICT). Any application that #includes ustat.h or calls |
| 8 |
> >> ustat() fails to build with glibc 2.28. |
| 9 |
> > |
| 10 |
> > migrate to statfs() or fstatfs(), that's easy. |
| 11 |
> |
| 12 |
> It would be if it was my code that needs to change. It isn't. It's a |
| 13 |
> third party library. |
| 14 |
|
| 15 |
I would say you are left with two options. You can either file a bug |
| 16 |
against the third party library and ask them to make the changes (maybe |
| 17 |
providing patches) or the harder option would be to migrate away from |
| 18 |
that library. Ideally, convincing the third part library authors to make |
| 19 |
those changes would be best because it would benefit all of their |
| 20 |
consumers. |
| 21 |
|
| 22 |
William |
Archives