Nabble - Octave - Bugs

Re: can't compile development version

2009-12-03T01:43:17Z

you were right. I installed libcurl and
the compilation went fine.

Thank You,

Bertrand

On Thu, 2009-12-03 at 01:49 -0500, John W. Eaton wrote:

> On 3-Dec-2009, Bertrand Roessli wrote:
>
> | I use gfortran and gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4)
> |
> | Bertrand Roessli
> |
> |
> | On Wed, 2009-12-02 at 14:36 -0500, John W. Eaton wrote:
> | > On 2-Dec-2009, Bertrand Roessli wrote:
> | >
> | > | I tried to compile the last development version
> | > | and got this error
> | > |
> | > | DLD-FUNCTIONS/urlwrite.cc:1427: error: expected ',' or '...' before '&'
> | > | token
> | > | DLD-FUNCTIONS/urlwrite.cc:1428: error: ISO C++ forbids declaration of
> | > | 'curl_handle' with no type
> | > | DLD-FUNCTIONS/urlwrite.cc: In function 'string_vector
> | > | mput_directory(int)':
> | >
> | > It works fine for me. What compiler are you using?
>
> I think this is a duplicate of the problem reported earlier:
>
> https://www-old.cae.wisc.edu/pipermail/bug-octave/2009-November/009925.html
>

_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Re: can't compile development version

2009-12-02T23:53:49Z

On 3-Dec-2009, Jaroslav Hajek wrote:

| 1. I can't find an autoconf feature designed to test enum members. Is
| there one? If not, perhaps we can write a general one for Octave?

I don't know of one and I don't see one in the autoconf macro
archive. I guess it just needs to be an AC_TRY_COMPILE with the
appropriate headers and a simple use of the required enum member.

| 2. Should the extra check be integrated into the OCTAVE_CHECK_LIBRARY,
| or is it preferable to do something like
| if $octave_curl_ok ; then
| .. check
| fi

I think you could use the AC_TRY_COMPILE macro in the the EXTRA-CHECK
argument passed to the OCTAVE_CHECK_LIBRARY macro used for checking
for libcurl. There are a couple of examples of this usage now. Look
at the checks for the qhull and hdf5 libraries.

jwe
_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Re: can't compile development version

2009-12-02T22:53:00Z

On Thu, Dec 3, 2009 at 7:49 AM, John W. Eaton <jwe@...> wrote:

Hi John,

before I try to fix it, I have 2 questions:

1. I can't find an autoconf feature designed to test enum members. Is
there one? If not, perhaps we can write a general one for Octave?
2. Should the extra check be integrated into the OCTAVE_CHECK_LIBRARY,
or is it preferable to do something like
if $octave_curl_ok ; then
.. check
fi

--
RNDr. Jaroslav Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz

_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Re: can't compile development version

2009-12-02T22:49:09Z

On 3-Dec-2009, Bertrand Roessli wrote:

| I use gfortran and gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4)
|
| Bertrand Roessli
|
|
| On Wed, 2009-12-02 at 14:36 -0500, John W. Eaton wrote:
| > On 2-Dec-2009, Bertrand Roessli wrote:
| >
| > | I tried to compile the last development version
| > | and got this error
| > |
| > | DLD-FUNCTIONS/urlwrite.cc:1427: error: expected ',' or '...' before '&'
| > | token
| > | DLD-FUNCTIONS/urlwrite.cc:1428: error: ISO C++ forbids declaration of
| > | 'curl_handle' with no type
| > | DLD-FUNCTIONS/urlwrite.cc: In function 'string_vector
| > | mput_directory(int)':
| >
| > It works fine for me. What compiler are you using?

I think this is a duplicate of the problem reported earlier:

https://www-old.cae.wisc.edu/pipermail/bug-octave/2009-November/009925.html

--
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

windows build when installing the database package

2009-12-02T22:47:47Z

On 2-Dec-2009, CoolHanDrew wrote:

| I get a problem in the windows build when installing the database package
|
| > pkg install database-1.0.4.tar.gz
| odbc_wrap.cpp: In member function 'void octave_swig_type::install_global()':
| odbc_wrap.cpp:1197: error: 'curr_sym_tab' was not declared in this scope
| odbc_wrap.cpp:1197: error: 'link_to_global_variable' was not declared in
| this
| scope
| odbc_wrap.cpp:1204: error: 'symbol_record' was not declared in this scope
| odbc_wrap.cpp:1204: error: 'sr' was not declared in this scope
| odbc_wrap.cpp:1204: error: 'global_sym_tab' was not declared in this scope
| odbc_wrap.cpp: In function 'void SWIG_Octave_SetModule(void*,
| swig_module_info*)':
|
| etc.
|
| Does this package have a bug, or is there a dependency that I am missing?

What version of Octave are you using? I'm guessing it is 3.2.x and
that the database package has not been updated to use the newer symbol
table code that is in Octave 3.2.x.

The right place to report problems with packages is to the package
maintiner, not the bug@... list.

jwe
_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Re: can't compile development version

2009-12-02T22:37:17Z

I use gfortran and gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4)

Bertrand Roessli

On Wed, 2009-12-02 at 14:36 -0500, John W. Eaton wrote:

> On 2-Dec-2009, Bertrand Roessli wrote:
>
> | I tried to compile the last development version
> | and got this error
> |
> | DLD-FUNCTIONS/urlwrite.cc:1427: error: expected ',' or '...' before '&'
> | token
> | DLD-FUNCTIONS/urlwrite.cc:1428: error: ISO C++ forbids declaration of
> | 'curl_handle' with no type
> | DLD-FUNCTIONS/urlwrite.cc: In function 'string_vector
> | mput_directory(int)':
>
> It works fine for me. What compiler are you using?
>
> jwe

_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

windows build when installing the database package

2009-12-02T21:08:43Z

Hi all,

I get a problem in the windows build when installing the database package

> pkg install database-1.0.4.tar.gz
odbc_wrap.cpp: In member function 'void octave_swig_type::install_global()':
odbc_wrap.cpp:1197: error: 'curr_sym_tab' was not declared in this scope
odbc_wrap.cpp:1197: error: 'link_to_global_variable' was not declared in this
scope
odbc_wrap.cpp:1204: error: 'symbol_record' was not declared in this scope
odbc_wrap.cpp:1204: error: 'sr' was not declared in this scope
odbc_wrap.cpp:1204: error: 'global_sym_tab' was not declared in this scope
odbc_wrap.cpp: In function 'void SWIG_Octave_SetModule(void*,
swig_module_info*)':

etc.

Does this package have a bug, or is there a dependency that I am missing?

EDIT: I am using the build Octave-3.2.3-2_i686-pc-mingw32_gcc-4.4.0_setup.exe

Cheers,

Andrew

possible incorrect default for options.color in __default_plot_options__.m

2009-12-02T20:48:09Z

Bug report for Octave 3.2.3 configured for i686-pc-mingw32

Description:
-----------

It appears __default_plot_options__.m may set an invalid default for the options.color option, at least when used from __pltopt1__.m and/or __pltopt__.m.

Attempting to run the testfin script example from http://www.csse.uwa.edu.au/~pk/research/matlabfns/FingerPrints/Docs/index.html

results in:

> testfin
error: invalid value for color property "color"
error: called from:
error:   C:\Octave\3.2.3_gcc-4.4.0\share\octave\3.2.3\m\plot\__line__.m at line 65, column 5
error:   C:\Octave\3.2.3_gcc-4.4.0\share\octave\3.2.3\m\plot\line.m at line 38, column 5
error:   C:\Octave\3.2.3_gcc-4.4.0\share\octave\3.2.3\m\plot\__plt2vv__.m at line 72, column 12
error:   C:\Octave\3.2.3_gcc-4.4.0\share\octave\3.2.3\m\plot\__plt2__.m at line 68, column 14
error:   C:\Octave\3.2.3_gcc-4.4.0\share\octave\3.2.3\m\plot\__plt__.m at line 79, column 10
error:   C:\Octave\3.2.3_gcc-4.4.0\share\octave\3.2.3\m\plot\plot.m at line 186, column 5
error:   C:\Octave\3.2.3_gcc-4.4.0\share\octave\3.2.3\m\plot\__quiver__.m at line 311, column 5
error:   C:\Octave\3.2.3_gcc-4.4.0\share\octave\3.2.3\m\plot\quiver.m at line 74, column 7
error:   c:\archives\fp\algorithm\kovesi_vision_functions\MatlabFns\FingerPrints\plotridgeorient.m at line 71, column 1
error:   c:\archives\fp\algorithm\kovesi_vision_functions\testfin.m at line 37, column 5

Repeat-By:
---------

Install version of octave indicated by this bug report (I originally downloaded this pre-built windows/mingw version).

Obtain test script from:

http://www.csse.uwa.edu.au/~pk/research/matlabfns/FingerPrints/Docs/testfin.m

Obtain Peter Kovesi's function archive from:

http://www.csse.uwa.edu.au/~pk/research/MatlabFns.tar.gz

Expand Peter's function archive somewhere.

Execute octave, and do addpath()s on Peter's function archive tree for ...\FingerPrints, ...\Misc, ...\GreyTrans

Modify the testfin.m script to access the finger.png file in Peter's expanded tree at ...\MatLabFns\FingerPrints\Docs\finger.png

Execute the (modified) testfin.m script.

(Sorry, I have not attempted to repeat this reduced set of steps to see if I have it exactly correct, as my path to this point was a far longer, more circuitous route. But I hope it conveys sufficient information that someone more experienced than I should have no problem reproducing similar results.)

Fix:
---

(This may not be a correct fix, but avoids the reported error I see when following the above steps)

Edit <octave-dir>\...\share\3.2.3\m\plot\__default_plot_options__.m, and change the line:

" options.color = [] ;"

to be

" options.color = [0, 0, 0] ;"

Configuration (please do not edit this section):
-----------------------------------------------

uname output:     Windows
configure opts:
Fortran compiler: mingw32-gfortran-4.4.0-dw2
FFLAGS:           -O -mieee-fp
FLIBS:            -lgfortran
CPPFLAGS:
INCFLAGS:         -I. -I/octmgw32/octave/octave-3.2.3 -I. -I./liboctave -I./src -I./libcruft/misc -I/octmgw32/octave/octave-3.2.3 -I/octmgw32/octave/octave-3.2.3/liboctave -I/octmgw32/octave/octave-3.2.3/src -I/octmgw32/octave/octave-3.2.3/libcruft/misc
C compiler:       mingw32-gcc-4.4.0-dw2, version4.4.0 (GCC)
CFLAGS:           -march=i686 -mtune=generic -O3 -Wall
CPICFLAG:
C++ compiler:     mingw32-g++-4.4.0-dw2, version4.4.0
CXXFLAGS:         -D_GLIBCXX_DLL -march=i686 -mtune=generic -O3 -Wall
CXXPICFLAG:
LD_CXX:           mingw32-g++-4.4.0-dw2
LDFLAGS:          -shared-libgcc -Wl,--allow-multiple-definition
LIBFLAGS:         -L.
RLD_FLAG:
BLAS_LIBS:        -llapack -lblas
FFTW_LIBS:        -lfftw3 -lfftw3f
LIBS:             -lreadline -lncurses -liberty -lhdf5 -lz -lm -lgdi32 -lws2_32 -luser32 -lkernel32
LEXLIB:
LIBGLOB:          -lglob
SED:              /usr/bin/sed
DEFS:
-DPACKAGE_NAME="" -DPACKAGE_TARNAME="" -DPACKAGE_VERSION="" -DPACKAGE_STRING="" -DPACKAGE_BUGREPORT="" -DOCTAVE_SOURCE=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -D__EXTENSIONS__=1 -D_ALL_SOURCE=1 -D_GNU_SOURCE=1 -D_POSIX_PTHREAD_SEMANTICS=1 -D_TANDEM_SOURCE=1 -DSEPCHAR=';' -DSEPCHAR_STR=";" -D__NO_MATH_INLINES=1 -DCXX_NEW_FRIEND_TEMPLATE_DECL=1 -DCXX_ISO_COMPLIANT_LIBRARY=1 -DHAVE_X_WINDOWS=1 -DHAVE_LIBM=1 -DHAVE_QHULL=1 -DHAVE_PCRE_COMPILE=1 -DHAVE_PCRE=1 -DHAVE_REGEX=1 -DHAVE_ZLIB_H=1 -DHAVE_ZLIB=1 -DHAVE_HDF5_H=1 -DHAVE_HDF5=1 -DHAVE_H5GGET_NUM_OBJS=1 -DHAVE_FFTW3=1 -DHAVE_GLPK_GLPK_H=1 -DHAVE_GLPK=1 -DHAVE_CURL_CURL_H=1 -DHAVE_CURL=1 -DHAVE_MAGICK=1 -DHAVE_WINDOWS_H=1 -DHAVE_GL_GL_H=1 -DHAVE_GL_GLU_H=1 -DHAVE_OPENGL=1 -DHAVE_FTGL_FTGL_H=1 -DHAVE_FTGL=1 -DHAVE_FLTK=1 -DHAVE_IEEE754_DATA_FORMAT=1 -DF77_FUNC(name,NAME)=name ## _ -DF77_FUNC_(name,NAME)=name ## _ -DHAVE_BLAS=1 -DHAVE_QRUPDATE=1 -DHAVE_SUITESPARSE_AMD_H=1 -DHAVE_AMD=1 -DHAVE_SUITESPARSE_UMFPACK_H=1 -DHAVE_UMFPACK=1 -DUMFPACK_SEPARATE_SPLIT=1 -DHAVE_SUITESPARSE_COLAMD_H=1 -DHAVE_COLAMD=1 -DHAVE_SUITESPARSE_CCOLAMD_H=1 -DHAVE_CCOLAMD=1 -DHAVE_SUITESPARSE_CHOLMOD_H=1 -DHAVE_CHOLMOD=1 -DHAVE_SUITESPARSE_CS_H=1 -DHAVE_CXSPARSE=1 -DHAVE_ARPACK=1 -Duid_t=int -Dgid_t=int -DHAVE_DEV_T=1 -DHAVE_INO_T=1 -DHAVE_LONG_LONG_INT=1 -DHAVE_UNSIGNED_LONG_LONG_INT=1 -DHAVE_SIGSET_T=1 -DHAVE_SIG_ATOMIC_T=1 -DSIZEOF_SHORT=2 -DSIZEOF_INT=4 -DSIZEOF_LONG=4 -DSIZEOF_LONG_LONG=8 -DHAVE_ALLOCA=1 -DHAVE_PLACEMENT_DELETE=1 -DHAVE_DYNAMIC_AUTO_ARRAYS=1 -DHAVE_FAST_INT_OPS=1 -DSIZEOF_LONG_DOUBLE=12 -DSTDC_HEADERS=1 -DHAVE_DIRENT_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_ASSERT_H=1 -DHAVE_CURSES_H=1 -DHAVE_DIRECT_H=1 -DHAVE_FCNTL_H=1 -DHAVE_FLOAT_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_LIMITS_H=1 -DHAVE_LOCALE_H=1 -DHAVE_MEMORY_H=1 -DHAVE_NCURSES_H=1 -DHAVE_PTHREAD_H=1 -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_UTIME_H=1 -DHAVE_TERMCAP_H=1 -DHAVE_UNISTD_H=1 -DHAVE_UTIME_H=1 -DHAVE_SSTREAM=1 -DHAVE_GLOB_H=1 -DHAVE_FNMATCH_H=1 -DHAVE_CONIO_H=1 -DHAVE_ATEXIT=1 -DHAVE_BASENAME=1 -DHAVE_CHMOD=1 -DHAVE_DUP2=1 -DHAVE_EXECVP=1 -DHAVE_EXPM1=1 -DHAVE_EXPM1F=1 -DHAVE_FSTAT=1 -DHAVE_GETCWD=1 -DHAVE_GETPID=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE__KBHIT=1 -DHAVE_LGAMMA=1 -DHAVE_LGAMMAF=1 -DHAVE_LOG1P=1 -DHAVE_LOG1PF=1 -DHAVE_MEMMOVE=1 -DHAVE_MKDIR=1 -DHAVE_PUTENV=1 -DHAVE_RAISE=1 -DHAVE_RENAME=1 -DHAVE_RMDIR=1 -DHAVE_ROUNDL=1 -DHAVE_SETLOCALE=1 -DHAVE_SETVBUF=1 -DHAVE_SNPRINTF=1 -DHAVE_STAT=1 -DHAVE_STRCASECMP=1 -DHAVE_STRDUP=1 -DHAVE_STRERROR=1 -DHAVE_STRICMP=1 -DHAVE_STRNCASECMP=1 -DHAVE_STRNICMP=1 -DHAVE_TEMPNAM=1 -DHAVE_TGAMMAF=1 -DHAVE_TRUNC=1 -DHAVE_UMASK=1 -DHAVE_UNLINK=1 -DHAVE_USLEEP=1 -DHAVE_UTIME=1 -DHAVE_VFPRINTF=1 -DHAVE_VSPRINTF=1 -DHAVE_VSNPRINTF=1 -DHAVE__CHMOD=1 -DHAVE__SNPRINTF=1 -DHAVE_DECL_EXP2=1 -DHAVE_DECL_ROUND=1 -DHAVE_DECL_TGAMMA=1 -DHAVE_EXP2=1 -DHAVE_ROUND=1 -DHAVE_TGAMMA=1 -DHAVE_MKSTEMPS=1 -DHAVE_C99_VSNPRINTF=1 -DOCTAVE_HAVE_BROKEN_STRPTIME=1 -D_WIN32_WINNT=0x0403 -DHAVE_LOADLIBRARY_API=1 -DENABLE_DYNAMIC_LINKING=1 -DHAVE_TIMEVAL=1 -DHAVE_CMATH_ISNAN=1 -DHAVE_CMATH_ISNANF=1 -DHAVE_CMATH_ISINF=1 -DHAVE_CMATH_ISINFF=1 -DHAVE_CMATH_ISFINITE=1 -DHAVE_CMATH_ISFINITEF=1 -DHAVE_FINITE=1 -DHAVE_ISNAN=1 -DHAVE_COPYSIGN=1 -DHAVE_SIGNBIT=1 -DHAVE__FINITE=1 -DHAVE__ISNAN=1 -DHAVE__COPYSIGN=1 -DHAVE_DECL_SIGNBIT=1 -DHAVE_ACOSH=1 -DHAVE_ACOSHF=1 -DHAVE_ASINH=1 -DHAVE_ASINHF=1 -DHAVE_ATANH=1 -DHAVE_ATANHF=1 -DHAVE_ERF=1 -DHAVE_ERFF=1 -DHAVE_ERFC=1 -DHAVE_ERFCF=1 -DHAVE_EXP2F=1 -DHAVE_LOG2=1 -DHAVE_LOG2F=1 -DHAVE_HYPOTF=1 -DHAVE_STRUCT_STAT_ST_RDEV=1 -DHAVE_DECL_TZNAME=1 -DHAVE_TZNAME=1 -DMKDIR_TAKES_ONE_ARG=1 -DUSE_READLINE=1 -DRETSIGTYPE=void -DHAVE_DECL_SYS_SIGLIST=0 -DMUST_REINSTALL_SIGHANDLERS=1 -DRETSIGTYPE_IS_VOID=1

