Re: installing Octave 4.0.1

[Andreas Weber]

Am 28.03.2016 um 16:23 schrieb Steph Bredenhann:
> 
> On 28/03/2016 11:43, Andreas Weber wrote:
>> Am 28.03.2016 um 09:33 schrieb Steph Bredenhann:
>>> I am install Octave 4.0.1 0n a Lenovo W520 laptop running Ubuntu 15.10,
>>> ./configure and make was successful, but sudo make install ended with:
>>>
>>>    GEN      .DOCSTRINGS
>>> Unable to parse dldfcn/__init_fltk__.df at line 4
>> Can you have a look at this thread?
>> http://octave.1599824.n4.nabble.com/Unable-to-parse-dldfcn-init-fltk-df-td4673719.html
>>
>>
>> Quote from Mike: "The text that starts with "XDEFUN_DLD_INTERNAL (" and
>> ends with ")" should also be a single line."
>>
>> Is this the case in your __init_fltk__.df?
>>
>> -- Andy
> I have seen this link yesterday before I made my post, my situation is
> identical:
> 
> address@hidden:/tmp/octave-4.0.1$ g++ --version
> g++ (Ubuntu 5.2.1-22ubuntu2) 5.2.1 20151010
> Copyright (C) 2015 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> address@hidden:/tmp/octave-4.0.1$ sed --version
> sed (GNU sed) 4.2.2
> Copyright (C) 2012 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>.
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> 
> Written by Jay Fenlason, Tom Lord, Ken Pizzini,
> and Paolo Bonzini.
> GNU sed home page: <http://www.gnu.org/software/sed/>.
> General help using GNU software: <http://www.gnu.org/gethelp/>.
> E-mail bug reports to: <address@hidden>.
> Be sure to include the word ``sed'' somewhere in the ``Subject:'' field.
> address@hidden:/tmp/octave-4.0.1$ whereis sed
> sed: /bin/sed /usr/share/man/man1/sed.1.gz /usr/share/info/sed.info.gz
> address@hidden:/tmp/octave-4.0.1$
> 
> if I follow the test given:
> 
> address@hidden:/tmp/octave-4.0.1$ ./libinterp/gendoc.pl
> ./libinterp/dldfcn/__init*.df
> ### DO NOT EDIT!
> ###
> ### This file is generated automatically from Octave source files.
> ### Edit source files directly and run make to update this file.
> 
> Unable to parse ./libinterp/dldfcn/__init_fltk__.df at line 4
> 

Hi Steph,
I've asked you to check if the line in __init_fltk__.df starts with
XDEFUN_DLD_INTERNAL (" and ends with )" without linebreaks. If this is
the case you should try to find the point where the additional unwanted
linebreaks are introduced.

If you remove the file from the build dir and run "make V=1" you'll see
the commands which generate the intermediate files. For example on my
system:

g++ -std=gnu++11 -E -DHAVE_CONFIG_H -I. -I../octave-src  \
  -Iliboctave -I../octave-src/liboctave
-I../octave-src/liboctave/cruft/misc -I../octave-src/liboctave/array
-Iliboctave/numeric -I../octave-src/liboctave/numeric
-Iliboctave/operators -I../octave-src/liboctave/operators
-I../octave-src/liboctave/system -I../octave-src/liboctave/util
-I../octave-src/libinterp/octave-value -Ilibinterp
-I../octave-src/libinterp -I../octave-src/libinterp/operators
-Ilibinterp/parse-tree -I../octave-src/libinterp/parse-tree
-Ilibinterp/corefcn -I../octave-src/libinterp/corefcn -Ilibgnu
-I../octave-src/libgnu   -I/usr/include/cairo -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/freetype2 -I/usr/include/libpng12  -DCP936
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_THREAD_SAFE -D_REENTRANT
-I/usr/include/freetype2  -I/usr/include/freetype2  \
  -pthread -fopenmp -Wall -W -Wshadow -Wold-style-cast -Wformat
-Wpointer-arith -Wwrite-strings -Wcast-align -Wcast-qual -g -O2 \
  -DMAKE_BUILTINS ../octave-src/libinterp/dldfcn/__init_fltk__.cc >
libinterp/dldfcn/__init_fltk__.df-t1

/bin/bash ../octave-src/libinterp/mkdefs ../octave-src/libinterp
../octave-src/libinterp/dldfcn/__init_fltk__.cc <
libinterp/dldfcn/__init_fltk__.df-t1 > libinterp/dldfcn/__init_fltk__.df-t

I would first execute the first part and then the second part to find
the problem.

-- Andy