Re: Relocatable octave

[Paul Kienzle]

On May 28, 2007, at 5:15 PM, Thomas Treichl wrote:

> Paul Kienzle schrieb:
>
> > >  and 2nd because other users must not have installed the same 
> > > macports compilers than me - this would mean that the mkoctfile 
> > > shell script must be changed by hand). Shipping the same compilers 
> > > with the octave.dmg wouldn't make sense, because then the octave.dmg 
> > > grows from 70MB to > 200MB.
> > This problem is more difficult.  I'm hoping you can use the default 
> > C/C++ compiler and just ship your own version of the fortran 
> > compiler.
>
> I can use the default gcc now and gfortran from the link you've sent. 
> Together they are doing a good job. I actually don't want to ship just 
> a gfortran with the octave.app but further tell the users where to get 
> that one needed in a seperate *html file.

Your call.

You have to be sure to supply any dynamic libraries from fortran that 
you link against because the octave core will require them.  Linking 
against a static version is questionable practice (something about code 
not being relocatable on the static version) and I have not fully 
tested that it works.

Another concern is that some folks will already have a fortran compiler 
installed, and this will not work with the fortran you used.  Asking 
them to install yours may break their existing software.

Regardless of how you resolve these issues, please make sure the 
fortran compiler is available from the same site as octave --- if the 
site you link to upgrades their fortran compiler your package may stop 
working.  This happened to me with AquaTerm and GnuPlot being out of 
sync.


        - Paul