User-preferences (please do not edit this section):

EDITOR = C:\Octave\3.2.3_gcc-4.4.0\tools\notepad++\notepad++.exe
EXEC_PATH = C:\Octave\3.2.3_gcc-4.4.0\MINGW32\bin;C:\Octave\3.2.3_gcc-4.4.0\MSYS\bin;C:\Octave\3.2.3_gcc-4.4.0\libexec\octave\3.2.3\site\exec\i686-pc-mingw32;C:\Octave\3.2.3_gcc-4.4.0\libexec\octave\api-v37\site\exec\i686-pc-mingw32;C:\Octave\3.2.3_gcc-4.4.0\libexec\octave\site\exec\i686-pc-mingw32;C:\Octave\3.2.3_gcc-4.4.0\libexec\octave\3.2.3\exec\i686-pc-mingw32;C:\Octave\3.2.3_gcc-4.4.0\bin;C:\Oracle\product\10.1.0\Client_1\bin;C:\Oracle\product\10.1.0\Client_1\jre\1.4.2\bin\client;C:\Oracle\product\10.1.0\Client_1\jre\1.4.2\bin;C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\;C:\Program Files\Borland\BDS\4.0\Bin;C:\Perl\bin\;c:\oracle\ora10gt_dev\bin;C:\PROGRA~1\Borland\CBUILD~1\Bin;C:\PROGRA~1\Borland\CBUILD~1\Projects\Bpl;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Subversion\bin;C:\Program Files\Haskell\bin;C:\ghc\ghc-6.8.2\bin;C:\Documents and Settings\Steve\My Documents\Borland Studio Projects\Bpl
IMAGE_PATH = .;C:\Octave\3.2.3_gcc-4.4.0\share\octave\3.2.3\imagelib
PAGER = C:\Octave\3.2.3_gcc-4.4.0\bin\less.exe
PS1 = \s:\#:\w
>
PS2 = >
PS4 = +
beep_on_error = 0
completion_append_char =
crash_dumps_octave_core = 1
echo_executing_commands = 0
fixed_point_format = 0
gnuplot_binary = C:\Octave\3.2.3_gcc-4.4.0\bin\gnuplot.exe
# gnuplot_command_end = <no value or error in displaying it>
# gnuplot_command_plot = <no value or error in displaying it>
# gnuplot_command_replot = <no value or error in displaying it>
# gnuplot_command_splot = <no value or error in displaying it>
# gnuplot_command_title = <no value or error in displaying it>
# gnuplot_command_using = <no value or error in displaying it>
# gnuplot_command_with = <no value or error in displaying it>
history_file = C:\Documents and Settings\Steve\.octave_hist
history_size = 1024
ignore_function_time_stamp = none
info_file = C:\Octave\3.2.3_gcc-4.4.0\share\info\octave.info
info_program = info
makeinfo_program = makeinfo
max_recursion_depth = 256
output_max_field_width = 5
output_precision = 5
page_output_immediately = 0
page_screen_output = 1
# print_answer_id_name = <no value or error in displaying it>
print_empty_dimensions = 1
save_precision = 16
saving_history = 1
sighup_dumps_octave_core = 1
sigterm_dumps_octave_core = 1
silent_functions = 0
split_long_rows = 1
string_fill_char =
struct_levels_to_print = 2
suppress_verbose_help_message = 0

Chat with Messenger straight from your Hotmail inbox. Check it out
_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Re: CURLOPT_USERNAME in urwrite.c

2009-12-02T16:52:10Z

On Dec 2, 2009, at 6:51 PM, Petr Mikulik wrote:

> Compilation of developer's Octave version fails on urlwrite.cc:
>
> libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I../libcruft/misc
> -I../liboctave -I../liboctave -I. -I. -g -O2 -DHAVE_CONFIG_H -mieee-fp
> -I/usr/include/freetype2 -Wall -W -Wshadow -Wold-style-cast -Wformat -g -O2
> -pthread -g -O2 -MT DLD-FUNCTIONS/DLD_FUNCTIONS_urlwrite_la-urlwrite.lo -MD
> -MP -MF DLD-FUNCTIONS/.deps/DLD_FUNCTIONS_urlwrite_la-urlwrite.Tpo -c
> DLD-FUNCTIONS/urlwrite.cc -fPIC -DPIC -o
> DLD-FUNCTIONS/.libs/DLD_FUNCTIONS_urlwrite_la-urlwrite.o
> DLD-FUNCTIONS/urlwrite.cc: In member function ‘void curl_handle::init(const
> std::string&, const std::string&, std::istream&, std::ostream&)’:
> DLD-FUNCTIONS/urlwrite.cc:566: error: ‘CURLOPT_USERNAME’ was not declared in
> this scope
> DLD-FUNCTIONS/urlwrite.cc:568: error: ‘CURLOPT_PASSWORD’ was not declared in
> this scope
> make[3]: *** [DLD-FUNCTIONS/DLD_FUNCTIONS_urlwrite_la-urlwrite.lo] Error 1
>
>
> My system is OpenSUSE 11.1 with
>
> $ rpm -qa | grep curl
> curl-7.19.0-11.3.1
> libcurl-devel-7.19.0-11.3.1
> libcurl4-7.19.0-11.3.1
>
> /usr/include/curl$ grep USER typecheck-gcc.h
> (option) == CURLOPT_USERPWD || \
> (option) == CURLOPT_PROXYUSERPWD || \
> (option) == CURLOPT_USERAGENT || \
> (option) == CURLOPT_FTP_ALTERNATIVE_TO_USER || \
>
> /usr/include/curl$ grep 0x07 curlver.h
> #define LIBCURL_VERSION_NUM 0x071300
>
>
> I think these two lines in urlwrite.cc:
>
> #if (LIBCURL_VERSION_NUM >= 0x071300)
> // This is possible since cURL 7.19.
>
> should be changed to
>
> #if (LIBCURL_VERSION_NUM >= 0x071301)
> // This is possible since cURL 7.19.1
>
> or whichever version introduced CURLOPT_USERNAME.

Petr,

I think you are correct, the link below indicates that CURLOPT_PASSWORD was introduced in 7.19.1

http://curl.haxx.se/libcurl/c/curl_easy_setopt.html

Jaroslav,

I'm not presently able to build successfully. Can you fix this?

Ben

_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

CURLOPT_USERNAME in urwrite.c

2009-12-02T16:42:35Z

On 3-Dec-2009, Petr Mikulik wrote:

| Compilation of developer's Octave version fails on urlwrite.cc:
|
| libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I../libcruft/misc
| -I../liboctave -I../liboctave -I. -I. -g -O2 -DHAVE_CONFIG_H -mieee-fp
| -I/usr/include/freetype2 -Wall -W -Wshadow -Wold-style-cast -Wformat -g -O2
| -pthread -g -O2 -MT DLD-FUNCTIONS/DLD_FUNCTIONS_urlwrite_la-urlwrite.lo -MD
| -MP -MF DLD-FUNCTIONS/.deps/DLD_FUNCTIONS_urlwrite_la-urlwrite.Tpo -c
| DLD-FUNCTIONS/urlwrite.cc -fPIC -DPIC -o
| DLD-FUNCTIONS/.libs/DLD_FUNCTIONS_urlwrite_la-urlwrite.o
| DLD-FUNCTIONS/urlwrite.cc: In member function ‘void curl_handle::init(const
| std::string&, const std::string&, std::istream&, std::ostream&)’:
| DLD-FUNCTIONS/urlwrite.cc:566: error: ‘CURLOPT_USERNAME’ was not declared in
| this scope
| DLD-FUNCTIONS/urlwrite.cc:568: error: ‘CURLOPT_PASSWORD’ was not declared in
| this scope
| make[3]: *** [DLD-FUNCTIONS/DLD_FUNCTIONS_urlwrite_la-urlwrite.lo] Error 1
|
|
| My system is OpenSUSE 11.1 with
|
| $ rpm -qa | grep curl
| curl-7.19.0-11.3.1
| libcurl-devel-7.19.0-11.3.1
| libcurl4-7.19.0-11.3.1
|
| /usr/include/curl$ grep USER typecheck-gcc.h
| (option) == CURLOPT_USERPWD || \
| (option) == CURLOPT_PROXYUSERPWD || \
| (option) == CURLOPT_USERAGENT || \
| (option) == CURLOPT_FTP_ALTERNATIVE_TO_USER || \
|
| /usr/include/curl$ grep 0x07 curlver.h
| #define LIBCURL_VERSION_NUM 0x071300
|
|
| I think these two lines in urlwrite.cc:
|
| #if (LIBCURL_VERSION_NUM >= 0x071300)
| // This is possible since cURL 7.19.
|
| should be changed to
|
| #if (LIBCURL_VERSION_NUM >= 0x071301)
| // This is possible since cURL 7.19.1
|
| or whichever version introduced CURLOPT_USERNAME.

As I said earlier, I think we should avoid using version number checks
in Octave code and instead use a feature test in the configure script.

Would someone like to submit a patch for that?

Thanks,

jwe
_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

CURLOPT_USERNAME in urwrite.c

2009-12-02T15:51:11Z

Compilation of developer's Octave version fails on urlwrite.cc:

libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I../libcruft/misc
-I../liboctave -I../liboctave -I. -I. -g -O2 -DHAVE_CONFIG_H -mieee-fp
-I/usr/include/freetype2 -Wall -W -Wshadow -Wold-style-cast -Wformat -g -O2
-pthread -g -O2 -MT DLD-FUNCTIONS/DLD_FUNCTIONS_urlwrite_la-urlwrite.lo -MD
-MP -MF DLD-FUNCTIONS/.deps/DLD_FUNCTIONS_urlwrite_la-urlwrite.Tpo -c
DLD-FUNCTIONS/urlwrite.cc -fPIC -DPIC -o
DLD-FUNCTIONS/.libs/DLD_FUNCTIONS_urlwrite_la-urlwrite.o
DLD-FUNCTIONS/urlwrite.cc: In member function ‘void curl_handle::init(const
std::string&, const std::string&, std::istream&, std::ostream&)’:
DLD-FUNCTIONS/urlwrite.cc:566: error: ‘CURLOPT_USERNAME’ was not declared in
this scope
DLD-FUNCTIONS/urlwrite.cc:568: error: ‘CURLOPT_PASSWORD’ was not declared in
this scope
make[3]: *** [DLD-FUNCTIONS/DLD_FUNCTIONS_urlwrite_la-urlwrite.lo] Error 1

My system is OpenSUSE 11.1 with

$ rpm -qa | grep curl
curl-7.19.0-11.3.1
libcurl-devel-7.19.0-11.3.1
libcurl4-7.19.0-11.3.1

