gnupic: Re: [gnupic] GPasm maint
Subject:
Re: [gnupic] GPasm maint
From:
Rob Hamerling ####@####.####
Date:
4 Jul 2008 19:54:08 -0000
Message-Id: <486E7FE4.9010704@gmail.com>
Hi David,
David wrote:
>> I think there must be an '#endif' missing in parse.y
> There aren't any #if's in parse.y, and I can't find anything mismatched
> in any of the included files. Did you edit stdhdr.h? You mentioned
> problems with HAVE_MALLOC_H, and there's a double #if/#endif around a
> reference to HAVE_MALLOC_H in stdhdr.h. Is it possible you got confused
> there?
Confusion and user-errors are always possible!
I have not edited stdhdr.h, I have specified some macros on the
commandline of the compiler:
-DVERSION="0.13.6" &
-DHAVE_STRING_H &
-DHAVE_STDLIB_H &
-DHAVE_STRICMP &
-DHAVE_MALLOC_H &
-DYY_NO_UNISTD_H &
-DHAVE_DOS_BASED_FILE_SYSTEM &
####@####.####
Well, since it is a 'warning' the compiler creates an proceeds
>> An error I 'circumvented' by excluding vsnprintf from the library
>>> vsnprintf.c(42): Error! E1055: Unable to open 'config.h'
>> I cannot find 'config.h', nor do I see any possible macro definition
>> to prevent it being included.
> config.h is supposed to be auto-generated from config.h.in when you
> run ./configure.
Ah, I have no experience with autoconf and automake!
I think there is no 'native' OS/2 version of these.
Maybe I could create config.h under Linux, I'll see.
>
> The #v() issue isn't *exactly* what's reported in bug #1250441, but
> it falls under the same heading. Notice how I said "...the #v syntax for
> gpasm currently only works for actual "symbols" and *not* defines."
> ERROR and MESSG directives are treated almost the same way as #defines,
> so gpasm just can't handle your usage quite right. I've been hacking
> away at parsing problems like this one, but I've gotten bogged down
> pretty badly in parsing hell. Not sure how it'll turn out.
Thanks for the explanation, I have removed the #v from these statements.
Regards, Rob.
--
Rob Hamerling, Vianen, NL (http://www.robh.nl/)
