Re: Octave 3.5.92 snapshot available for ftp

[Ben Abbott]

On Jan 7, 2012, at 6:03 AM, Lukas Reichlin wrote:

> On 06.01.2012, at 22:54, John W. Eaton wrote:
> 
>> On  6-Jan-2012, Lukas Reichlin wrote:
>> 
>> | On 06.01.2012, at 22:02, John W. Eaton wrote:
>> | 
>> | > 
>> | > A new snapshot of Octave is now available from alpha.gnu.org in the
>> | > directory /gnu/octave:
>> | > 
>> | >  48481042bdd5f924ccfc983916cd1e16  octave-3.5.92.tar.gz
>> | > 
>> | >  -rw-r--r-- 1 3003 3002 17958889 Jan 06 20:55 octave-3.5.92.tar.gz
>> | > 
>> | > The snapshot is tagged in the usual way (ss-3-5-92) in the Mercurial
>> | > archive.
>> | > 
>> | > Please remember that these snapshots are provided for testing
>> | > purposes.  I do not consider them to be Octave releases.  If people
>> | > think there will be confusion because of the version number, then we
>> | > can add a notice to the Octave startup message.
>> | > 
>> | > Unless there are some serious problems with this snapshot, I would
>> | > like to release it (or something very close to it) as 3.6.0 in the
>> | > next few days.  Even if you have been building Octave regularly from
>> | > the Mercurial archive, it would help if you could build from the
>> | > snapshot and report any problems.
>> | > 
>> | > jwe
>> | 
>> | I've created a MacPorts portfile for the Mac users amongst us. The build 
>> failed, but I don't know the reason. I attached the log in main.log
>> 
>> Does the following change fix the problem for you?
>> 
>> http://hg.savannah.gnu.org/hgweb/octave/rev/906eecd4bf43
>> 
>> After applying this change, I think you will need to do run the
>> following commands in your source tree, then run Make again.  Since
>> this change affects a file that is included in a Makefile.am file,
>> you'll need automake and autoconf for this patch to work when applied
>> to the 3.5.92 sources.  You should not need them when building from a
>> future snapshot or release tarball.
>> 
>> cd src/DLD-FUNCTIONS
>> ./config-module.sh
>> 
>> jwe
> 
> I applied your patch but the build failed. I think it is because I used the 
> wrong arguments, usually I build with MacPorts portfiles, not by hand just 
> using MacPorts for the dependencies.
> 
> The tools should be installed:
> ==============================
> ra:~ lukas$ port installed | grep pcre
>  git-core @1.7.7.4_0+doc+pcre+python27 (active)
>  pcre @8.12_1 (active)
> ra:~ lukas$ port installed | grep auto
>  autoconf @2.68_2 (active)
>  automake @1.11.2_0 (active)
> 
> 
> Ben Abbott's configure arguments:
> =================================
> For gcc-4.5
> 
> 
> ./autogen.sh
> 
> VER="4.5"
> 
> export PREFIX=/opt/local
> export CC=/opt/local/bin/gcc-mp-$VER
> export CXX=/opt/local/bin/g++-mp-$VER
> export CXXCPP="/opt/local/bin/g++-mp-$VER -E"
> export F77=/opt/local/bin/gfortran-mp-$VER
> export FC=/opt/local/bin/gfortran-mp-$VER
> export CXXFLAGS="-pipe -O2 -g -m64 -ggdb3"
> export FFLAGS="$CXXFLAGS -D_THREAD_SAFE -pthread -gstabs"
> export CFLAGS="$FFLAGS -lstdc++"
> export LDFLAGS=-L$PREFIX/lib
> export CPPFLAGS=-I$PREFIX/include
> export BLAS_LIBS="-lcblas -lf77blas -latlas"
> export LAPACK_LIBS=-llapack
> 
> ./configure --prefix="/opt/local" --without-framework-carbon --with-x 
>           --with-cholmod="-lcholmod -lmetis"
> 
> make -j2

Lukas, you missed the back-slash, used for line continuation.

./configure --prefix="/opt/local" --without-framework-carbon --with-x \
          --with-cholmod="-lcholmod -lmetis"

Ben