/usr/include/curl$ grep USER typecheck-gcc.h
(option) == CURLOPT_USERPWD || \
(option) == CURLOPT_PROXYUSERPWD || \
(option) == CURLOPT_USERAGENT || \
(option) == CURLOPT_FTP_ALTERNATIVE_TO_USER || \

/usr/include/curl$ grep 0x07 curlver.h
#define LIBCURL_VERSION_NUM 0x071300

I think these two lines in urlwrite.cc:

#if (LIBCURL_VERSION_NUM >= 0x071300)
// This is possible since cURL 7.19.

should be changed to

#if (LIBCURL_VERSION_NUM >= 0x071301)
// This is possible since cURL 7.19.1

or whichever version introduced CURLOPT_USERNAME.

---
PM
_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Re: Add support for determining Octave version into C++ headers

2009-12-02T13:15:46Z

On 2-Dec-2009, William S Fulton wrote:

| preprocessor rather than autoconf? For example, what feature is needed
| to fix these API changes introduced somewhere around Octave 3.2:
|
| example_wrap.cxx:1209: error: ‘varref’ is not a member of ‘symbol_table’
| example_wrap.cxx:1210: error: ‘mark_global’ is not a member of
| ‘symbol_table’

What are you trying to do here? Why are you accessing the symbol
table directly?

If you are trying to access global variables, you should probably be
using the get_global_value and set_global_value functions that are
declared in variables.h. These functions have been around in this
form for quite some time now.

If you are trying to do something else then I suggest posting the code
you are having trouble with to the help list. Maybe someone there
could help you write it in a way that would just work.

jwe
_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Re: Add support for determining Octave version into C++ headers

2009-12-02T13:00:00Z

On 2-Dec-2009, Jaroslav Hajek wrote:

| Maybe instead of version numbers, we could provide #defines for notable changes?
| Something like
| #define HAVE_NEW_UNWIND_PROTECT_API

I think that just leads to a bigger mess. Do we later have to add

HAVE_NEW_NEW_REALLY_REALLY_NEW_UNWIND_PROTECT_API

?

| or better
| #define UNWIND_PROTECT_API 1
| and then use
| #if (UNWIND_PROTECT_API >= 1)

I don't think we want to have to remember to increment one (or more)
of a multitude of version numbers every time a change is made to the
internals of Octave.

If people want a stable API of some sort, then I suggest that the
people interested in such a thing start proposing what that API should
be.

jwe
_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Re: Add support for determining Octave version into C++ headers

2009-12-02T12:33:17Z

John W. Eaton wrote:

> On 2-Dec-2009, William S Fulton wrote:
>
> | --------
> | Bug report for Octave 3.0.1 configured for i486-pc-linux-gnu
> |
> | Description:
> | -----------
> |
> | It isn't possible to deal with the changing non-backwards compatible
> C++
> | APIs in
> | Octave (version 3.2 broke lots of APIs) as the version macros in the
> C++
> | headers do
> | not allow one to write different code for different versions of Octave.
> | The problem
> | is that the version is held in a string and not as a number. It is
> | impossible for the C++
> | preprocessor to work with strings.
> |
> | Fix:
> | ---
> |
> | In src/version.h the version macro contains:
> |
> | #define OCTAVE_API_VERSION "api-v37"
> |
> | Please add an additional numeric macro, something like:
> |
> | #define OCTAVE_API_VERSION_NUMERIC 37
> |
> | Please do this urgently before you release any more versions as without
> | it is
> | impossible to write C++ extensions to work more than one version of
> Octave.
>
> It is not impossible. I recommend that instead of testing version
> numbers, you use some kind of configure script that checks for the
> features you need. If you insist on using version numbers, then your
> configure script can be as simple as printing out the Octave version
> number and comparing it to whatever you think it is you need. But I
> would strongly recommend that you check for features, not version
> numbers.

John, thanks for this suggestion. Unfortunately we do not have control
over how users build their software and certainly can't rely on them
using autoconf. We would like to generate extensions that just work with
whatever version of Octave they happen to have installed. With the
feature idea, is there a way to check for features using the
preprocessor rather than autoconf? For example, what feature is needed
to fix these API changes introduced somewhere around Octave 3.2:

example_wrap.cxx:1209: error: ‘varref’ is not a member of ‘symbol_table’
example_wrap.cxx:1210: error: ‘mark_global’ is not a member of
‘symbol_table’

As Octave already has an API version, at least consider making this
version usable from the preprocessor, it is a really simple solution
that all major scripting languages that support C/C++ extensions have in
place.

Regards
William
_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Re: Add support for determining Octave version into C++ headers

2009-12-02T12:20:01Z

On Wed, Dec 2, 2009 at 8:36 PM, John W. Eaton <jwe@...> wrote:

> On 2-Dec-2009, William S Fulton wrote:
>
> | --------
> | Bug report for Octave 3.0.1 configured for i486-pc-linux-gnu
> |
> | Description:
> | -----------
> |
> | It isn't possible to deal with the changing non-backwards compatible C++
> | APIs in
> | Octave (version 3.2 broke lots of APIs) as the version macros in the C++
> | headers do
> | not allow one to write different code for different versions of Octave.
> | The problem
> | is that the version is held in a string and not as a number. It is
> | impossible for the C++
> | preprocessor to work with strings.
> |
> | Fix:
> | ---
> |
> | In src/version.h the version macro contains:
> |
> | #define OCTAVE_API_VERSION "api-v37"
> |
> | Please add an additional numeric macro, something like:
> |
> | #define OCTAVE_API_VERSION_NUMERIC 37
> |
> | Please do this urgently before you release any more versions as without
> | it is
> | impossible to write C++ extensions to work more than one version of Octave.
>
> It is not impossible. I recommend that instead of testing version
> numbers, you use some kind of configure script that checks for the
> features you need. If you insist on using version numbers, then your
> configure script can be as simple as printing out the Octave version
> number and comparing it to whatever you think it is you need. But I
> would strongly recommend that you check for features, not version
> numbers.
>
> jwe

I agree this method is preferable in most cases, unless you really
want to have a single self-contained C++ file.

Maybe instead of version numbers, we could provide #defines for notable changes?
Something like
#define HAVE_NEW_UNWIND_PROTECT_API
or better
#define UNWIND_PROTECT_API 1
and then use
#if (UNWIND_PROTECT_API >= 1)

--
RNDr. Jaroslav Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz

_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

can't compile development version

2009-12-02T11:36:57Z

On 2-Dec-2009, Bertrand Roessli wrote:

| I tried to compile the last development version
| and got this error
|
| DLD-FUNCTIONS/urlwrite.cc:1427: error: expected ',' or '...' before '&'
| token
| DLD-FUNCTIONS/urlwrite.cc:1428: error: ISO C++ forbids declaration of
| 'curl_handle' with no type
| DLD-FUNCTIONS/urlwrite.cc: In function 'string_vector
| mput_directory(int)':

It works fine for me. What compiler are you using?

jwe
_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Add support for determining Octave version into C++ headers

2009-12-02T11:36:12Z

On 2-Dec-2009, William S Fulton wrote:

| --------
| Bug report for Octave 3.0.1 configured for i486-pc-linux-gnu
|
| Description:
| -----------
|
| It isn't possible to deal with the changing non-backwards compatible C++
| APIs in
| Octave (version 3.2 broke lots of APIs) as the version macros in the C++
| headers do
| not allow one to write different code for different versions of Octave.
| The problem
| is that the version is held in a string and not as a number. It is
| impossible for the C++
| preprocessor to work with strings.
|
| Fix:
| ---
|
| In src/version.h the version macro contains:
|
| #define OCTAVE_API_VERSION "api-v37"
|
| Please add an additional numeric macro, something like:
|
| #define OCTAVE_API_VERSION_NUMERIC 37
|
| Please do this urgently before you release any more versions as without
| it is
| impossible to write C++ extensions to work more than one version of Octave.

It is not impossible. I recommend that instead of testing version
numbers, you use some kind of configure script that checks for the
features you need. If you insist on using version numbers, then your
configure script can be as simple as printing out the Octave version
number and comparing it to whatever you think it is you need. But I
would strongly recommend that you check for features, not version
numbers.

jwe
_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Add support for determining Octave version into C++ headers

2009-12-02T11:13:12Z

--------
Bug report for Octave 3.0.1 configured for i486-pc-linux-gnu

Description:
-----------

It isn't possible to deal with the changing non-backwards compatible C++
APIs in
Octave (version 3.2 broke lots of APIs) as the version macros in the C++
headers do
not allow one to write different code for different versions of Octave.
The problem
is that the version is held in a string and not as a number. It is
impossible for the C++
preprocessor to work with strings.

Fix:
---

In src/version.h the version macro contains:

#define OCTAVE_API_VERSION "api-v37"

Please add an additional numeric macro, something like:

#define OCTAVE_API_VERSION_NUMERIC 37

Please do this urgently before you release any more versions as without
it is
impossible to write C++ extensions to work more than one version of Octave.

Configuration (please do not edit this section):
-----------------------------------------------

uname output: Linux caracal 2.6.27-14-generic #1 SMP Mon Aug 31
13:01:41 UTC 2009 i686 GNU/Linux
configure opts: '--host=i486-linux-gnu' '--build=i486-linux-gnu'
'--prefix=/usr' '--datadir=/usr/share' '--libdir=/usr/lib'
'--libexecdir=/usr/lib' '--infodir=/usr/share/info'
'--mandir=/usr/share/man' '--with-blas=-lblas-3gf'
'--with-lapack=-llapackgf-3' '--with-hdf5' '--with-fftw'
'--enable-shared' '--enable-rpath' '--disable-static'
'build_alias=i486-linux-gnu' 'host_alias=i486-linux-gnu' 'CC=gcc'
'CFLAGS=-g -O2' 'LDFLAGS=-Wl,-Bsymbolic-functions' 'CPPFLAGS=' 'CXX=g++'
'CXXFLAGS=-g -O2' 'F77=gfortran' 'FFLAGS=-g -O2'
Fortran compiler: gfortran
FFLAGS: -O2 -g
F2C: @F2C@
F2CFLAGS: @F2CFLAGS@
FLIBS: -L/usr/lib/gcc/i486-linux-gnu/4.3.1
-L/usr/lib/gcc/i486-linux-gnu/4.3.1/../../../../lib -L/lib/../lib
-L/usr/lib/../lib -L/usr/lib/gcc/i486-linux-gnu/4.3.1/../../.. -lhdf5
-lz -lgfortranbegin -lgfortran -lm
CPPFLAGS:
INCFLAGS: -I. -I. -I./liboctave -I./src -I./libcruft/misc
C compiler: gcc, version 4.3.1 (Ubuntu 4.3.1-8ubuntu3)
CFLAGS: -O2 -g
CPICFLAG: -fPIC
C++ compiler: g++, version 4.3.1
CXXFLAGS: -O2 -g
CXXPICFLAG: -fPIC
LD_CXX: g++
LDFLAGS:
LIBFLAGS: -L.
RLD_FLAG: -Wl,-rpath -Wl,/usr/lib/octave-3.0.1
BLAS_LIBS: -llapackgf-3 -lblas-3gf
FFTW_LIBS: -lfftw3
LIBS: -lreadline -lncurses -ldl -lhdf5 -lz -lm
LEXLIB:
LIBGLOB:
SED: /bin/sed
DEFS:

