octave-maintainers
[Top][All Lists]
Advanced

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

Re: Default not compiling


From: Daniel J Sebald
Subject: Re: Default not compiling
Date: Thu, 20 Sep 2012 15:03:35 -0500
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16

On 09/20/2012 02:46 PM, Jordi Gutiérrez Hermoso wrote:
On 20 September 2012 15:39, Daniel J Sebald<address@hidden>  wrote:
Not sure.  My fresh build has a problem with Fwarning

../../octave/libinterp/octave-value/ov-usr-fcn.cc: In member function 'void
octave_user_function::restore_warning_states()':
../../octave/libinterp/octave-value/ov-usr-fcn.cc:675:42: error: 'Fwarning'
was not declared in this scope

I can't seem to find the declaration for that function anywhere.

A function named Ffoobar is the result of applying the DEFUN* family
of macros to a function named "foobar". Grep for " (foobar" (note the
space) to find where it should be defined.

HTH,
- Jordi G. H.

YID, thanks.

I see then this is one of the "use built-in function first" types of functions. What I'm seeing in the associated header file is

extern OCTINTERP_API void vwarning (const char *fmt, va_list args);
extern OCTINTERP_API void warning (const char *fmt, ...);

Is the first instance supposed to be "Fwarning"? Or is the code now supposed to be changed so that it calls "vwarning" rather than "Fwarning"?... Or neither?

Dan


reply via email to

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