Re: Packaging Octave for Windows and OS X... all but not perfs

[Samir Sharshar]

Yes,

Wel gfortran seems to me to be in a very earlier alpha stage ;-)

I've used with a correct PATH (sorry...) my old brave g77 compiler.

I've recompiled Octave with the "new" gcc 3.3.2 from Apple in the hope 
to obtain greater performance.

Tears... my new compiled octave 2.1.64 on my beautiful dual G5 2GHZ 
benchs are really catastrophic... just like an ugly PIV 2 GHZ... :-)

Octave 2.1.64 complied on Opteron is twice faster... Where the glitch ?

Samir
Le 17 déc. 04, à 17:43, Joe Koski a écrit :

> Samir,
>
> First, I tried gfortran on three old Fortran codes: one encountered an
> internal compiler error (known), one compiled but failed at execution, 
> and
> the third worked properly. In other words, gfortran is still "alpha" 
> and not
> ready to be a work horse yet.
>
> Is your system finding g77 properly? I have attempted to build octave, 
> but
> had it fail later in the build. In my .bashrc (or you could 
> alternatively
> use .bash_profile) I have
>
> PATH=/usr/local/bin:$PATH
> export PATH
> export GNUTERM=aqua
> export DISPLAY=:0.0
> export FC=g77
> export CC=gcc
>
> defined to help g77 and octave locate things. Can you compile Fortran 
> code
> outside the octave build? That's the first thing I would check, but no
> guarantees...
>
> Joe
>
>
> on 12/17/04 2:53 AM, Samir Sharshar at address@hidden wrote:
>
> > >
> > Hello,
> >
> > Running on OSX Panther 10.3.6
> >
> > gcc -v
> > Reading specs from /usr/libexec/gcc/darwin/ppc/3.3/specs
> > Thread model: posix
> > gcc version 3.3 20030304 (Apple Computer, Inc. build 1671)
> >
> > I've got the g95v4.0.-bin.taar.gz from hpc.sourceforge.net
> >
> > gfortran -v
> > Reading specs from
> > /usr/local/lib/gcc/powerpc-apple-darwin7.5.0/4.0.0/specs
> > Configured with: ../gcc/configure --enable-threads=posix
> > --enable-languages=f95 --enable-static --disable-shared
> > Thread model: posix
> > gcc version 4.0.0 20041009 (experimental)
> >
> > configure RAS
> > make give an error on compiling libcruft/ranlib/qrgnin.f at line:48
> > with TODO: functions with alternate entry points
> >
> > ...well...
> >
> > I've try to return to my old(?) g77 3.4 with ./configure --with-f77=
> > '/usr/local/bin/g77' and I've get
> >
> > defining F77 to be /usr/local/bin/g77
> > checking whether we are using the GNU Fortran 77 compiler... no
> > checking whether /usr/local/bin/g77 accepts -g... no
> > checking how to get verbose linking output from /usr/local/bin/g77...
> > configure: WARNING: compilation failed
> >
> > checking for Fortran libraries of /usr/local/bin/g77...
> > -L/usr/local/lib -lg2c
> > checking for dummy main to link with Fortran libraries... none
> > checking for Fortran name-mangling scheme... configure: error: cannot
> > compile a simple Fortran program
> >
> > Any idea ?
> >
> > Thanks,
> >
> > Samir
> >
> > > -------------------------------------------------------------
> > > Octave is freely available under the terms of the GNU GPL.
> > >
> > > Octave's home on the web:  http://www.octave.org
> > > How to fund new projects:  http://www.octave.org/funding.html
> > > Subscription information:  http://www.octave.org/archive.html
> > > -------------------------------------------------------------
> >
> >
> >
> > -------------------------------------------------------------
> > Octave is freely available under the terms of the GNU GPL.
> >
> > Octave's home on the web:  http://www.octave.org
> > How to fund new projects:  http://www.octave.org/funding.html
> > Subscription information:  http://www.octave.org/archive.html
> > -------------------------------------------------------------



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------