On Feb 4, 1:15 pm, dannychrastina <danny.chrast...@gmail.com> wrote:
> Hi,
<SNIP>
> > and like the likely culprit IMHO.
>
> Strange to me that it's only polybori which wouldn't build, and that I
> only ever saw gcc an g++ being called, and sage comes with its own
> fortran compiler so why would i go anywhere near ifort, but I did have
> a "__dso_handle" error which according
> tohttps://groups.google.com/group/sage-support/browse_thread/thread/497...
> is connected to having the Intel stuff. I'd never have figured this
> out.
Besides libcsage PolyBoRi is the only package in Sage that uses SCons.
And we are shipping somewhat outdated code and I had planned to
upgrade to SCons 1.0 every time I look at that ticket, but it hasn't
happened yet.
> > > I did "sage -sh" to use put sage's scons in the $PATH; my system
> > > doesn't have it.
>
> > > Anyway, sage builds now and works so thanks for all your help.
>
> > Well, thank you for sticking around and helping to debug this. These
> > kind of build bugs are always the most entertaining ones since my
> > initial reaction was "not another bug in those damn custom patched
> > binutils" and it is a real config issue in SCons.
>
> If there's any chance I can be helpful with anything else let me know.
No problem. In the long term we want to support the Intel compilers,
but as of now it is a low, low priority project, so no movement has
happened in that direction yet. It will also require some generic
overhaul of the build system I am planning to do in the next 3 months,
i.e. #2999-#3001.
> Best,
>
> Danny.
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