-DPACKAGE_NAME="" -DPACKAGE_TARNAME="" -DPACKAGE_VERSION=""
-DPACKAGE_STRING="" -DPACKAGE_BUGREPORT="" -DOCTAVE_SOURCE=1
-D_GNU_SOURCE=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DSEPCHAR=':'
-DSEPCHAR_STR=":" -D__NO_MATH_INLINES=1 -DCXX_NEW_FRIEND_TEMPLATE_DECL=1
-DCXX_ISO_COMPLIANT_LIBRARY=1 -DCXX_ABI=unknown -DHAVE_LIBM=1
-DHAVE_QHULL=1 -DHAVE_PCRE=1 -DHAVE_REGEXEC=1 -DHAVE_REGEX=1
-DHAVE_ZLIB_H=1 -DHAVE_ZLIB=1 -DHAVE_HDF5_H=1 -DHAVE_HDF5=1
-DHAVE_H5GGET_NUM_OBJS=1 -DHAVE_FFTW3=1 -DHAVE_GLPK_H=1 -DHAVE_GLPK=1
-DHAVE_CURL_CURL_H=1 -DHAVE_CURL=1 -DHAVE_IEEE754_DATA_FORMAT=1
-DF77_FUNC(name,NAME)=name ## _ -DF77_FUNC_(name,NAME)=name ## _
-DHAVE_BLAS=1 -DHAVE_SUITESPARSE_UMFPACK_H=1 -DHAVE_UMFPACK=1
-DUMFPACK_SEPARATE_SPLIT=1 -DHAVE_SUITESPARSE_COLAMD_H=1
-DHAVE_COLAMD=1 -DHAVE_SUITESPARSE_CCOLAMD_H=1 -DHAVE_CCOLAMD=1
-DHAVE_SUITESPARSE_CHOLMOD_H=1 -DHAVE_CHOLMOD=1 -DHAVE_SUITESPARSE_CS_H=1
-DHAVE_CXSPARSE=1 -DHAVE_GETHOSTNAME=1 -DHAVE_GETPWNAM=1 -DHAVE_DEV_T=1
-DHAVE_INO_T=1 -DHAVE_NLINK_T=1 -DHAVE_NLINK_T=1 -DHAVE_LONG_LONG_INT=1
-DHAVE_UNSIGNED_LONG_LONG_INT=1 -DHAVE_SIGSET_T=1 -DHAVE_SIG_ATOMIC_T=1
-DSIZEOF_SHORT=2 -DSIZEOF_INT=4 -DSIZEOF_LONG=4 -DSIZEOF_LONG_LONG=8
-DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DNPOS=std::string::npos
-DHAVE_PLACEMENT_DELETE=1 -DHAVE_DYNAMIC_AUTO_ARRAYS=1 -DSTDC_HEADERS=1
-DHAVE_DIRENT_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_SYS_WAIT_H=1
-DHAVE_ASSERT_H=1 -DHAVE_CURSES_H=1 -DHAVE_DLFCN_H=1 -DHAVE_FCNTL_H=1
-DHAVE_FLOAT_H=1 -DHAVE_GRP_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_LIMITS_H=1
-DHAVE_LOCALE_H=1 -DHAVE_MEMORY_H=1 -DHAVE_NCURSES_H=1 -DHAVE_POLL_H=1
-DHAVE_PWD_H=1 -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_POLL_H=1
-DHAVE_SYS_RESOURCE_H=1 -DHAVE_SYS_SELECT_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMES_H=1 -DHAVE_SYS_TYPES_H=1
-DHAVE_SYS_UTSNAME_H=1 -DHAVE_TERMCAP_H=1 -DHAVE_UNISTD_H=1
-DHAVE_UTIME_H=1 -DHAVE_SSTREAM=1 -DHAVE_TERMIO_H=1 -DHAVE_SGTTY_H=1
-DHAVE_GLOB_H=1 -DHAVE_FNMATCH_H=1 -DHAVE_FNMATCH=1 -DHAVE_GLOB=1
-DHAVE_ATEXIT=1 -DHAVE_BASENAME=1 -DHAVE_BCOPY=1 -DHAVE_BZERO=1
-DHAVE_CANONICALIZE_FILE_NAME=1 -DHAVE_CHMOD=1 -DHAVE_DUP2=1
-DHAVE_ENDGRENT=1 -DHAVE_ENDPWENT=1 -DHAVE_EXECVP=1 -DHAVE_FCNTL=1
-DHAVE_FORK=1 -DHAVE_GETCWD=1 -DHAVE_GETEGID=1 -DHAVE_GETEUID=1
-DHAVE_GETGID=1 -DHAVE_GETGRENT=1 -DHAVE_GETGRGID=1 -DHAVE_GETGRNAM=1
-DHAVE_GETPGRP=1 -DHAVE_GETPID=1 -DHAVE_GETPPID=1 -DHAVE_GETPWENT=1
-DHAVE_GETPWUID=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE_GETUID=1 -DHAVE_GETWD=1
-DHAVE_KILL=1 -DHAVE_LGAMMA=1 -DHAVE_LINK=1 -DHAVE_LOCALTIME_R=1
-DHAVE_LSTAT=1 -DHAVE_MEMMOVE=1 -DHAVE_MKDIR=1 -DHAVE_MKFIFO=1
-DHAVE_MKSTEMP=1 -DHAVE_ON_EXIT=1 -DHAVE_PIPE=1 -DHAVE_POLL=1
-DHAVE_PUTENV=1 -DHAVE_RAISE=1 -DHAVE_READLINK=1 -DHAVE_REALPATH=1
-DHAVE_RENAME=1 -DHAVE_RINDEX=1 -DHAVE_RMDIR=1 -DHAVE_ROUND=1
-DHAVE_SELECT=1 -DHAVE_SETGRENT=1 -DHAVE_SETLOCALE=1
-DHAVE_SETPWENT=1 -DHAVE_SETVBUF=1 -DHAVE_SIGACTION=1
-DHAVE_SIGLONGJMP=1 -DHAVE_SIGPENDING=1 -DHAVE_SIGPROCMASK=1
-DHAVE_SIGSUSPEND=1 -DHAVE_SNPRINTF=1 -DHAVE_STAT=1 -DHAVE_STRCASECMP=1
-DHAVE_STRDUP=1 -DHAVE_STRERROR=1 -DHAVE_STRNCASECMP=1 -DHAVE_STRPTIME=1
-DHAVE_STRSIGNAL=1 -DHAVE_SYMLINK=1 -DHAVE_TEMPNAM=1 -DHAVE_TGAMMA=1
-DHAVE_UMASK=1 -DHAVE_UNAME=1 -DHAVE_UNLINK=1 -DHAVE_USLEEP=1
-DHAVE_UTIME=1 -DHAVE_VFPRINTF=1 -DHAVE_VSPRINTF=1 -DHAVE_VSNPRINTF=1
-DHAVE_WAITPID=1 -DHAVE_STRFTIME=1 -DHAVE_LIBDL=1 -DHAVE_DLOPEN=1
-DHAVE_DLSYM=1 -DHAVE_DLERROR=1 -DHAVE_DLCLOSE=1 -DHAVE_DLOPEN_API=1
-DENABLE_DYNAMIC_LINKING=1 -DHAVE_TIMEVAL=1 -DHAVE_FINITE=1
-DHAVE_ISNAN=1 -DHAVE_ISINF=1 -DHAVE_COPYSIGN=1 -DHAVE_DECL_SIGNBIT=1
-DHAVE_ACOSH=1 -DHAVE_ASINH=1 -DHAVE_ATANH=1 -DHAVE_ERF=1 -DHAVE_ERFC=1
-DHAVE_EXP2=1 -DHAVE_LOG2=1 -DHAVE_STRUCT_STAT_ST_BLKSIZE=1
-DHAVE_STRUCT_STAT_ST_BLOCKS=1 -DHAVE_STRUCT_STAT_ST_RDEV=1
-DHAVE_STRUCT_TM_TM_ZONE=1 -DHAVE_TM_ZONE=1 -DUSE_READLINE=1
-DEXCEPTION_IN_MATH=1 -DRETSIGTYPE=void -DHAVE_DECL_SYS_SIGLIST=1
-DHAVE_POSIX_SIGNALS=1 -DRETSIGTYPE_IS_VOID=1 -DHAVE_GETRUSAGE=1
-DHAVE_TIMES=1 -DYYTEXT_POINTER=1 -DGNUPLOT_BINARY="gnuplot"

User-preferences (please do not edit this section):
--------------------------------------------------

EDITOR = /usr/bin/vim
EXEC_PATH =
/usr/lib/octave/3.0.1/site/exec/i486-pc-linux-gnu:/usr/lib/octave/api-v32/site/exec/i486-pc-linux-gnu:/usr/lib/octave/site/exec/i486-pc-linux-gnu:/usr/lib/octave/3.0.1/exec/i486-pc-linux-gnu:/usr/bin:/opt/intel/idb/10.1.018/bin:/opt/intel/cc/10.1.018/bin:/home/william/bin:/home/william/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
IMAGE_PATH = .:/usr/share/octave/3.0.1/imagelib
PAGER = pager
PS1 = \s:\#>
PS2 = >
PS4 = +
beep_on_error = 0
completion_append_char =
crash_dumps_octave_core = 1
echo_executing_commands = 0
fixed_point_format = 0
gnuplot_binary = gnuplot
gnuplot_command_end =

gnuplot_command_plot = pl
gnuplot_command_replot = rep
gnuplot_command_splot = sp
gnuplot_command_title = t
gnuplot_command_using = u
gnuplot_command_with = w
history_file = /home/william/.octave_hist
history_size = 1024
ignore_function_time_stamp = system
info_file = /usr/share/info/octave3.0.info
info_program = info
makeinfo_program = makeinfo
max_recursion_depth = 256
output_max_field_width = 5
output_precision = 5
page_output_immediately = 0
page_screen_output = 1
print_answer_id_name = 1
print_empty_dimensions = 1
save_precision = 16
saving_history = 1
sighup_dumps_octave_core = 1
sigterm_dumps_octave_core = 1
silent_functions = 0
split_long_rows = 1
string_fill_char =
struct_levels_to_print = 2
suppress_verbose_help_message = 0
_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

can't compile development version

2009-12-02T02:25:42Z

Hello,

I tried to compile the last development version
and got this error

DLD-FUNCTIONS/urlwrite.cc:1427: error: expected ',' or '...' before '&'
token
DLD-FUNCTIONS/urlwrite.cc:1428: error: ISO C++ forbids declaration of
'curl_handle' with no type
DLD-FUNCTIONS/urlwrite.cc: In function 'string_vector
mput_directory(int)':

Thank You,

Bertrand Roessli

_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

root

2009-12-02T01:50:23Z

--------
Bug report for Octave 3.2.3 configured for i686-pc-linux-gnu

