Bruno Haible wrote:
Sam Steingold wrote:
Therefore for now, this change is better limited to your project.
OK, how about adding an --guard_prefix option?
fixing the problem at the source (gnulib-tool) is much easier - just a
few lines.
fixing it inside clisp is a bigger task.
Feel free to do
Sam Steingold wrote:
> > Therefore for now, this change is better limited to your project.
>
> OK, how about adding an --guard_prefix option?
> fixing the problem at the source (gnulib-tool) is much easier - just a
> few lines.
> fixing it inside clisp is a bigger task.
Feel free to do it in you
On Wed, Aug 12, 2009 at 10:43 AM, Bruno Haible wrote:
> Sam Steingold wrote:
>> >> On one of these, do a
>> >> sed -e s/_GL_UNISTD_H/_GL_UNISTD_H_2/
>> >
>> > 2. you can use the --macro-prefix gnulib-too argument to augment the
>> > guards.
>> > i.e., whenever you generate a header, modify the gu
Sam Steingold wrote:
> >> On one of these, do a
> >> sed -e s/_GL_UNISTD_H/_GL_UNISTD_H_2/
> >
> > 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.
>
> diff --git a/gnulib-tool b
Sam Steingold wrote:
On Mon, Aug 10, 2009 at 6:26 PM, Bruno Haible 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/g
On Mon, Aug 10, 2009 at 6:26 PM, Bruno Haible 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/ t
Sam Steingold wrote:
> > It would be worth trying to not --avoid=unistd in the modules
> > subdirectories.
> > This should lead to a different being generated for the module
> > subdirectory than for the clisp core, but a more complete one.
> >
> > More generally, you want to use --avoid for modu
On Sat, Aug 8, 2009 at 3:14 AM, Bruno Haible wrote:
> It would be worth trying to not --avoid=unistd in the modules subdirectories.
> This should lead to a different being generated for the module
> subdirectory than for the clisp core, but a more complete one.
>
> More generally, you want to use
On Mon, Aug 10, 2009 at 2:22 PM, Sam Steingold wrote:
> I followed your instructions, so now I have unistd.h both in the above
> and in build/gllib/unistd.h
> the former comes first on the gcc -I list, but, apparently, #include
> next discards it and only the latter is actually used.
... and when
On Sat, Aug 8, 2009 at 3:14 AM, Bruno Haible wrote:
> Sam Steingold wrote:
>> In file included from
>> /cygdrive/c/sds/dev/current/modules/syscalls/gllib/gethostname.c:83:
>> /cygdrive/c/sds/dev/current/modules/syscalls/gllib/w32sock.h: In function
>> `set_winsock_errno':
>> /cygdrive/c/sds/dev/c
Sam Steingold wrote:
> In file included from
> /cygdrive/c/sds/dev/current/modules/syscalls/gllib/gethostname.c:83:
> /cygdrive/c/sds/dev/current/modules/syscalls/gllib/w32sock.h: In function
> `set_winsock_errno':
> /cygdrive/c/sds/dev/current/modules/syscalls/gllib/w32sock.h:34: warning:
> imp
make[4]: Entering directory `/cygdrive/c/sds/dev/current/build-mingw-1/syscalls/
gllib'
gcc -mno-cygwin -DHAVE_CONFIG_H -I. -I/cygdrive/c/sds/dev/current/modules/syscal
ls/gllib -I.. -I/cygdrive/c/sds/top/include -Ic:/sds/dev/current/build-mingw-1
/gllib -g -O2 -W -Wswitch -Wcomment -Wpointer-a
12 matches
Mail list logo
