math/sage error log message

Montgomery-Smith, Stephen stephen at missouri.edu
Wed May 14 20:13:34 UTC 2014


On 05/14/2014 02:36 PM, Bruce wrote:
> At this time I get the same error at the same place.  I have had sage on
> this computer before freebsd-9.2 and haven't been able to build it
> since.  Every time I notice a change in the sage port I try again.  I
> have tried about 4 times in the last week.  Before the last Makefile
> change in the port it got a lot farther and the error was during the
> building of the html documentation.
> I have tried MAKE_JOBS_UNSAFE and it gets farther.
> 
> I am using a Shuttle xpc with amd 64 and freebsd-9.2
> 
> uname -a FreeBSD 192.168.1.4 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898:
> Thu Sep 26 22:50:31 UTC 2013
> root at bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> Thanks for your help.

All the recent changes to the Makefile have been essentially cosmetic.
THe only change that might be at work is that I removed the
"NO_STAGE=yes" line.  That might have introduced some environment
variables that created the crash.  But it seems very unlikely.

Did you upgrade FreeBSD or other ports in the mean time?  Or maybe you
are using an old and buggy gcc47?

I should add that no-one has been able to get sage to build if the base
compiler is clang.  So updating to FreeBSD-10 will only make things
worse.  I am still using FreeBSD-8.

When you run it with MAKE_JOBS_UNSAFE, what error does it stop with?
Ironically it may not be getting as far.  When MAKE_JOBS_UNSAFE is not
set, it tries to build the subpackages in parallel.  So if it breaks on
more than one package, it is a bit random which package will cause the
break.

However, if you got as far as building the documentation, then the build
of the sage binaries is complete.  And then you can use sage to your
hearts content and get the docs using google.

In the meantime, I am looking into getting sage 6.2 working.  But that
is also giving me many problems.

Also, when replying, try to make sure that you send it to
stephen at freebsd.org.  If you send it to stephen at missouri.edu, it will
not get separated from all the other email I get from the FreeBSD
project, and I might not see it.  You are free to send it to both of
these email addresses, but make sure the stephen at freebsd.org email
address is included.


More information about the freebsd-ports mailing list