Error building sage package-gfortran

46 views
Skip to first unread message

Arnald Dutta

unread,
Mar 5, 2020, 12:40:51 AM3/5/20
to sage-devel
Hi,
I am facing problem with gfortran-9.2.0 while building sage.

Error prompted on the terminal after trying to build sage :

Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all-build'):

* package: gfortran-9.2.0
  log file: /home/arnald/sage-9.0/logs/pkgs/gfortran-9.2.0.log
  build directory: /home/arnald/sage-9.0/local/var/tmp/sage/build/gfortran-9.2.0

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

Makefile:31: recipe for target 'all-build' failed
make[1]: *** [all-build] Error 1
make[1]: Leaving directory '/home/arnald/sage-9.0'
Makefile:16: recipe for target 'build' failed
make: *** [build] Error 2

I have attached gfortran-9.2.0.log and config.log.
Thanks in advance.
gfortran-9.2.0.log
config.log

Dima Pasechnik

unread,
Mar 5, 2020, 2:50:57 AM3/5/20
to sage-devel
It looks as if you didn't have gfortran installed.
Any reason for that?

--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/86632ba7-bc85-4e19-ad18-6a6dda5320f7%40googlegroups.com.

Arnald Dutta

unread,
Mar 5, 2020, 2:22:52 PM3/5/20
to sage-devel
I was facing issues while installing gfortran. I reinstalled all the packages and ran all the commands as instructed in the FAQ: building Sage on debian or ubuntu to build sage.
And now it is working fine.
Thank you, sir
To unsubscribe from this group and stop receiving emails from it, send an email to sage-...@googlegroups.com.

Matthias Koeppe

unread,
Mar 5, 2020, 3:28:25 PM3/5/20
to sage-devel
This looks like an interaction with an Anaconda installation -- perhaps a conda environment was active while "configure" ran but not while "make" ran.
Reply all
Reply to author
Forward
0 new messages