gfortran on MacOS X
Bill Northcott
w.northcott@unsw.edu.au
Mon May 2 11:58:00 GMT 2005
On 02/05/2005, at 8:34 PM, Dominik Epple wrote:
> Thank you for your explications.
>
> I did as described above. Especially, my modifications to the
> build_gcc script are:
>
> 105c105,106
> < --build=$BUILD-apple-darwin$DARWIN_VERS"
> ---
> > --build=$BUILD-apple-darwin$DARWIN_VERS \
> > $MYFLAGS"
> 321a323,324
> > # dominik hack
> > cp -p $DIR/dst-$BUILD-$t$DEST_ROOT/lib/libgfortranbegin.* .
> $DEST_ROOT/lib/ || exit 1
I have not hacked around there. I will have a look at it. My
thoughts are that to do the job properly it should all be conditional
of f95 being requested.
>
>
> where I use $MYFLAGS to tell configure where my GMP lives.
I did not need anything to tell the build system where mine was in /
usr/local.
> After installing the compiler into /usr using ditto, I can
> successfully compile and run my a litte numeric testprogram. :)
The compiler as at the gcc-4.0.0 release has a major problem which is
described in the documentation. It cannot build a function with
alternate entry points. A patch for this (PR13082) was committed to
the cvs on 29 April. I have added this patch manually to the Apple
gcc-5013 code and it seems to work. It will now build Octave which
was not possible with gcc-4.0.0 release version.
>
> Playing with the idea of providing binary packages for gfortran.org
> (as someone doing so is missing as I read), let me ask the
> following question: how do I build such nice .dmgs with pkgs inside?
Apple's developer tools contain a nice GUI package maker which wraps
the code up with any install scripts you want. Disk images can be
made with Disk Utility from /Applications/Utilities. Everything is
well documented.
>
> If I understand correctly it is all about the equivalent of 'tar cf
> gfortran.tar build/dst' ...
Don't go there. The Apple utilities are much easier to use.
Regards
Bill
More information about the Fortran
mailing list