octave-maintainers
[Top][All Lists]
Advanced

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

Re: MinGW build error: 'liboctave_warning_handler' undeclared


From: Philip Nienhuis
Subject: Re: MinGW build error: 'liboctave_warning_handler' undeclared
Date: Fri, 24 Aug 2012 23:18:11 +0200
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100701 SeaMonkey/2.0.6

John W. Eaton wrote:
On 24-Aug-2012, Philip Nienhuis wrote:

| But now I'm back at:
|
|
| :
| In file included from lex.ll:79:0:
| ../../octave/libinterp/parse-tree/octave.gperf: In static member
| function 'static unsigned int octave_kw_hash::hash(const char*, unsigned
| int)':
| ../../octave/libinterp/parse-tree/octave.gperf:130:49: warning: use of
| old-style cast
| ../../octave/libinterp/parse-tree/octave.gperf:136:49: warning: use of
| old-style cast
| In file included from parse-tree/lex.cc:1559:0:
| ../libgnu/unistd.h: At global scope:
| ../libgnu/unistd.h:1273:1: error: explicit qualification in declaration
| of 'gnulib::isatty'
|
| (see
| 
http://octave.1599824.n4.nabble.com/MinGW-libgnu-unistd-h-1259-1-error-explicit-qualification-in-declaration-of-gnulib-isatty-td4630511.html
|     and
| 
https://mailman.cae.wisc.edu/pipermail/octave-maintainers/2012-June/028534.html
| )
|
| Hmmm it is an old problem, I forgot about my June 4 post... I probably
| gave up the Octave-MinGW build after that...

I don't know what is causing this problem, but it I suspect it is a a
problem with gnulib.

I can try to take a look at it if you add -save-temps to the command
that compiles lex.cc and send me the resulting lex.ii file.

I couldn't find lex.cc in the current sources. Only lex.h and lex.ll are present. I checked this on a recently checked out fresh hg clone.

Extremely intriguing as lex.cc is explicitly mentioned in the error mesaage itself ("In file included from parse-tree/lex.cc:").

Philip


reply via email to

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