Re: [lfs-dev] libcap, which and gperf

2018-02-03 Thread Bruce Dubbs

Armin K. wrote:

On Sat, 2018-02-03 at 18:49 +1100, Wayne Blaszczyk wrote:

FYI,

It looks like libcap silently fails a gperf check due to which
missing.
If which is installed then libcap build fails with the following:


make[1]: Entering directory '/opt/sources/libcap-2.25/libcap'
gcc -O2 -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Dlinux -Wall
-Wwrite-strings -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-
prototypes -Wmissing-prototypes -Wnested-externs -Winline -Wshadow
-g  -fPIC -I/opt/sources/libcap-2.25/libcap/../libcap/include/uapi
-I/opt/sources/libcap-2.25/libcap/../libcap/include -include
_caps_output.gperf -c cap_text.c -o cap_text.o
In file included from :0:0:
./_caps_output.gperf:71:80: error: unknown type name ‘size_t’
  gperf_case_strncmp (register const char *s1, register const char
*s2, register size_t n)
  
^~

./_caps_output.gperf:96:53: error: unknown type name ‘size_t’
  __cap_hash_name (register const char *str, register size_t len)
  ^~
./_caps_output.gperf:200:55: error: unknown type name ‘size_t’
  __cap_lookup_name (register const char *str, register size_t len)
^~
./_caps_output.gperf:200:1: error: conflicting types for
‘__cap_lookup_name’
  __cap_lookup_name (register const char *str, register size_t len)
  ^
./_caps_output.gperf:33:29: note: previous declaration of
‘__cap_lookup_name’ was here
  const struct __cap_token_s *__cap_lookup_name(const char *, unsigned
int);
  ^
make[1]: *** [Makefile:63: cap_text.o] Error 1
make[1]: Leaving directory '/opt/sources/libcap-2.25/libcap'
make: *** [Makefile:12: all] Error 2


Probably related to this:

https://bugs.gentoo.org/604802


The question is, how important is libcap being built with gperf.

Regards,
Wayne.







It's not important at all, as the tarball already distributes pre-
generated file (with an older gperf, I guess). Fix the issue with

make BUILD_GPERF=no


We have gperf after libcap, so it is really a non-issue for LFS.

  - Bruce


--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: [lfs-dev] libcap, which and gperf

2018-02-03 Thread Armin K.
On Sat, 2018-02-03 at 18:49 +1100, Wayne Blaszczyk wrote:
> FYI,
> 
> It looks like libcap silently fails a gperf check due to which
> missing.
> If which is installed then libcap build fails with the following:
> 
> 
> make[1]: Entering directory '/opt/sources/libcap-2.25/libcap'
> gcc -O2 -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Dlinux -Wall
> -Wwrite-strings -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-
> prototypes -Wmissing-prototypes -Wnested-externs -Winline -Wshadow
> -g  -fPIC -I/opt/sources/libcap-2.25/libcap/../libcap/include/uapi
> -I/opt/sources/libcap-2.25/libcap/../libcap/include -include
> _caps_output.gperf -c cap_text.c -o cap_text.o
> In file included from :0:0:
> ./_caps_output.gperf:71:80: error: unknown type name ‘size_t’
>  gperf_case_strncmp (register const char *s1, register const char
> *s2, register size_t n)
>  
>^~
> ./_caps_output.gperf:96:53: error: unknown type name ‘size_t’
>  __cap_hash_name (register const char *str, register size_t len)
>  ^~
> ./_caps_output.gperf:200:55: error: unknown type name ‘size_t’
>  __cap_lookup_name (register const char *str, register size_t len)
>^~
> ./_caps_output.gperf:200:1: error: conflicting types for
> ‘__cap_lookup_name’
>  __cap_lookup_name (register const char *str, register size_t len)
>  ^
> ./_caps_output.gperf:33:29: note: previous declaration of
> ‘__cap_lookup_name’ was here
>  const struct __cap_token_s *__cap_lookup_name(const char *, unsigned
> int);
>  ^
> make[1]: *** [Makefile:63: cap_text.o] Error 1
> make[1]: Leaving directory '/opt/sources/libcap-2.25/libcap'
> make: *** [Makefile:12: all] Error 2
> 
> 
> Probably related to this:
> 
> https://bugs.gentoo.org/604802
> 
> 
> The question is, how important is libcap being built with gperf.
> 
> Regards,
> Wayne.
> 
> 
> 
> 
> 

It's not important at all, as the tarball already distributes pre-
generated file (with an older gperf, I guess). Fix the issue with

make BUILD_GPERF=no
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

[lfs-dev] libcap, which and gperf

2018-02-02 Thread Wayne Blaszczyk
FYI,

It looks like libcap silently fails a gperf check due to which missing.
If which is installed then libcap build fails with the following:


make[1]: Entering directory '/opt/sources/libcap-2.25/libcap'
gcc -O2 -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Dlinux -Wall 
-Wwrite-strings -Wpointer-arith -Wcast-qual -Wcast-align -Wstrict-prototypes 
-Wmissing-prototypes -Wnested-externs -Winline -Wshadow
-g  -fPIC -I/opt/sources/libcap-2.25/libcap/../libcap/include/uapi 
-I/opt/sources/libcap-2.25/libcap/../libcap/include -include _caps_output.gperf 
-c cap_text.c -o cap_text.o
In file included from :0:0:
./_caps_output.gperf:71:80: error: unknown type name ‘size_t’
 gperf_case_strncmp (register const char *s1, register const char *s2, register 
size_t n)

^~
./_caps_output.gperf:96:53: error: unknown type name ‘size_t’
 __cap_hash_name (register const char *str, register size_t len)
 ^~
./_caps_output.gperf:200:55: error: unknown type name ‘size_t’
 __cap_lookup_name (register const char *str, register size_t len)
   ^~
./_caps_output.gperf:200:1: error: conflicting types for ‘__cap_lookup_name’
 __cap_lookup_name (register const char *str, register size_t len)
 ^
./_caps_output.gperf:33:29: note: previous declaration of ‘__cap_lookup_name’ 
was here
 const struct __cap_token_s *__cap_lookup_name(const char *, unsigned int);
 ^
make[1]: *** [Makefile:63: cap_text.o] Error 1
make[1]: Leaving directory '/opt/sources/libcap-2.25/libcap'
make: *** [Makefile:12: all] Error 2


Probably related to this:

https://bugs.gentoo.org/604802


The question is, how important is libcap being built with gperf.

Regards,
Wayne.





-- 
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page