Description:
-----------

    I am trying to link the chemical package CANTERA to OCTAVE.
    Cantera supports a MATLAB interface. I compiled the interface
    successfully and tested it by running the cantera_demo script.
    All demos run well, only the demos which contain the 1D Class
    of Cantera fail with the following

    error: concatenation operator not implemented for `struct' by `class' operations
    error: evaluating argument list element number 1
    error: called from:
    error:   /usr/local/cantera/demos/matlab/flame.m at line 46, column 3
    error:   /usr/local/cantera/demos/matlab/flame1.m at line 74, column 4
    error:   /usr/local/cantera/demos/matlab/run_examples.m at line 30, column 1

    the function flame is called from flame1 where the simulation problem is set up
    (this "enveloping" code might not be necessary to resolve the error
     but one gets a good idea what's going on)

        % FLAME1 - A burner-stabilized flat flame
        %
        %    This script simulates a burner-stablized lean hydrogen-oxygen flame
        %    at low pressure.

        help flame1;
        %disp('press any key to begin the simulation');
        %pause;

        t0 = cputime; % record the starting time

        % parameter values
        p          =   0.05*oneatm;         % pressure
        tburner    =   373.0;               % burner temperature
        mdot       =   0.06;                % kg/m^2/s

        rxnmech    = 'h2o2.cti';           % reaction mechanism file
        comp       = 'H2:1.8, O2:1, AR:7'; % premixed gas composition

        initial_grid = [0.0 0.02 0.04 0.06 0.08 0.1 ...
                0.15 0.2 0.4 0.49 0.5]; % m

        tol_ss    = [1.0e-5 1.0e-13];       % [rtol atol] for steady-state
                                                         % problem
        tol_ts    = [1.0e-4 1.0e-9];          % [rtol atol] for time stepping

        loglevel = 1;                      % amount of diagnostic output (0
                                            % to 5)

        refine_grid = 1;                    % 1 to enable refinement, 0 to
                                           % disable
        max_jacobian_age = [5, 10];

        %%%%%%%%%%%%%%%% create the gas object %%%%%%%%%%%%%%%%%%%%%%%%
        %
        % This object will be used to evaluate all thermodynamic, kinetic    ,
        % and transport properties
        %
        gas = IdealGasMix(rxnmech);

        % set its state to that of the unburned gas at the burner
        set(gas,'T', tburner, 'P', p, 'X', comp);

        %%%%%%%%%%%%%%%% create the flow object %%%%%%%%%%%%%%%%%%%%%%%

        f = AxisymmetricFlow(gas,'flow');
        set(f, 'P', p, 'grid', initial_grid);
        set(f, 'tol', tol_ss, 'tol-time', tol_ts);

        %%%%%%%%%%%%%%% create the burner %%%%%%%%%%%%%%%%%%%%%%%%%%%%%
        %
        % The burner is an Inlet object. The temperature, mass flux,
        % and composition (relative molar) may be specified.
        %
        burner = Inlet('burner');
        set(burner, 'T', tburner, 'MassFlux', mdot, 'X', comp);

        %%%%%%%%%%%%%% create the outlet %%%%%%%%%%%%%%%%%%%%%%%%%%%%
        %
        % The type of flame is determined by the object that terminates
        % the domain. An Outlet object imposes zero gradient boundary
        % conditions for the temperature and mass fractions, and zero
        % radial velocity and radial pressure gradient.
        %
        s = Outlet('out');

        %%%%%%%%%%%%% create the flame object %%%%%%%%%%%%
        %
        % Once the component parts have been created, they can be assembled
        % to create the flame object.
        %
        fl = flame(gas, burner, f, s);

        ...


    Ok, this is the start of Function flame until the error:

        function f = flame(gas, left, flow, right)

        % FLAME - create a flame object.
        %
        %    gas     -- object representing the gas. This object will be used to
        %                compute all required thermodynamic, kinetic, and transport
        %                properties. The state of this object should be set
        %                to an estimate of the gas state emerging from the
        %                burner before calling StagnationFlame.
        %
        %    left    -- object representing the burner, which must be
        %                created using function Inlet.
        %
        %    flow    -- object representing the flow, created with
        %                function AxisymmetricFlow.
        %
        %    right   -- object representing the surface.function f = flame(gas, left, flow, right)

        % Check input parameters
        if nargin ~= 4
            error('wrong number of input arguments.');
        end

        if ~isIdealGas(gas)
            error('gas object must represent an ideal gas mixture.');
        end
        if ~isInlet(left)
            error('burner object of wrong type.');
        end
        if ~isFlow(flow)
            error('flow object of wrong type.');
        end

        flametype = 0;
            if isSurface(right)
        flametype = 1;
            elseif isInlet(right)
        flametype = 3;
        end

        % create the container object
        %the ERROR occurs HERE when the method @Stack/Stack.m is called
        f = Stack([left flow right]);

    Here is the definition of function s

        function s = Stack(domains)
        %
        % STACK - A one-dimensional 'stack' of domains.
        %
        %    A stack object is a container for one-dimensional domains,
        %    which are instances of class Domain1D. The domains are of two
        %    types - extended domains, and connector domains.
        %

        disp("DEBUG POS 1 - Stack "); disp (domains); pause;

The error is in the function headline before the disp(" DEBUG ..") I inserted. Obviously it is not possible to merge the 3 objects into 1 implicitly. The author of the code, Dr. Goodwin, did a thorough job to structure it object orientated. Probably the scripts above will not run without the definition if the basic classes, but the code is well documented and it should be possible to get the idea. I posted what I did to link Cantera to Octave on the Google Cantera Usergroup, in case it is necessary. I don't know if this is significant, I had compiled Octave myself and failed to link in some libraries (SparseMatrixes, FFTW, GraphicMagic, qrupdate, qhull).

Expected Outcome:
------------------------
Matlab compatibility regarding class objects, no error.

Repeat-By:
---------

    The original error can be repeated with a call of the flame1.m example of Cantera.
    I tried to produce also a shorter example without the Cantera package,
    but failed. I am new to both Cantera and Octave.

Fix:
---

    -

Configuration (please do not edit this section):
-----------------------------------------------

uname output:     Linux puppypc 2.6.30.5 #1 SMP Tue Sep 1 15:48:26 GMT-8 2009 i686 GNU/Linux
configure opts:
Fortran compiler: gfortran
FFLAGS:           -O -mieee-fp
FLIBS:            -L/usr/lib/gcc/i486-t2-linux-gnu/4.2.2 -L/usr/lib/gcc/i486-t2-linux-gnu/4.2.2/../../../../i486-t2-linux-gnu/lib -L/usr/lib/gcc/i486-t2-linux-gnu/4.2.2/../../.. -lz -lgfortranbegin -lgfortran -lm
CPPFLAGS:
INCFLAGS:         -I. -I. -I./liboctave -I./src -I./libcruft/misc
C compiler:       gcc, version 4.2.2
CFLAGS:           -g -O2
CPICFLAG:         -fPIC
C++ compiler:     g++, version 4.2.2
CXXFLAGS:         -g -O2
CXXPICFLAG:       -fPIC
LD_CXX:           g++
LDFLAGS:
LIBFLAGS:         -L.
RLD_FLAG:         -Wl,-rpath -Wl,/usr/local/lib/octave-3.2.3
BLAS_LIBS:
FFTW_LIBS:
LIBS:             -lreadline -lncurses -ldl -lz -lm
LEXLIB:
LIBGLOB:
SED:              /bin/sed
DEFS:

-DPACKAGE_NAME="" -DPACKAGE_TARNAME="" -DPACKAGE_VERSION="" -DPACKAGE_STRING="" -DPACKAGE_BUGREPORT="" -DOCTAVE_SOURCE=1 -D_GNU_SOURCE=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -D__EXTENSIONS__=1 -D_POSIX_PTHREAD_SEMANTICS=1 -D_TANDEM_SOURCE=1 -DSEPCHAR=':' -DSEPCHAR_STR=":" -D__NO_MATH_INLINES=1 -DCXX_NEW_FRIEND_TEMPLATE_DECL=1 -DCXX_ISO_COMPLIANT_LIBRARY=1 -DHAVE_X_WINDOWS=1 -DHAVE_LIBM=1 -DHAVE_PCRE_COMPILE=1 -DHAVE_PCRE=1 -DHAVE_REGEXEC=1 -DHAVE_REGEX=1 -DHAVE_ZLIB_H=1 -DHAVE_ZLIB=1 -DHAVE_GLPK_H=1 -DHAVE_GLPK=1 -DHAVE_CURL_CURL_H=1 -DHAVE_CURL=1 -DHAVE_IEEE754_DATA_FORMAT=1 -DF77_FUNC(name,NAME)=name ## _ -DF77_FUNC_(name,NAME)=name ## _ -DHAVE_GETHOSTNAME=1 -DHAVE_GETPWNAM=1 -DHAVE_DEV_T=1 -DHAVE_INO_T=1 -DHAVE_NLINK_T=1 -DHAVE_NLINK_T=1 -DHAVE_LONG_LONG_INT=1 -DHAVE_UNSIGNED_LONG_LONG_INT=1 -DHAVE_SIGSET_T=1 -DHAVE_SIG_ATOMIC_T=1 -DSIZEOF_SHORT=2 -DSIZEOF_INT=4 -DSIZEOF_LONG=4 -DSIZEOF_LONG_LONG=8 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_PLACEMENT_DELETE=1 -DHAVE_DYNAMIC_AUTO_ARRAYS=1 -DHAVE_FAST_INT_OPS=1 -DSIZEOF_LONG_DOUBLE=12 -DSTDC_HEADERS=1 -DHAVE_DIRENT_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_SYS_WAIT_H=1 -DHAVE_ASSERT_H=1 -DHAVE_CURSES_H=1 -DHAVE_DLFCN_H=1 -DHAVE_FCNTL_H=1 -DHAVE_FLOAT_H=1 -DHAVE_GRP_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_LIMITS_H=1 -DHAVE_LOCALE_H=1 -DHAVE_MEMORY_H=1 -DHAVE_NCURSES_H=1 -DHAVE_POLL_H=1 -DHAVE_PTHREAD_H=1 -DHAVE_PWD_H=1 -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_POLL_H=1 -DHAVE_SYS_RESOURCE_H=1 -DHAVE_SYS_SELECT_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMES_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_UTSNAME_H=1 -DHAVE_TERMCAP_H=1 -DHAVE_UNISTD_H=1 -DHAVE_UTIME_H=1 -DHAVE_SSTREAM=1 -DHAVE_TERMIOS_H=1 -DHAVE_TERMIO_H=1 -DHAVE_SGTTY_H=1 -DHAVE_GLOB_H=1 -DHAVE_FNMATCH_H=1 -DHAVE_FNMATCH=1 -DHAVE_GLOB=1 -DHAVE_ATEXIT=1 -DHAVE_BASENAME=1 -DHAVE_BCOPY=1 -DHAVE_BZERO=1 -DHAVE_CANONICALIZE_FILE_NAME=1 -DHAVE_CHMOD=1 -DHAVE_DUP2=1 -DHAVE_ENDGRENT=1 -DHAVE_ENDPWENT=1 -DHAVE_EXECVP=1 -DHAVE_EXPM1=1 -DHAVE_EXPM1F=1 -DHAVE_FCNTL=1 -DHAVE_FORK=1 -DHAVE_FSTAT=1 -DHAVE_GETCWD=1 -DHAVE_GETEGID=1 -DHAVE_GETEUID=1 -DHAVE_GETGID=1 -DHAVE_GETGRENT=1 -DHAVE_GETGRGID=1 -DHAVE_GETGRNAM=1 -DHAVE_GETPGRP=1 -DHAVE_GETPID=1 -DHAVE_GETPPID=1 -DHAVE_GETPWENT=1 -DHAVE_GETPWUID=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE_GETUID=1 -DHAVE_GETWD=1 -DHAVE_KILL=1 -DHAVE_LGAMMA=1 -DHAVE_LGAMMAF=1 -DHAVE_LGAMMA_R=1 -DHAVE_LGAMMAF_R=1 -DHAVE_LINK=1 -DHAVE_LOCALTIME_R=1 -DHAVE_LOG1P=1 -DHAVE_LOG1PF=1 -DHAVE_LSTAT=1 -DHAVE_MEMMOVE=1 -DHAVE_MKDIR=1 -DHAVE_MKFIFO=1 -DHAVE_MKSTEMP=1 -DHAVE_ON_EXIT=1 -DHAVE_PIPE=1 -DHAVE_POLL=1 -DHAVE_PUTENV=1 -DHAVE_RAISE=1 -DHAVE_READLINK=1 -DHAVE_REALPATH=1 -DHAVE_RENAME=1 -DHAVE_RINDEX=1 -DHAVE_RMDIR=1 -DHAVE_ROUNDL=1 -DHAVE_SELECT=1 -DHAVE_SETGRENT=1 -DHAVE_SETLOCALE=1 -DHAVE_SETPWENT=1 -DHAVE_SETVBUF=1 -DHAVE_SIGACTION=1 -DHAVE_SIGLONGJMP=1 -DHAVE_SIGPENDING=1 -DHAVE_SIGPROCMASK=1 -DHAVE_SIGSUSPEND=1 -DHAVE_SNPRINTF=1 -DHAVE_STAT=1 -DHAVE_STRCASECMP=1 -DHAVE_STRDUP=1 -DHAVE_STRERROR=1 -DHAVE_STRNCASECMP=1 -DHAVE_STRPTIME=1 -DHAVE_STRSIGNAL=1 -DHAVE_SYMLINK=1 -DHAVE_TEMPNAM=1 -DHAVE_TGAMMAF=1 -DHAVE_TRUNC=1 -DHAVE_UMASK=1 -DHAVE_UNAME=1 -DHAVE_UNLINK=1 -DHAVE_USLEEP=1 -DHAVE_UTIME=1 -DHAVE_VFPRINTF=1 -DHAVE_VSPRINTF=1 -DHAVE_VSNPRINTF=1 -DHAVE_WAITPID=1 -DHAVE_DECL_EXP2=1 -DHAVE_DECL_ROUND=1 -DHAVE_DECL_TGAMMA=1 -DHAVE_EXP2=1 -DHAVE_ROUND=1 -DHAVE_TGAMMA=1 -DHAVE_STRFTIME=1 -DHAVE_C99_VSNPRINTF=1 -DHAVE_LIBDL=1 -DHAVE_DLOPEN=1 -DHAVE_DLSYM=1 -DHAVE_DLERROR=1 -DHAVE_DLCLOSE=1 -DHAVE_DLOPEN_API=1 -DENABLE_DYNAMIC_LINKING=1 -DHAVE_TIMEVAL=1 -DHAVE_CMATH_ISNAN=1 -DHAVE_CMATH_ISNANF=1 -DHAVE_CMATH_ISINF=1 -DHAVE_CMATH_ISINFF=1 -DHAVE_CMATH_ISFINITE=1 -DHAVE_CMATH_ISFINITEF=1 -DHAVE_FINITE=1 -DHAVE_ISNAN=1 -DHAVE_ISINF=1 -DHAVE_COPYSIGN=1 -DHAVE_DECL_SIGNBIT=1 -DHAVE_ACOSH=1 -DHAVE_ACOSHF=1 -DHAVE_ASINH=1 -DHAVE_ASINHF=1 -DHAVE_ATANH=1 -DHAVE_ATANHF=1 -DHAVE_ERF=1 -DHAVE_ERFF=1 -DHAVE_ERFC=1 -DHAVE_ERFCF=1 -DHAVE_EXP2F=1 -DHAVE_LOG2=1 -DHAVE_LOG2F=1 -DHAVE_HYPOTF=1 -DHAVE_STRUCT_STAT_ST_BLKSIZE=1 -DHAVE_STRUCT_STAT_ST_BLOCKS=1 -DHAVE_STRUCT_STAT_ST_RDEV=1 -DHAVE_STRUCT_TM_TM_ZONE=1 -DHAVE_TM_ZONE=1 -DUSE_READLINE=1 -DEXCEPTION_IN_MATH=1 -DRETSIGTYPE=void -DHAVE_DECL_SYS_SIGLIST=1 -DHAVE_POSIX_SIGNALS=1 -DRETSIGTYPE_IS_VOID=1 -DHAVE_GETRUSAGE=1 -DHAVE_TIMES=1 -DYYTEXT_POINTER=1

User-preferences (please do not edit this section):
--------------------------------------------------

EDITOR = mp
EXEC_PATH = /usr/local/libexec/octave/3.2.3/site/exec/i686-pc-linux-gnu:/usr/local/libexec/octave/api-v37/site/exec/i686-pc-linux-gnu:/usr/local/libexec/octave/site/exec/i686-pc-linux-gnu:/usr/local/libexec/octave/3.2.3/exec/i686-pc-linux-gnu:/usr/local/bin:/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/X11R7/bin:/root/my-applications/bin:/opt/qt4/bin:/opt/mozilla.org/bin:/opt/samba/bin
IMAGE_PATH = .:/usr/local/share/octave/3.2.3/imagelib
PAGER = less
PS1 = >>
PS2 =
PS4 = +
beep_on_error = 1
completion_append_char =
crash_dumps_octave_core = 0
echo_executing_commands = 0
fixed_point_format = 1
gnuplot_binary = gnuplot
# gnuplot_command_end = <no value or error in displaying it>
# gnuplot_command_plot = <no value or error in displaying it>
# gnuplot_command_replot = <no value or error in displaying it>
# gnuplot_command_splot = <no value or error in displaying it>
# gnuplot_command_title = <no value or error in displaying it>
# gnuplot_command_using = <no value or error in displaying it>
# gnuplot_command_with = <no value or error in displaying it>
history_file = /root/.octave_hist
history_size = 1024
ignore_function_time_stamp = system
info_file = /usr/local/share/info/octave.info
info_program = info
makeinfo_program = makeinfo
max_recursion_depth = 256
output_max_field_width = 5
output_precision = 5
page_output_immediately = 0
page_screen_output = 0
# print_answer_id_name = <no value or error in displaying it>
print_empty_dimensions = 0
save_precision = 16
saving_history = 1
sighup_dumps_octave_core = 1
sigterm_dumps_octave_core = 1
silent_functions = 0
split_long_rows = 1
string_fill_char =
struct_levels_to_print = 2
suppress_verbose_help_message = 0

Sorry I was not able to send this from inside the bug_report script,
regards
emil

--

Emil Widmann
Kürsinger Hütte
Obersulzbachtal
5741 Neukirchen am Großvenediger
+43 6565 6450
emil.widmann@...
info@...

_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Re: sscanf returns zero status

2009-12-01T02:01:51Z

Hi,

Here is the supporting information regarding the problem associated with sscanf.

Octave version 3.0.4

my string variable is "exon":[[[1842,1945]]]

string(11:min(22,11+20))
>> 1842,1945]]]

So I expect delta of value 5 from below statement.

[num, one, err, delta] = sscanf(string(11:min(22,11+20)), '%f', 1);

Hope this will help.

Regards,
Vipin

_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

num2str deleting leading spaces, - is it a Bug or Feature?

2009-12-01T00:31:00Z

Bug report for Octave 3.2.2 configured for i686-pc-mingw32

Description:
-----------

I want leading speces in an Output-String for a numerical value,
but num2str(x, "% 10.3") deletes the leading spaces

Repeat-By:
---------

x = 10;
["xxx", num2str(x, "% 10.3f"), "###"]
---> ans = xxx10.000###

Fix:
---

x = 10;
["xxx", sprintf("% 10.3f", x), "###"]

Configuration (please do not edit this section):
-----------------------------------------------

