On 04/08/2017 11:19, Pierre Labastie wrote:
> On 04/08/2017 00:19, Armin K. wrote:
>> On 03.08.2017 22:40, Pierre Labastie wrote:
>>> On 03/08/2017 19:42, Pierre Labastie wrote:
>>>> Hi,
>>>> Using the instructions in the current systemd book, upgrading from 
>>>> systemd-233
>>>> to 234, I get:
>>>> --------------------------
>>>>    CC       src/resolve/dns-type.o
>>>>    CC       src/login/test-inhibit.o
>>>> In file included from src/resolve/dns-type.c:34:0:
>>>> src/resolve/dns_type-from-name.h:136:1: error: conflicting types for
>>>> 'lookup_dns_type'
>>>>   lookup_dns_type (register const char *str, register size_t len)
>>>>   ^~~~~~~~~~~~~~~
>>>> src/resolve/dns-type.c:32:1: note: previous declaration of 
>>>> 'lookup_dns_type'
>>>> was here
>>>>   lookup_dns_type (register const char *str, register GPERF_LEN_TYPE len);
>>>>   ^~~~~~~~~~~~~~~
>>>> make[3]: *** [Makefile:16353: src/resolve/dns-type.o] Error 1
>>>> make[3]: *** Waiting for unfinished jobs....
>>>> --------------------------
>>>> Using make -j1 does not help.
>>>>
>>>> I haven't investigated much. Please tell me if you need further 
>>>> information.
>>>>
>>>> Pierre
>>>>
>>>
>>> Just downloaded the source from github, run autogen.sh, then built by the
>>> book. Configured, compiled, and installed OK. Got 2 failures in tests.
>>>
>>> Could it be a problem with the tarball on anduin?
>>>
>>> Pierre
>>>
>>
>> Could be mismatching gperf versions used to generate files in the tarball and
>> gperf version on your system. Which gperf version do you have installed? You
>> could get away with removing src/resolve/dns_type-from-name.h and letting
>> gperf regenerate it.
>>
> 
> I have gperf-3.0.4. That might be it (will try to upgrade gperf and let you 
> know).

Yes, it compiles OK after upgrading to gperf-3.1. Thanks Armin.

> 
> OTOH, why not use the upstream tarball in BLFS?

Still that question remains...
Pierre
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to