Re: octave on development level

[c.]

On 29 Sep 2013, at 00:38, Werner Koenig <address@hidden> wrote:

> Hello list,
> 
> I want to install a parallel version of octave on development level

what do you mean exactly by "a parallel version"?

> on my
> openSuse 12.3 distribution. So I get the source via
> hg clone http://www.octave.org/hg/octave
> after a ./bootstrap and ./configure --prefix=/opt/octave which works
> properly, I get an error by make
> -> Entering directory `/home/.../libinterp'
> -> WARNING: 'flex' is missing on your system.
> -> *** [corefcn/oct-tex-lexer.cc] Fehler 1
> 
> I am sure properly install a flex on my system.

if you have, then for some reason it cannot be found at compile time.
What does the flex-related section in config.log say?

It looks like the following on my system (OS X 10.8.5) it should be something
similar for you, if it contains errors, instead, those errors might
give you an hint about where to start with debugging:

configure:7838: checking for flex
configure:7854: found /opt/local/bin/flex
configure:7865: result: flex
configure:7903: flex conftest.l
configure:7907: $? = 0
configure:7909: checking lex output file root
configure:7923: result: lex.yy
configure:7928: checking lex library
configure:7942: /opt/local/bin/gcc-mp-4.7 -o conftest -pipe -O2 -m64 
-D_THREAD_SAFE -I/opt/local/include -L/opt/local/lib -m64  conftest.c -lfl  >&5
configure:7942: $? = 0
configure:7952: result: -lfl
configure:7958: checking whether yytext is a pointer
configure:7975: /opt/local/bin/gcc-mp-4.7 -o conftest -pipe -O2 -m64 
-D_THREAD_SAFE -I/opt/local/include -L/opt/local/lib -m64  conftest.c -lfl  >&5
configure:7975: $? = 0
configure:7983: result: yes
configure:8003: result: defining LFLAGS to be -I
configure:8031: checking for bison
configure:8047: found /opt/local/bin/bison
configure:8058: result: bison -y
configure:8077: checking syntax of bison push/pull declaration
configure:8121: result: dash 


> What can I do, to get
> an octave program at development level.

If you want to work "at development level" you should be prepared to identify 
and fix such build issues, just dig into the code and try to see if you can find
the source of the error.

> So long Werner

HTH,
c.