uname output: Windows
configure opts:
Fortran compiler: mingw32-gfortran-4.3.0-dw2
FFLAGS: -O -mieee-fp
FLIBS: -lgfortran
CPPFLAGS: -march=i686 -mtune=generic -O2
INCFLAGS: -I. -I/octmgw32/octave/octave-3.2.2 -I.
-I./liboctave -I./src -I./libcruft/misc
-I/octmgw32/octave/octave-3.2.2
-I/octmgw32/octave/octave-3.2.2/liboctave
-I/octmgw32/octave/octave-3.2.2/src
-I/octmgw32/octave/octave-3.2.2/libcruft/misc
C compiler: mingw32-gcc-4.3.0-dw2, version4.3.0-dw2 (GCC TDM-2
for MinGW)
CFLAGS: -Wall
CPICFLAG:
C++ compiler: mingw32-g++-4.3.0-dw2, version4.3.0-dw2
CXXFLAGS: -D_DLL -Wall
CXXPICFLAG:
LD_CXX: mingw32-g++-4.3.0-dw2
LDFLAGS: -shared-libgcc -Wl,--exclude-libs=-lstdc++_s
-Wl,--allow-multiple-definition
LIBFLAGS: -L.
RLD_FLAG:
BLAS_LIBS: -llapack -lblas
FFTW_LIBS: -lfftw3 -lfftw3f
LIBS: -lreadline -lncurses -liberty -lblas -lhdf5 -lz -lm
-lgdi32 -lws2_32 -luser32 -lkernel32
LEXLIB:
LIBGLOB: -lglob
SED: /usr/bin/sed
DEFS:
-DPACKAGE_NAME="" -DPACKAGE_TARNAME="" -DPACKAGE_VERSION=""
-DPACKAGE_STRING="" -DPACKAGE_BUGREPORT="" -DOCTAVE_SOURCE=1
-D_GNU_SOURCE=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1
-DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -D__EXTENSIONS__=1
-D_POSIX_PTHREAD_SEMANTICS=1 -D_TANDEM_SOURCE=1 -DSEPCHAR=';'
-DSEPCHAR_STR=";" -D__NO_MATH_INLINES=1
-DCXX_NEW_FRIEND_TEMPLATE_DECL=1 -DCXX_ISO_COMPLIANT_LIBRARY=1
-DHAVE_X_WINDOWS=1 -DHAVE_LIBM=1 -DHAVE_QHULL=1 -DHAVE_PCRE_COMPILE=1
-DHAVE_PCRE=1 -DHAVE_REGEX=1 -DHAVE_ZLIB_H=1 -DHAVE_ZLIB=1
-DHAVE_HDF5_H=1 -DHAVE_HDF5=1 -DHAVE_H5GGET_NUM_OBJS=1 -DHAVE_FFTW3=1
-DHAVE_GLPK_GLPK_H=1 -DHAVE_GLPK=1 -DHAVE_CURL_CURL_H=1 -DHAVE_CURL=1
-DHAVE_MAGICK=1 -DHAVE_WINDOWS_H=1 -DHAVE_GL_GL_H=1 -DHAVE_GL_GLU_H=1
-DHAVE_OPENGL=1 -DHAVE_FTGL_FTGL_H=1 -DHAVE_FTGL=1 -DHAVE_FLTK=1
-DHAVE_IEEE754_DATA_FORMAT=1 -DF77_FUNC(name,NAME)=name ## _
-DF77_FUNC_(name,NAME)=name ## _ -DHAVE_BLAS=1 -DHAVE_QRUPDATE=1
-DHAVE_SUITESPARSE_AMD_H=1 -DHAVE_AMD=1 -DHAVE_SUITESPARSE_UMFPACK_H=1
-DHAVE_UMFPACK=1 -DUMFPACK_SEPARATE_SPLIT=1
-DHAVE_SUITESPARSE_COLAMD_H=1 -DHAVE_COLAMD=1
-DHAVE_SUITESPARSE_CCOLAMD_H=1 -DHAVE_CCOLAMD=1
-DHAVE_SUITESPARSE_CHOLMOD_H=1 -DHAVE_CHOLMOD=1
-DHAVE_SUITESPARSE_CS_H=1 -DHAVE_CXSPARSE=1 -DHAVE_ARPACK=1
-Duid_t=int -Dgid_t=int -DHAVE_DEV_T=1 -DHAVE_INO_T=1
-DHAVE_LONG_LONG_INT=1 -DHAVE_UNSIGNED_LONG_LONG_INT=1
-DHAVE_SIGSET_T=1 -DHAVE_SIG_ATOMIC_T=1 -DSIZEOF_SHORT=2
-DSIZEOF_INT=4 -DSIZEOF_LONG=4 -DSIZEOF_LONG_LONG=8 -DHAVE_ALLOCA=1
-DHAVE_PLACEMENT_DELETE=1 -DHAVE_DYNAMIC_AUTO_ARRAYS=1
-DHAVE_FAST_INT_OPS=1 -DSIZEOF_LONG_DOUBLE=12 -DSTDC_HEADERS=1
-DHAVE_DIRENT_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_ASSERT_H=1
-DHAVE_CURSES_H=1 -DHAVE_DIRECT_H=1 -DHAVE_FCNTL_H=1 -DHAVE_FLOAT_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_LIMITS_H=1 -DHAVE_LOCALE_H=1
-DHAVE_MEMORY_H=1 -DHAVE_NCURSES_H=1 -DHAVE_PTHREAD_H=1
-DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TIME_H=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_UTIME_H=1 -DHAVE_TERMCAP_H=1
-DHAVE_UNISTD_H=1 -DHAVE_UTIME_H=1 -DHAVE_SSTREAM=1 -DHAVE_GLOB_H=1
-DHAVE_FNMATCH_H=1 -DHAVE_CONIO_H=1 -DHAVE_ATEXIT=1 -DHAVE_BASENAME=1
-DHAVE_CHMOD=1 -DHAVE_DUP2=1 -DHAVE_EXECVP=1 -DHAVE_EXPM1=1
-DHAVE_EXPM1F=1 -DHAVE_FSTAT=1 -DHAVE_GETCWD=1 -DHAVE_GETPID=1
-DHAVE_GETTIMEOFDAY=1 -DHAVE__KBHIT=1 -DHAVE_LGAMMA=1 -DHAVE_LGAMMAF=1
-DHAVE_LOG1P=1 -DHAVE_LOG1PF=1 -DHAVE_MEMMOVE=1 -DHAVE_MKDIR=1
-DHAVE_PUTENV=1 -DHAVE_RAISE=1 -DHAVE_RENAME=1 -DHAVE_RMDIR=1
-DHAVE_ROUNDL=1 -DHAVE_SETLOCALE=1 -DHAVE_SETVBUF=1 -DHAVE_SNPRINTF=1
-DHAVE_STAT=1 -DHAVE_STRCASECMP=1 -DHAVE_STRDUP=1 -DHAVE_STRERROR=1
-DHAVE_STRICMP=1 -DHAVE_STRNCASECMP=1 -DHAVE_STRNICMP=1
-DHAVE_TEMPNAM=1 -DHAVE_TGAMMAF=1 -DHAVE_TRUNC=1 -DHAVE_UMASK=1
-DHAVE_UNLINK=1 -DHAVE_USLEEP=1 -DHAVE_UTIME=1 -DHAVE_VFPRINTF=1
-DHAVE_VSPRINTF=1 -DHAVE_VSNPRINTF=1 -DHAVE__CHMOD=1
-DHAVE__SNPRINTF=1 -DHAVE_DECL_EXP2=1 -DHAVE_DECL_ROUND=1
-DHAVE_DECL_TGAMMA=1 -DHAVE_EXP2=1 -DHAVE_ROUND=1 -DHAVE_TGAMMA=1
-DHAVE_MKSTEMPS=1 -DHAVE_C99_VSNPRINTF=1
-DOCTAVE_HAVE_BROKEN_STRPTIME=1 -D_WIN32_WINNT=0x0403
-DHAVE_LOADLIBRARY_API=1 -DENABLE_DYNAMIC_LINKING=1 -DHAVE_TIMEVAL=1
-DHAVE_CMATH_ISNAN=1 -DHAVE_CMATH_ISNANF=1 -DHAVE_CMATH_ISINF=1
-DHAVE_CMATH_ISINFF=1 -DHAVE_CMATH_ISFINITE=1 -DHAVE_CMATH_ISFINITEF=1
-DHAVE_FINITE=1 -DHAVE_ISNAN=1 -DHAVE_COPYSIGN=1 -DHAVE_SIGNBIT=1
-DHAVE__FINITE=1 -DHAVE__ISNAN=1 -DHAVE__COPYSIGN=1
-DHAVE_DECL_SIGNBIT=1 -DHAVE_ACOSH=1 -DHAVE_ACOSHF=1 -DHAVE_ASINH=1
-DHAVE_ASINHF=1 -DHAVE_ATANH=1 -DHAVE_ATANHF=1 -DHAVE_ERF=1
-DHAVE_ERFF=1 -DHAVE_ERFC=1 -DHAVE_ERFCF=1 -DHAVE_EXP2F=1
-DHAVE_LOG2=1 -DHAVE_LOG2F=1 -DHAVE_HYPOTF=1
-DHAVE_STRUCT_STAT_ST_RDEV=1 -DHAVE_DECL_TZNAME=1 -DHAVE_TZNAME=1
-DMKDIR_TAKES_ONE_ARG=1 -DUSE_READLINE=1 -DRETSIGTYPE=void
-DHAVE_DECL_SYS_SIGLIST=0 -DMUST_REINSTALL_SIGHANDLERS=1
-DRETSIGTYPE_IS_VOID=1

User-preferences (please do not edit this section):

EDITOR = C:\Programme\pspad\PSPad.exe
EXEC_PATH =
C:\Programme\Octave\3.2.2_gcc-4.3.0\MINGW32\bin;C:\Programme\Octave\3.2.2_gcc-4.3.0\MSYS\bin;C:\Programme\Octave\3.2.2_gcc-4.3.0\libexec\octave\3.2.2\site\exec\i686-pc-mingw32;C:\Programme\Octave\3.2.2_gcc-4.3.0\libexec\octave\api-v37\site\exec\i686-pc-mingw32;C:\Programme\Octave\3.2.2_gcc-4.3.0\libexec\octave\site\exec\i686-pc-mingw32;C:\Programme\Octave\3.2.2_gcc-4.3.0\libexec\octave\3.2.2\exec\i686-pc-mingw32;C:\Programme\Octave\3.2.2_gcc-4.3.0\bin;C:\Programme\MiKTeX
2.7\miktex\bin;C:\Programme\Microsoft Visual
Studio\Common\Tools;C:\Programme\Microsoft Visual
Studio\Common\Msdev98\BIN;C:\Programme\Microsoft Visual
Studio\DF98\BIN;C:\Programme\Microsoft Visual
Studio\VC98\BIN;C:\PROGRA~1\GEMEIN~1\ASPENT~1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Programme\Gemeinsame
Dateien\AspenTech Shared\;C:\Programme\Rainbow Technologies\SentinelLM
7.2.0.1
Server\English\;C:\Programme\gnuplot\bin\;C:\VXIpnp\WinNT\Bin;C:\Programme\XEmacs\XEmacs-21.4.21\i586-pc-win32;C:\Programme\Ghostgum\gs\gs8.63\bin
IMAGE_PATH =
.;C:\Programme\Octave\3.2.2_gcc-4.3.0\share\octave\3.2.2\imagelib
PAGER = C:\Programme\Octave\3.2.2_gcc-4.3.0\bin\less.exe
PS1 = \s:\#:\w
>
PS2 = >
PS4 = +
beep_on_error = 0
completion_append_char =
crash_dumps_octave_core = 1
echo_executing_commands = 0
fixed_point_format = 0
gnuplot_binary = C:\Programme\Octave\3.2.2_gcc-4.3.0\bin\gnuplot.exe
# gnuplot_command_end = <no value or error in displaying it>
# gnuplot_command_plot = <no value or error in displaying it>
# gnuplot_command_replot = <no value or error in displaying it>
# gnuplot_command_splot = <no value or error in displaying it>
# gnuplot_command_title = <no value or error in displaying it>
# gnuplot_command_using = <no value or error in displaying it>
# gnuplot_command_with = <no value or error in displaying it>
history_file = C:\Dokumente und Einstellungen\spofahl\.octave_hist
history_size = 1024
ignore_function_time_stamp = system
info_file = C:\Programme\Octave\3.2.2_gcc-4.3.0\share\info\octave.info
info_program = info
makeinfo_program = makeinfo
max_recursion_depth = 256
output_max_field_width = 5
output_precision = 5
page_output_immediately = 0
page_screen_output = 1
# print_answer_id_name = <no value or error in displaying it>
print_empty_dimensions = 1
save_precision = 16
saving_history = 1
sighup_dumps_octave_core = 1
sigterm_dumps_octave_core = 1
silent_functions = 0
split_long_rows = 1
string_fill_char =
struct_levels_to_print = 2
suppress_verbose_help_message = 0

_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Re: sscanf returns zero status

2009-11-30T23:23:36Z

John W. Eaton wrote:

> On 30-Nov-2009, vipin.ts@... wrote:
>
> | I am using a matlab script and trying to reproduce it in octave. But I am getting a zero value while handling with sscanf function.
> | Here is the code
> |
> | [num, one, err, delta] = sscanf(string(pos:min(len,pos+20)), '%f', 1);
> |
> | In this statement matlab gives a delta variable with numeric value, but in octave always I am getting zero value.
> |
> | Many thanks for helping to solve the problem.
>
> This might be a bug, but you haven't given enough information for
> anyone to debug the problem.
>
> What version of Octave are you using?
>
> What is the value of
>
> string(pos:min(len,pos+20))
>
> when sscanf is called?
>
> jwe
> _______________________________________________
> Bug-octave mailing list
> Bug-octave@...
> https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave
>

The 3.2 series' sscanf always return a 0 in the fourth outarg.

I fixed the string seeking in this changeset:
http://hg.savannah.gnu.org/hgweb/octave/rev/3ccd3a03944c

This changeset couldn't be transplanted to 3.2 since it breaks the ABI.

Best regards,
David
_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Re: base class assignment problem (was: Re: very strange bug)

2009-11-30T22:28:42Z

On Mon, Nov 30, 2009 at 11:34 AM, Lukas Reichlin <lukas.reichlin@...> wrote:

On 02.11.2009, at 17:43, John W. Eaton wrote:

> On 2-Nov-2009, Jaroslav Hajek wrote:
>
> | On Fri, Oct 30, 2009 at 6:38 PM, John W. Eaton <jwe@...> wrote:
> | > On 30-Oct-2009, Lukas Reichlin wrote:
> | >
> | > | control-oo is here:
> | > | http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/control-oo/
> | > |
> | > | Download the package with:
> | > | http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/control-oo.tar.gz?view=tar
> | > |
> | > | Make sure that the "legacy" control package is not in your Octave
> | > | path, because some functions have identical names (Matlab
> | > | compatibility).
> | > |
> | > | I reduced the example as good as possible. If it is still too
> | > | complicated to understand, you will have to wait until Robert posts
> | > | his example next weekend.
> | >
> | > I'm attaching a minimal example. Unpack the oo-bug.tar.gz file, cd to
> | > the oo-bug directory and run the bug.m script.
> | >
> | > The problem seems to be that the base class objects are not properly
> | > copied when their fields are modified inside methods. I don't have a
> | > solution so it would be great if someone else would like to take a
> | > shot a fixing this problem.
> | >
> | > jwe
> | >
> | >
> |
> | How about this?
> | http://hg.savannah.gnu.org/hgweb/octave/rev/0df32e0b2074
>
> This change fixes the problem for me.
>
> Thanks,
>
> jwe

Thanks for fixing the bug. However, I couldn't test whether the change fixes the problem for me because I'm (still) unable to compile Octave from source (I'm using Octave.app on MacOSX). It would be great if the fix would be included in the upcoming release 3.2.4, since the control-oo package depends on it.

Regards,
Lukas

This fix would need to be adapted for 3.2.x because it breaks binary compatibility (new virtual method). As it stands, it doesn't conform to our stable release policy.

hth

--
RNDr. Jaroslav Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz

_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Re: Fixing HDF-1.8 API for octave-3.2.x

2009-11-30T15:51:19Z

John W. Eaton wrote:

> On 28-Oct-2009, dbateman wrote:
>
> | Kacper Kowalik wrote:
> | >
> | > Attached patches do the following:
> | >
> | > 1) octave-3.2.2-drop-ancient-hdf5.diff - removes now obsolete code
> | > under 'HAVE_H5GGET_NUM_OBJS'
> | > and 'have_h5giterate_bug' since hdf5>=1.6 includes H5GGET_NUM_OBJS and
> | > is free of the h5giterate_bug.
> | > As results it drops compatibility with hdf5-1.2 and hdf5-1.4
> | >
> | > 2) octave-3.2.2-simplify_and_prep_for_hdf5-18.diff - small changes in
> | > configure.in and config.h.in,
> | > now if HDF5>=1.8 is present on the system, new flag (HAVE_HDF5_18) is
> | > defined.
> | > Unless HDF5-1.8 library was compiled with --with-default-api-version=v16
> | >
> | > 3) octave-3.2.2-add-hdf5_18.diff - brings HDF5-1.8 API octave while
> | > retaining compatibility with HDF5-1.6
> | >
> | > Best regards,
> | > Kacper Kowalik
> | >
> | >
> |
> | Were these patches ever applied? It would be nice to have them in the
> | development tree to allow the use of HDF 1.8 natively..
>
> No, I don't think they were applied. Do they look OK to you? If so,
> I have no objection to applying them, though it would be slightly
> easier to do that if they were hg changesets relative to the current
> sources instead of simple context diffs relative to Octave 3.2.2.
>
>

Ok, I've added these patches, including changelogs and keeping Kacper as
the author in the changelog, the commit and added him to the
contributors file.

Under the v1.6 and v1.8 builds I tested that appeared to work as advertised.

Regards
David
_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Re: Ginput doesn't work in 3.2.3

2009-11-30T15:18:01Z

> >>> clf
> >>> imshow(rand(100))
> >>> [x,y,k]=ginput(1)
> > fputs (ostream, "unset multiplot;\n\n");
> (1) Add a "set multiplot" in __go_draw_figure__ after drawing all axes

