On Jun 18, 11:06 am, just_a_user <[EMAIL PROTECTED]> wrote:
> Hi Michael,
Hi Hans,
> I tried to build 3.0.2 again, which failed. The new zipped log
> file is posted on my webpage: www.math.umass.edu/~johnston
>
> Just to let you know, for this build I MOVED my g77, g95, and gfortran
> to force the SAGE build to use its own g95.
>
> If you do find a way around the build problem please do let me know.
>
> Thanks, Hans
I got the 3.0.2 build log and it blows up at
customize G95FCompiler
don't know how to compile Fortran code on platform 'posix'
Traceback (most recent call last):
File "setup.py", line 53, in <module>
setup_package()
File "setup.py", line 45, in setup_package
configuration=configuration )
File "/opt/sage-3.0.2/local/lib/python2.5/site-packages/numpy/
distutils/core.py", line 176, in setup
return old_setup(**new_attr)
File "/opt/sage-3.0.2/local/lib/python2.5/distutils/core.py", line
151, in setup
dist.run_commands()
File "/opt/sage-3.0.2/local/lib/python2.5/distutils/dist.py", line
974, in run_commands
self.run_command(cmd)
File "/opt/sage-3.0.2/local/lib/python2.5/distutils/dist.py", line
994, in run_command
cmd_obj.run()
File "/opt/sage-3.0.2/local/lib/python2.5/distutils/command/
build.py", line 112, in run
self.run_command(cmd_name)
File "/opt/sage-3.0.2/local/lib/python2.5/distutils/cmd.py", line
333, in run_command
self.distribution.run_command(command)
File "/opt/sage-3.0.2/local/lib/python2.5/distutils/dist.py", line
994, in run_command
cmd_obj.run()
File "/opt/sage-3.0.2/local/lib/python2.5/site-packages/numpy/
distutils/command/build_clib.py", line 83, in run
self.fcompiler.customize(self.distribution)
AttributeError: 'NoneType' object has no attribute 'customize'
Error building scipy.
The same issue about "don't know how to compile Fortran code on
platform 'posix'" also happens with numpy, but it does not actually
throw an exception there. Since the Scipy we ship is ancient (a 1.5
year old svn checkout IIRC) and the numpy is much more current I would
like to upgrade to a more recent Scipy and try again. The upgrade will
hopefully happen next week. The just released 3.0.3 will not fix the
problem unfortunately. One potential solution could be to remove
fortran compilers like the Intel fortran compiler from $PATH and try
again. But that is certainly a shot in the dark.
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
