octave-maintainers
[Top][All Lists]
Advanced

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

Re: error: invalid character `' (ASCII 0) near line 164, column 2 [chang


From: Ben Abbott
Subject: Re: error: invalid character `' (ASCII 0) near line 164, column 2 [changeset]
Date: Fri, 12 Feb 2010 11:06:52 -0500

The error below has returned for me.

> Making all in interpreter
> ../../run-octave -f -q -H ./mk_doc_cache.m doc-cache ../../scripts/DOCSTRINGS 
> ../../src/DOCSTRINGS || { rm -f doc-cache; exit 1; }
> warning: invalid character `' (ASCII 0) near line 92, column 2
> error: invalid character `' (ASCII 0) near line 165, column 2
> parse error near line 165 of file 
> /Users/bpabbott/Development/mercurial/local_clone/scripts/set/unique.m
> 
>   syntax error
> 
> error: called from:
> error:   
> /Users/bpabbott/Development/mercurial/local_clone/scripts/optimization/__all_opts__.m
>  at line 56, column 11
> error:   
> /Users/bpabbott/Development/mercurial/local_clone/scripts/optimization/PKG_ADD
>  at line 1, column 0
> 
> make[3]: *** [doc-cache] Error 1
> make[2]: *** [all-recursive] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
> ben-abbotts-macbook-pro:local

>From config.log, it appears that the proper flex was found.

configure:47631: checking for flex
configure:47647: found /sw/lib/flex/bin/flex

... and its version is > 2.5.30 ...

$ /sw/lib/flex/bin/flex --version
flex 2.5.35

At the top of lex.ll I see

  25 %option prefix = "octave_"
  26 
  27 %top {
  28 #ifdef HAVE_CONFIG_H
  29 #include <config.h>
  30 #endif
  31 }

If I reinstate the reverted changeset below ...

        http://hg.savannah.gnu.org/hgweb/octave/rev/e6441e13acb2

... then all works as expected. I realize that reinstating this change is not 
the proper fix. I did it to verify the context of the problem.

My last successful build occurred after the changeset below

        http://hg.savannah.gnu.org/hgweb/octave/rev/323c9cbbd02a

Does anyone have an idea of what changed that could produce this problem?

Ben





reply via email to

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