Yes, this is (almost) the solution.

Please notice that the current behaviour (i.e. incomplete "set multiplot" /
"unset multiplot") is actually a bug disabling hotkey and mousing
funcionality for 2d plots.

Please fix it with the enclosed patch.

(Note: "unset multiplot" makes no harm if there is no previous "set
multiplot".)

---
Petr Mikulik
[unset_multiplot.patch]

__go_draw_figure__.m: Fix missing "unset multiplot", required for plots consisting of several subfigures, for example. --- __go_draw_figure__-orig.m 2009-09-23 10:36:47.000000000 +0200 +++ __go_draw_figure__.m 2009-11-30 14:09:04.000000000 +0100 @@ -95,6 +95,7 @@ error ("__go_draw_figure__: unknown object class, %s", type); endswitch endfor + fputs (plot_stream, "\nunset multiplot;\n"); else fputs (plot_stream, "\nreset; clear;\n"); fflush (plot_stream);

_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

curl/urlwrite problem

2009-11-30T12:12:38Z

On 30-Nov-2009, Kai Habel wrote:

| I think Jaroslav's recent changeset [1] causes an error if curl 7.19.0
| is present (e.g. OpenSuse 11.1).
|
| I get:
|
| /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.
| -I.. -I../libcruft/misc -I../liboctave -I../liboctave -I. -I. -g
| -O2 -DHAVE_CONFIG_H -I/usr/include/freetype2 -Wall -W -Wshadow
| -Wold-style-cast -Wformat -g -O2 -pthread -g -O2 -MT
| DLD-FUNCTIONS/DLD_FUNCTIONS_urlwrite_la-urlwrite.lo -MD -MP -MF
| DLD-FUNCTIONS/.deps/DLD_FUNCTIONS_urlwrite_la-urlwrite.Tpo -c -o
| DLD-FUNCTIONS/DLD_FUNCTIONS_urlwrite_la-urlwrite.lo `test -f
| 'DLD-FUNCTIONS/urlwrite.cc' || echo './'`DLD-FUNCTIONS/urlwrite.cc
| libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I../libcruft/misc
| -I../liboctave -I../liboctave -I. -I. -g -O2 -DHAVE_CONFIG_H
| -I/usr/include/freetype2 -Wall -W -Wshadow -Wold-style-cast -Wformat -g
| -O2 -pthread -g -O2 -MT
| DLD-FUNCTIONS/DLD_FUNCTIONS_urlwrite_la-urlwrite.lo -MD -MP -MF
| DLD-FUNCTIONS/.deps/DLD_FUNCTIONS_urlwrite_la-urlwrite.Tpo -c
| DLD-FUNCTIONS/urlwrite.cc -fPIC -DPIC -o
| DLD-FUNCTIONS/.libs/DLD_FUNCTIONS_urlwrite_la-urlwrite.o
| making gendoc.cc
| DLD-FUNCTIONS/urlwrite.cc: In member function ‘void
| curl_handle::init(const std::string&, const std::string&, std::istream&,
| std::ostream&)’:
| DLD-FUNCTIONS/urlwrite.cc:566: error: ‘CURLOPT_USERNAME’ was not
| declared in this scope
| DLD-FUNCTIONS/urlwrite.cc:568: error: ‘CURLOPT_PASSWORD’ was not
| declared in this scope
| make[3]: *** [DLD-FUNCTIONS/DLD_FUNCTIONS_urlwrite_la-urlwrite.lo] Fehler 1
| make[3]: *** Warte auf noch nicht beendete Prozesse...
| make[3]: Leaving directory `/home/kai/hg-octave/octave/src'
| make[2]: *** [all] Fehler 2
| make[2]: Leaving directory `/home/kai/hg-octave/octave/src'
| make[1]: *** [all-recursive] Fehler 1
| make[1]: Leaving directory `/home/kai/hg-octave/octave'
| make: *** [all] Fehler 2
|
|
| I think in src/DLD-Functions/urlwrite.cc:
|
| setopt (CURLOPT_NOBODY, 1);
| 561
| 562 // Set the username and password
| 563 #if (LIBCURL_VERSION_NUM >= 0x071300)
| 564 // This is possible since cURL 7.19.1
| 565 if (user.length () != 0)
| 566 setopt (CURLOPT_USERNAME, user.c_str());
| 567 if (passwd.length () != 0)
|
| line 563
|
| should be changed in:
|
| #if (LIBCURL_VERSION_NUM >= 0x071301)
| // This is possible since cURL 7.19.1
|
| since ‘CURLOPT_USERNAME’ and ‘CURLOPT_PASSWORD’ were introduced with 7.19.1

I think we should avoid using version number checks in Octave code and
instead use a feature test in the configure script.

Would someone like to submit a patch for that?

Thanks,

jwe
_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

curl/urlwrite problem

2009-11-30T11:58:21Z

Hello,

I think Jaroslav's recent changeset [1] causes an error if curl 7.19.0
is present (e.g. OpenSuse 11.1).

I get:

/bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.
-I.. -I../libcruft/misc -I../liboctave -I../liboctave -I. -I. -g
-O2 -DHAVE_CONFIG_H -I/usr/include/freetype2 -Wall -W -Wshadow
-Wold-style-cast -Wformat -g -O2 -pthread -g -O2 -MT
DLD-FUNCTIONS/DLD_FUNCTIONS_urlwrite_la-urlwrite.lo -MD -MP -MF
DLD-FUNCTIONS/.deps/DLD_FUNCTIONS_urlwrite_la-urlwrite.Tpo -c -o
DLD-FUNCTIONS/DLD_FUNCTIONS_urlwrite_la-urlwrite.lo `test -f
'DLD-FUNCTIONS/urlwrite.cc' || echo './'`DLD-FUNCTIONS/urlwrite.cc
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I../libcruft/misc
-I../liboctave -I../liboctave -I. -I. -g -O2 -DHAVE_CONFIG_H
-I/usr/include/freetype2 -Wall -W -Wshadow -Wold-style-cast -Wformat -g
-O2 -pthread -g -O2 -MT
DLD-FUNCTIONS/DLD_FUNCTIONS_urlwrite_la-urlwrite.lo -MD -MP -MF
DLD-FUNCTIONS/.deps/DLD_FUNCTIONS_urlwrite_la-urlwrite.Tpo -c
DLD-FUNCTIONS/urlwrite.cc -fPIC -DPIC -o
DLD-FUNCTIONS/.libs/DLD_FUNCTIONS_urlwrite_la-urlwrite.o
making gendoc.cc
DLD-FUNCTIONS/urlwrite.cc: In member function ‘void
curl_handle::init(const std::string&, const std::string&, std::istream&,
std::ostream&)’:
DLD-FUNCTIONS/urlwrite.cc:566: error: ‘CURLOPT_USERNAME’ was not
declared in this scope
DLD-FUNCTIONS/urlwrite.cc:568: error: ‘CURLOPT_PASSWORD’ was not
declared in this scope
make[3]: *** [DLD-FUNCTIONS/DLD_FUNCTIONS_urlwrite_la-urlwrite.lo] Fehler 1
make[3]: *** Warte auf noch nicht beendete Prozesse...
make[3]: Leaving directory `/home/kai/hg-octave/octave/src'
make[2]: *** [all] Fehler 2
make[2]: Leaving directory `/home/kai/hg-octave/octave/src'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/home/kai/hg-octave/octave'
make: *** [all] Fehler 2

I think in src/DLD-Functions/urlwrite.cc:

setopt (CURLOPT_NOBODY, 1);
561
562 // Set the username and password
563 #if (LIBCURL_VERSION_NUM >= 0x071300)
564 // This is possible since cURL 7.19.1
565 if (user.length () != 0)
566 setopt (CURLOPT_USERNAME, user.c_str());
567 if (passwd.length () != 0)

line 563

should be changed in:

#if (LIBCURL_VERSION_NUM >= 0x071301)
// This is possible since cURL 7.19.1

since ‘CURLOPT_USERNAME’ and ‘CURLOPT_PASSWORD’ were introduced with 7.19.1

Kai

[1] http://hg.savannah.gnu.org/hgweb/octave/rev/dd3fc8ba4796
_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

sscanf returns zero status

2009-11-30T11:48:17Z

On 30-Nov-2009, vipin.ts@... wrote:

| I am using a matlab script and trying to reproduce it in octave. But I am getting a zero value while handling with sscanf function.
| Here is the code
|
| [num, one, err, delta] = sscanf(string(pos:min(len,pos+20)), '%f', 1);
|
| In this statement matlab gives a delta variable with numeric value, but in octave always I am getting zero value.
|
| Many thanks for helping to solve the problem.

This might be a bug, but you haven't given enough information for
anyone to debug the problem.

What version of Octave are you using?

What is the value of

string(pos:min(len,pos+20))

when sscanf is called?

jwe
_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

sscanf returns zero status

2009-11-30T09:58:15Z

I am using a matlab script and trying to reproduce it in octave. But I am getting a zero value while handling with sscanf function.
Here is the code

[num, one, err, delta] = sscanf(string(pos:min(len,pos+20)), '%f', 1);

In this statement matlab gives a delta variable with numeric value, but in octave always I am getting zero value.

Many thanks for helping to solve the problem.

Thanks,
Vipin
_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

sqp error (nonconformant arguments)

2009-11-30T09:01:34Z

--------
Bug report for Octave 3.0.2 configured for i686-suse-linux-gnu

Description:
-----------

The problem is with the following command:

sqp([1, 1], @(z) norm(z));

I get an error message saying:

---
error: operator +: nonconformant arguments (op1 is 1x2, op2 is 2x1)
error: evaluating binary operator `+' near line 572, column 56
error: evaluating argument list element number 5
error: evaluating while command near line 571, column 3
error: called from `sqp:linesearch_L1' in file
`/usr/share/octave/3.0.2/m/optimization/sqp.m'
error: evaluating while command near line 359, column 5
error: evaluating if command near line 195, column 3
error: called from `sqp' in file
`/usr/share/octave/3.0.2/m/optimization/sqp.m'
---

Note that

sqp([1; 1], @(z) norm(z));

works without problems. I'm new to Octave, but AFAIK if the docs say
'vector' any of x or x' shoud be ok :)

Please excuse if this bug was already fixed in a new version, this is
the latest one I can access right now.

Repeat-By:
---------

Simply run 'sqp([1, 1], @(z), norm(z))'.

Fix:
---

This should be as easy as simply using the transpose of one of the two
vectors summed :)

However once you start changing the operation in line 572 you get an
error later on, etc.

Configuration (please do not edit this section):
-----------------------------------------------

uname output: Linux abel06 2.6.27.37-0.1-pae #1 SMP 2009-10-15
14:56:58 +0200 i686 i686 i386 GNU/Linux
configure opts: '--host=i686-suse-linux-gnu'
'--build=i686-suse-linux-gnu' '--target=i586-suse-linux'
'--program-prefix=' '--prefix=/usr' '--exec-prefix=/usr'
'--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc'
'--datadir=/usr/share' '--includedir=/usr/include' '--libdir=/usr/lib'
'--localstatedir=/var' '--sharedstatedir=/usr/com'
'--mandir=/usr/share/man' '--infodir=/usr/share/info'
'--libexecdir=/usr/lib' 'build_alias=i686-suse-linux-gnu'
'host_alias=i686-suse-linux-gnu' 'target_alias=i586-suse-linux'
'CFLAGS=-march=i586 -mtune=i686 -fmessage-length=0 -O2 -Wall
-D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
-fasynchronous-unwind-tables -g' 'CPPFLAGS=-DH5_USE_16_API'
'CXXFLAGS=-march=i586 -mtune=i686 -fmessage-length=0 -O2 -Wall
-D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
-fasynchronous-unwind-tables -g' 'FFLAGS=-march=i586 -mtune=i686
-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector
-funwind-tables -fasynchronous-unwind-tables -g'
Fortran compiler: gfortran
FFLAGS: -march=i586 -mtune=i686 -fmessage-length=0 -O2 -Wall
-D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
-fasynchronous-unwind-tables -g -mieee-fp
F2C: @F2C@
F2CFLAGS: @F2CFLAGS@
FLIBS: -L/usr/lib/gcc/i586-suse-linux/4.3
-L/usr/lib/gcc/i586-suse-linux/4.3/../../../../i586-suse-linux/lib
-L/usr/lib/gcc/i586-suse-linux/4.3/../../.. -lhdf5 -lz -lgfortranbegin
-lgfortran -lm
CPPFLAGS: -DH5_USE_16_API
INCFLAGS: -I. -I. -I./liboctave -I./src -I./libcruft/misc
C compiler: gcc, version 4.3.2 [gcc-4_3-branch revision 141291]
(SUSE Linux)
CFLAGS: -march=i586 -mtune=i686 -fmessage-length=0 -O2 -Wall
-D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
-fasynchronous-unwind-tables -g
CPICFLAG: -fPIC
C++ compiler: g++, version 4.3.2
CXXFLAGS: -march=i586 -mtune=i686 -fmessage-length=0 -O2 -Wall
-D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
-fasynchronous-unwind-tables -g
CXXPICFLAG: -fPIC
LD_CXX: g++
LDFLAGS:
LIBFLAGS: -L.
RLD_FLAG: -Wl,-rpath -Wl,/usr/lib/octave-3.0.2
BLAS_LIBS: -llapack -lblas
FFTW_LIBS: -lfftw3
BLAS_LIBS: -llapack -lblas
FFTW_LIBS: -lfftw3
LIBS: -lreadline -lncurses -ldl -lhdf5 -lz -lm
LEXLIB:
LIBGLOB:
SED: /usr/bin/sed
DEFS:

