[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: uname: build problem on win32

From: Sam Steingold
Subject: Re: uname: build problem on win32
Date: Mon, 10 Aug 2009 18:43:17 -0400

On Mon, Aug 10, 2009 at 6:26 PM, Bruno Haible<address@hidden> wrote:
> Sam Steingold wrote:
>> the bottom line is:
>> if I add -I build/gnulib/ to module CFLAGS, then include_next will
>> make build/gnulib/unistd.h supersede build/syscalls/gnulib/unistd.h,
>> which is no good.
>> if I do NOT add -I build/gnulib/ to module CFLAGS, then
>> regexp/gnulib/regex.c will not find build/gnulib/alloca.h
> Indeed, this is still somewhat weird. The include_next should work as expected
> if you massage the inclusion guard identifiers of the two unistd.h files
> so that they become different: On one of these, do a
>  sed -e s/_GL_UNISTD_H/_GL_UNISTD_H_2/

you seem to imply that after all the solution is to add -I
build/gnulib/ to module CFLAGS,
but to somehow uniquify those guards so that _all_ the generated
unistd.h files are included one by one and none is bypassed.

1. are you sure this is safe? (i.e., they cannot step on each others toes)

2. you can use the --macro-prefix gnulib-too argument to augment the guards.
i.e., whenever you generate a header, modify the guards according to the prefix.


Sam Steingold <http://sds.podval.org>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]