[Pkg-octave-devel] compilation with gcc-4.3

[Rafael Laboissiere]

* Cyril Brulebois <cyril.brulebois at enst-bretagne.fr> [2008-02-06 13:12]:

> Well, that's not necessarily supported by the underlying build system.
> If you want to make sure 4.3 is used, you can have a look at
> gcc-snapshot (which is also from the 4.3 series), that you can use by
> exporting PATH and LD_LIBRARY_PATH as explained in README.Debian, and
> then passing “-ePATH -eLD_LIBRARY_PATH” to debuild, as first
> parameters (that is important so that they are taken into account,
> don't put them e.g. after “-us -uc -b”).

Thanks for the suggestion.  I was too lazy to use gcc-snapshot during my
tests.

Anyway, I tested again following your instructions above and the package
built fine with g++ 4.3, no need for the cstring patch provided by Pascal.
Also, octave runs fine here, as per ./run-octave.

However, the build does not complete, choking at:

    dh_shlibdeps -a -l/usr/lib/octave-3.0.0
    dpkg-shlibdeps: failure: no dependency information found for /usr/lib/gcc-snapshot/lib/libstdc++.so.6 (used by debian/octave3.0/usr/lib/octave/3.0.0/oct/x86_64-pc-linux-gnu/getrusage.oct).
    dh_shlibdeps: command returned error code 512

Do you know how to get around this?    

An unrelated issue: Using gcc-snapshot for building the current octave
package is not as simple as setting the environment variables as suggested.
The problem comes from debian/rules, in which the compiler paths are
hardcoded:

    c_compiler= /usr/bin/gcc
    cxx_compiler= /usr/bin/g++
    f77_compiler= /usr/bin/gfortran

If nobody objects, I will change the above to:    

    c_compiler= gcc
    cxx_compiler= g++
    f77_compiler= gfortran
 
-- 
Rafael