Re: Compilation issue after gcc removal

2018-07-19 Thread Michael Schwendt
On Fri, 20 Jul 2018 01:08:55 +0200, Marcin Zajączkowski wrote: > On 2018-07-20 00:26, Artur Iwicki wrote: > > I looked at libattr and in the changelog, there's this: > >> * Tue Jul 17 2018 Kamil Dudka 2.4.48-3 > >> - temporarily provide attr/xattr.h symlink until users are migrated > >> (#1601

Compilation issue after gcc removal

2018-07-19 Thread Marcin Zajączkowski
On 2018-07-20 00:26, Artur Iwicki wrote: > I looked at libattr and in the changelog, there's this: >> * Tue Jul 17 2018 Kamil Dudka 2.4.48-3 >> - temporarily provide attr/xattr.h symlink until users are migrated >> (#1601482) > > The bugzilla ticket says that attr/xattr.h was removed from libatt

Re: Compilation issue after gcc removal

2018-07-19 Thread Artur Iwicki
I looked at libattr and in the changelog, there's this: >* Tue Jul 17 2018 Kamil Dudka 2.4.48-3 >- temporarily provide attr/xattr.h symlink until users are migrated (#1601482) The bugzilla ticket says that attr/xattr.h was removed from libattr and is now a symlink to sys/xattr.h. Taking a look a

Compilation issue after gcc removal

2018-07-19 Thread Marcin Zajączkowski
Hi, After the recent gcc removal from build root [1] I added explicit dependency on gcc [2], but even though my pyxattr package started to fail with [3][4]: > xattr.c:532:56: error: 'ENOATTR' undeclared (first use in this function); did > you mean 'ENOTTY'? I've checked it and ENOATTR should be