Good thing you made me check. I didn't actually include gfortran into the
build environment, so its saying `checking for gfortran... no`.
On Tue, Oct 30, 2018 at 4:48 PM Dima Pasechnik wrote:
> Well, does ./configure outputs something like
>
> .
> gcc-7.2.0 not installed (configure check
Well, does ./configure outputs something like
.
gcc-7.2.0 not installed (configure check)
gdb-8.2
gf2x-1.2.p0
gfan-0.6.2.p0
gfortran-7.2.0 not installed (configure check)
...
If so it should not build gfortran (unless you have SAGE_INSTALL_GCC
set to yes for some reason...
No, but nixos doesn't follow FHS[0], so I am using linux namespaces (more
precisely this[1]) to build sage in an environment where all the build
dependencies are at their FHS locations. So sage is using nixos's gfortran,
the namespaces are just so it can find it where it expects it. This worked
On Tue, Oct 30, 2018 at 4:29 PM Timo Kaufmann wrote:
>
> Its a bit of a complicated case, but I'm not using anaconda. I'm using nixos
> and a special build environment that uses linux namespaces to make sure all
> the dependencies are in the location sage expects them. I'm using that to
> build
Its a bit of a complicated case, but I'm not using anaconda. I'm using
nixos and a special build environment that uses linux namespaces to make
sure all the dependencies are in the location sage expects them. I'm using
that to build sage-the-distribution when testing because that won't build
na
On Tue, Oct 30, 2018 at 4:01 PM Timo Kaufmann wrote:
>
> I just had the same issue. Why do you think "several versions of gfortran
> guts" are the issue? How does sage find gfortran / why does it get confused?
>
What's the OS you are using? How do you install Sage?
I suspect it's a conflict with
I just had the same issue. Why do you think "several versions of gfortran
guts" are the issue? How does sage find gfortran / why does it get confused?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receivi
