Re: isis 1.5.0-20 installation on snow Leopard

On Feb 1, 2010, at 7:29 PM, juan luna wrote:

> Using built-in specs.
> Target: i686-apple-darwin8
> Configured with: /Builds/unix/gcc/gcc-4.2/configure --prefix=/usr/local --mandir=/share/man --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --build=i686-apple-darwin8 --host=i686-apple-darwin8 --target=i686-apple-darwin8 --enable-languages=fortran
> Thread model: posix
> gcc version 4.2.1

Hi Juan-

Aside from John Davis's request to get the contents of the "typescript" file, I'll toss out the following.   I have had remarkable success lately building both HEASOFT (6.6.2, 6.7, and 6.8) and S-lang (2.1, 2.2) and ISIS (1.4.9-xx through 1.5.0-20), plus all the associated modules, and haven't been running into any of the problems others have.  (I know of at least two people struggling to get HEASOFT working on the Macs, and you're having problems with ISIS.)  Here's a list of things I do, and maybe equally importantly, don't do.  I'm not sure what the magic combination is that has allowed me to get away with relatively painless builds.

1) I long ago gave up on Fink.  I have found that a lot of the stuff in Fink is very old, and that /sw directory tree got pretty crowded with stuff that I don't use a lot.  I mostly download stuff individually as I need it, avoiding getting it from fink.  The /sw tree is at the very end of my paths.

2)  The Apple X Code software, a lot of which is in /usr/bin, is in the middle of my paths.  GCC 4.2.1 above looks to be the Apple X Code version.  From my little reading of web sites, gfortran versions prior to the one associated with gcc 4.3.x hadn't yet restored all the bells and whistles that were present in gcc 3.4 versions.  It might be worthwhile to upgrade gcc, and not use the /usr/bin paths as your main source of compilers and libraries.

3) I prepend my paths with /usr/local/bin, and I have been installing everything along the /usr/local directory tree path.  

4) I installed gcc 4.4.0 in /usr/local/bin (from a Mac 10.5 binary, which seems to still work under 10.6 just fine), and use that in all of my builds:

mnowak%> which gcc
/usr/local/bin/gcc
mnowak%> /usr/local/bin/gcc --version
gcc (GCC) 4.4.0 20081219 (experimental)
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

mnowak%> /usr/local/bin/gfortran --version
GNU Fortran (GCC) 4.4.0 20081219 (experimental)
Copyright (C) 2008 Free Software Foundation, Inc.

GNU Fortran comes with NO WARRANTY, to the extent permitted by law.
You may redistribute copies of GNU Fortran
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING

That was from sourceforge, which I know has a gcc 4.5 binary sitting there now.  I don't know if that one is as trustworthy as the gcc 4.4 version (which is probably still there, but might require a bit deeper digging on the web pages).

Cheers,

Mike




----
You received this message because you are
subscribed to the isis-users list.
To unsubscribe, send a message to
isis-users-request_at_email.domain.hiddenwith the first line of the message as:
unsubscribe