[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 17:39:19 -0400

On Sat, Aug 8, 2009 at 3:14 AM, Bruno Haible<address@hidden> wrote:
> It would be worth trying to not --avoid=unistd in the modules subdirectories.
> This should lead to a different <unistd.h> being generated for the module
> subdirectory than for the clisp core, but a more complete one.
> More generally, you want to use --avoid for modules which generate code,
> and where duplicate functions in different .o files would lead to linker
> errors. But you may want to omit --avoid for modules which only provide
> autoconf macros and header files.

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

I can, of course, add -I build/gnulib/ to module CFLAGS on a per-module basis,
but what if a module wants both unistd.h and alloca?!

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

reply via email to

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