Re: compiling development sources on mac

[Rob Mahurin]

On Fri, Dec 18, 2009 at 02:46:01PM -0500, John W. Eaton wrote:
> On 18-Dec-2009, Rob Mahurin wrote:
> | On Thu, Dec 17, 2009 at 06:47:21PM -0500, Ben Abbott wrote:
> | > Which prompted me to add the line below at the top of md5.c ... My
> | > error was different from yours. My build failed at md5.c, not with
> | > lex.cc
> | > 
> | >   #include <config.h>
> | > 
> | > I needed to add this line to the top of ...
> | > 
> | >   liboctave/md5.c
> | >   src/gl2ps.c
> | > 
> | > With those two changes, my build completed without error. However it
> | > doesn't run due to dylib conflicts which, I understand, are specific
> | > to my configuration.
> | 
> | Thanks.  Today I have to modify those files as well.
> | 
> | If I insert an include statement at the top of lex.cc, the
> | compile continues.  However, lex.cc is not part of the developer
> | sources:
> | 
> |     $ rm src/lex.cc && make -C src lex.cc
> |     /bin/sh ../build-aux/ylwrap lex.ll lex.octave_.c lex.cc -- flex -I -I
> | 
> | The generated lex.cc includes <config.h> about twelve hundred lines
> | in, where the contents of lex.ll appear.  But <string.h> is included
> | in the generated output up near the top of the file.  Is there a
> | "right" way to include <config.h> near the top of lex.cc, since that's
> | apparently a gnulib requirement?
> 
> Maybe the easiest way around this problem would be to create a file
> that contains
> 
>   #ifdef HAVE_CONFIG_H
>   #include <config.h>
>   #endif
>   #include "lex.cc"
> 
> and then compile that instead of lex.cc.

Here is a patch that changes these three files.  The fix for lex.cc is
ugly.

Cheers,
Rob

config_before_string.patch
Description: Text document