-DPACKAGE_NAME="" -DPACKAGE_TARNAME="" -DPACKAGE_VERSION=""
-DPACKAGE_STRING="" -DPACKAGE_BUGREPORT="" -DOCTAVE_SOURCE=1
-D_GNU_SOURCE=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DSEPCHAR=':'
-DSEPCHAR_STR=":" -D__NO_MATH_INLINES=1 -DCXX_NEW_FRIEND_TEMPLATE_DECL=1
-DCXX_ISO_COMPLIANT_LIBRARY=1 -DCXX_ABI=unknown -DHAVE_LIBM=1
-DHAVE_PCRE=1 -DHAVE_REGEXEC=1 -DHAVE_REGEX=1 -DHAVE_ZLIB_H=1
-DHAVE_ZLIB=1 -DHAVE_HDF5_H=1 -DHAVE_HDF5=1 -DHAVE_H5GGET_NUM_OBJS=1
-DHAVE_FFTW3=1 -DHAVE_GLPK_H=1 -DHAVE_GLPK=1 -DHAVE_CURL_CURL_H=1
-DHAVE_CURL=1 -DHAVE_IEEE754_DATA_FORMAT=1 -DF77_FUNC(name,NAME)=name ##
_ -DF77_FUNC_(name,NAME)=name ## _ -DHAVE_BLAS=1 -DHAVE_GETHOSTNAME=1
-DHAVE_GETPWNAM=1 -DHAVE_DEV_T=1 -DHAVE_INO_T=1 -DHAVE_NLINK_T=1
-DHAVE_NLINK_T=1 -DHAVE_LONG_LONG_INT=1 -DHAVE_UNSIGNED_LONG_LONG_INT=1
-DHAVE_SIGSET_T=1 -DHAVE_SIG_ATOMIC_T=1 -DSIZEOF_SHORT=2
-DSIZEOF_INT=4 -DSIZEOF_LONG=4 -DSIZEOF_LONG_LONG=8 -DHAVE_ALLOCA_H=1
-DHAVE_ALLOCA=1 -DNPOS=std::string::npos -DHAVE_PLACEMENT_DELETE=1
-DHAVE_DYNAMIC_AUTO_ARRAYS=1 -DSTDC_HEADERS=1 -DHAVE_DIRENT_H=1
-DTIME_WITH_SYS_TIME=1 -DHAVE_SYS_WAIT_H=1 -DHAVE_ASSERT_H=1
-DHAVE_CURSES_H=1 -DHAVE_DLFCN_H=1 -DHAVE_FCNTL_H=1 -DHAVE_FLOAT_H=1
-DHAVE_GRP_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_LIMITS_H=1 -DHAVE_LOCALE_H=1
-DHAVE_MEMORY_H=1 -DHAVE_NCURSES_H=1 -DHAVE_POLL_H=1 -DHAVE_PWD_H=1
-DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_SYS_IOCTL_H=1
-DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_POLL_H=1 -DHAVE_SYS_RESOURCE_H=1
-DHAVE_SYS_SELECT_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TIME_H=1
-DHAVE_SYS_TIMES_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_UTSNAME_H=1
-DHAVE_TERMCAP_H=1 -DHAVE_UNISTD_H=1 -DHAVE_UTIME_H=1 -DHAVE_SSTREAM=1
-DHAVE_TERMIO_H=1 -DHAVE_SGTTY_H=1 -DHAVE_GLOB_H=1 -DHAVE_FNMATCH_H=1
-DHAVE_FNMATCH=1 -DHAVE_GLOB=1 -DHAVE_ATEXIT=1 -DHAVE_BASENAME=1
-DHAVE_BCOPY=1 -DHAVE_BZERO=1 -DHAVE_CANONICALIZE_FILE_NAME=1
-DHAVE_CHMOD=1 -DHAVE_DUP2=1 -DHAVE_ENDGRENT=1 -DHAVE_ENDPWENT=1
-DHAVE_EXECVP=1 -DHAVE_FCNTL=1 -DHAVE_FORK=1 -DHAVE_GETCWD=1
-DHAVE_GETEGID=1 -DHAVE_GETEUID=1 -DHAVE_GETGID=1 -DHAVE_GETGRENT=1
-DHAVE_GETGRGID=1 -DHAVE_GETGRNAM=1 -DHAVE_GETPGRP=1 -DHAVE_GETPID=1
-DHAVE_GETPPID=1 -DHAVE_GETPWENT=1 -DHAVE_GETPWUID=1 -DHAVE_GETTIMEOFDAY=1
-DHAVE_GETUID=1 -DHAVE_GETWD=1 -DHAVE_KILL=1 -DHAVE_LGAMMA=1
-DHAVE_LINK=1 -DHAVE_LOCALTIME_R=1 -DHAVE_LSTAT=1 -DHAVE_MEMMOVE=1
-DHAVE_MKDIR=1 -DHAVE_MKFIFO=1 -DHAVE_MKSTEMP=1 -DHAVE_ON_EXIT=1
-DHAVE_PIPE=1 -DHAVE_POLL=1 -DHAVE_PUTENV=1 -DHAVE_RAISE=1
-DHAVE_READLINK=1 -DHAVE_REALPATH=1 -DHAVE_RENAME=1 -DHAVE_RINDEX=1
-DHAVE_RMDIR=1 -DHAVE_ROUND=1 -DHAVE_SELECT=1 -DHAVE_SETGRENT=1
-DHAVE_SETLOCALE=1 -DHAVE_SETPWENT=1 -DHAVE_SETVBUF=1 -DHAVE_SIGACTION=1
-DHAVE_SIGLONGJMP=1 -DHAVE_SIGPENDING=1 -DHAVE_SIGPROCMASK=1
-DHAVE_SIGSUSPEND=1 -DHAVE_SNPRINTF=1 -DHAVE_STAT=1 -DHAVE_STRCASECMP=1
-DHAVE_STRDUP=1 -DHAVE_STRERROR=1 -DHAVE_STRNCASECMP=1 -DHAVE_STRPTIME=1
-DHAVE_STRSIGNAL=1 -DHAVE_SYMLINK=1 -DHAVE_TEMPNAM=1 -DHAVE_TGAMMA=1
-DHAVE_UMASK=1 -DHAVE_UNAME=1 -DHAVE_UNLINK=1 -DHAVE_USLEEP=1
-DHAVE_UTIME=1 -DHAVE_VFPRINTF=1 -DHAVE_VSPRINTF=1 -DHAVE_VSNPRINTF=1
-DHAVE_WAITPID=1 -DHAVE_STRFTIME=1 -DHAVE_LIBDL=1 -DHAVE_DLOPEN=1
-DHAVE_DLSYM=1 -DHAVE_DLERROR=1 -DHAVE_DLCLOSE=1 -DHAVE_DLOPEN_API=1
-DENABLE_DYNAMIC_LINKING=1 -DHAVE_TIMEVAL=1 -DHAVE_FINITE=1
-DHAVE_ISNAN=1 -DHAVE_ISINF=1 -DHAVE_COPYSIGN=1 -DHAVE_DECL_SIGNBIT=1
-DHAVE_ACOSH=1 -DHAVE_ASINH=1 -DHAVE_ATANH=1 -DHAVE_ERF=1 -DHAVE_ERFC=1
-DHAVE_EXP2=1 -DHAVE_LOG2=1 -DHAVE_STRUCT_STAT_ST_BLKSIZE=1
-DHAVE_STRUCT_STAT_ST_BLOCKS=1 -DHAVE_STRUCT_STAT_ST_RDEV=1
-DHAVE_STRUCT_TM_TM_ZONE=1 -DHAVE_TM_ZONE=1 -DUSE_READLINE=1
-DEXCEPTION_IN_MATH=1 -DRETSIGTYPE=void -DHAVE_DECL_SYS_SIGLIST=1
-DHAVE_POSIX_SIGNALS=1 -DRETSIGTYPE_IS_VOID=1 -DHAVE_GETRUSAGE=1
-DHAVE_TIMES=1 -DYYTEXT_POINTER=1 -DGNUPLOT_BINARY="gnuplot"

User-preferences (please do not edit this section):
--------------------------------------------------

EDITOR = emacs
EXEC_PATH =
/usr/lib/octave/3.0.2/site/exec/i686-suse-linux-gnu:/usr/lib/octave/api-v32/site/exec/i686-suse-linux-gnu:/usr/lib/octave/site/exec/i686-suse-linux-gnu:/usr/lib/octave/3.0.2/exec/i686-suse-linux-gnu:/usr/bin:/home/brucker/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/opt/kde3/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:/usr/lib/qt3/bin
IMAGE_PATH = .:/usr/share/octave/3.0.2/imagelib
PAGER = less
PS1 = octave:\#>
PAGER = less
PS1 = octave:\#>
PS2 = octave:\#+>
PS4 = +
beep_on_error = 0
completion_append_char =
crash_dumps_octave_core = 1
echo_executing_commands = 4
fixed_point_format = 0
gnuplot_binary = gnuplot
gnuplot_command_end =

gnuplot_command_plot = pl
gnuplot_command_replot = rep
gnuplot_command_splot = sp
gnuplot_command_title = t
gnuplot_command_using = u
gnuplot_command_with = w
history_file = /home/brucker/.octave_hist
history_size = 1024
ignore_function_time_stamp = system
info_file = /usr/share/info/octave.info
info_program = info
makeinfo_program = makeinfo
max_recursion_depth = 256
output_max_field_width = 5
output_precision = 5
page_output_immediately = 0
page_screen_output = 1
print_answer_id_name = 1
print_empty_dimensions = 1
save_precision = 16
saving_history = 0
sighup_dumps_octave_core = 1
sigterm_dumps_octave_core = 1
silent_functions = 0
split_long_rows = 1
string_fill_char =
struct_levels_to_print = 2
suppress_verbose_help_message = 0

_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Re: base class assignment problem (was: Re: very strange bug)

2009-11-30T02:34:51Z

On 02.11.2009, at 17:43, John W. Eaton wrote:

> On 2-Nov-2009, Jaroslav Hajek wrote:
>
> | On Fri, Oct 30, 2009 at 6:38 PM, John W. Eaton <jwe@...> wrote:
> | > On 30-Oct-2009, Lukas Reichlin wrote:
> | >
> | > | control-oo is here:
> | > | http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/control-oo/
> | > |
> | > | Download the package with:
> | > | http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/control-oo.tar.gz?view=tar
> | > |
> | > | Make sure that the "legacy" control package is not in your Octave
> | > | path, because some functions have identical names (Matlab
> | > | compatibility).
> | > |
> | > | I reduced the example as good as possible. If it is still too
> | > | complicated to understand, you will have to wait until Robert posts
> | > | his example next weekend.
> | >
> | > I'm attaching a minimal example. Unpack the oo-bug.tar.gz file, cd to
> | > the oo-bug directory and run the bug.m script.
> | >
> | > The problem seems to be that the base class objects are not properly
> | > copied when their fields are modified inside methods. I don't have a
> | > solution so it would be great if someone else would like to take a
> | > shot a fixing this problem.
> | >
> | > jwe
> | >
> | >
> |
> | How about this?
> | http://hg.savannah.gnu.org/hgweb/octave/rev/0df32e0b2074
>
> This change fixes the problem for me.
>
> Thanks,
>
> jwe

Thanks for fixing the bug. However, I couldn't test whether the change fixes the problem for me because I'm (still) unable to compile Octave from source (I'm using Octave.app on MacOSX). It would be great if the fix would be included in the upcoming release 3.2.4, since the control-oo package depends on it.

Regards,
Lukas

BTW: Luca Favatella (the maintainer of "control") and I intend to make control-oo the "official" control package once the fix for Octave arrives. This step would offer substantially better compatibility to Matlab's control systems toolbox for the average user. It would fix some long-standing bugs as well ...

_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Re: Fixing HDF-1.8 API for octave-3.2.x

2009-11-28T05:02:07Z

John W. Eaton wrote:
> No, I don't think they were applied. Do they look OK to you? If so,
> I have no objection to applying them, though it would be slightly
> easier to do that if they were hg changesets relative to the current
> sources instead of simple context diffs relative to Octave 3.2.2.
>
>

Ok, I've started applying and pushing these patches

D.

_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Re: eigs crash on a particular spare matrix

2009-11-28T04:41:35Z

This appears to be the same bug in ARPACK that I ran into (valgrind
shows the same behavior), so I can confirm in Octave 3.2.3 on Ubuntu
9.10 32- and 64-bit. I'd suggest using the work around proposed by
Marco Caliari and convert the matrix to be complex before running eigs:

A(1,1) = A(1,1) + j * 0; % Add a complex component with magnitude 0

This forces eigs to use a different set of functions internally,
functions that do not exhibit the over-convergence bug, and preserves
the result. Sadly, this makes eigs twice as slow...

Cheers,
Cyrus

On Sat, 2009-11-28 at 11:52 +0100, Idomeneas Pateros wrote:

> Hello
> I obtain a core processing these files :
>
> function mysparse(i)
> P=[ones(10,10),zeros(10,10)
> ones(10,10),-i*ones(10,10)];
> A=sparse(P);
> [v,d]=eigs(A);
> endfunction
>
> function testmysparse(n)
> for i=1:n
> mysparse(i)
> end
> endfunction
>
> When I call the testmysparse function in command prompt :
> testmysparse(6)
> the Octave version 3.2.2 in ubuntu 9.10 32 bit crashes producing this
> message :
> *** glibc detected *** octave: double free or corruption (!prev):
> 0x086808a8 ***
> which it seems to be an error with double free (or double malloc) of a
> memory reference
> I can't run this program in a different machine (64 bit or other OS in 32
> bit).
> Can anyone inform me if it runs under other platforms ?
>
> Thanks
> Idomeneas
>
>
>
> Cyrus Hall wrote:
> >
> > Ciao all-
> >
> > I've been happily using eigs for a couple months now and have never run
> > into any problems. However I have recently run into a particular matrix
> > that *sometimes* crashes octave *only* when both the eigenvalues and
> > eigenvectors are requested. I.e.
> >
> > [V,S] = eigs(P);
> >
> > I have no idea where to start trying to find a minimal matrix that
> > causes the error, so I've just posted the single (and only) matrix I've
> > found that triggers the bug:
> >
> > http://www.inf.usi.ch/phd/hall/core-matrix.oct
> >
> > Just run eigs, with two output arguments, several times and you should
> > experience the crash. I've confirmed the same behavior on two different
> > machines, one an Intel 32-bit and the other a 64-bit Opteron, both
> > running 3.2.3. Both builds of Octave are my own, so I also installed
> > the latest Ubuntu package (3.2.2) and confirmed it has the same problem
> > and that the valgrind trace looks very similar.
> >
> > I've posted a valgrind session with the same matrix. It can be found
> > here:
> >
> > http://www.inf.usi.ch/phd/hall/octave-valgrind-bad-matrix-eigs.txt
> >
> > (ignore the libreadline off-by one read errors on startup - it appears
> > readline needs some love)
> >
> > The session is from the 32-bit machine, but the errors are the same on
> > the 64-bit box: A bunch of invalid writes from dlacpy_
> > in /usr/lib/liblapack.so.3gf.o, followed by invalid reads. Apparently
> > the memory malloc uses eventually gets stomped on, as free or malloc
> > eventually causes the program to crash in the end. The exactly free or
> > malloc is non-deterministic.
> >
> > I am not using the known to be bad ubuntu version of atlas, and only
> > have the non-optimized version installed - indeed, atlas isn't even
> > installed on the x64 box and it has the same problem.
> >
> > When results are computed without a crash they are correct (taking
> > matlab as correct).
> >
> > Cheers,
> > Cyrus
> >
> > _______________________________________________
> > Bug-octave mailing list
> > Bug-octave@...
> > https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave
> >
> >
>

_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave

Re: eigs crash on a particular spare matrix

2009-11-28T04:21:28Z

Idomeneas Pateros wrote:

This is the same problem and can be treated with the patch I proposed to
arpack.. See the rest of thread at

http://old.nabble.com/eigs-crash-on-a-particular-spare-matrix-to26390119.html

For the patch at the explanation

D.

--
David Bateman dbateman@...
35 rue Gambetta +33 1 46 04 02 18 (Home)
92100 Boulogne-Billancourt FRANCE +33 6 72 01 06 33 (Mob)

_______________________________________________
Bug-octave mailing list
Bug-octave@...
https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave