[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 14:47:14 -0500 |
On Friday, February 12, 2010, at 01:35PM, "John W. Eaton" <address@hidden>
wrote:
>On 12-Feb-2010, Ben Abbott wrote:
>
>| 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
>
>As I recall from the last time this problem came up, there was some
>problem with the version of flex distributed by Apple. Where did your
>copy of 2.5.35 come from?
>
>jwe
>
The sources come from sourceforge and the package from Fink.
http://pdb.finkproject.org/pdb/package.php/flex-devel
I experimented a bit to try to narrow down the problem. Since everything worked
a few days ago, I tried reverting the untabify changeset, and obtained a
functional result. Then I restored the current lex.ll ... and Octave builds and
runs without the problem.
I'm confused, but I think it clear something was wrong on my end.
Sorry for the noise.
Ben