Examining the giac-1.9.0.15po log file, the only error report occur when there is a attempt to load icas.o in line 4735.
There are a large number of warnings (~528 of 546 warnings) about deprecated pointer to a binary functions, typically
monomial.h:680:25: warning: 'template<class _Arg1, class _Arg2, class _Result> class std::pointer_to_binary_function' is deprecated [-Wdeprecated-declarations]
[spkg-install] 680 | const std::pointer_to_binary_function < const monomial<T> &, const monomial<T> &, bool> m_is_strictly_greater
[spkg-install] | ^~~~~~~~~~~~~~~~~~~~~~~~~~
There are configure warnings line 37 and 38 suggest use of --build, --host and --target switches and the presence of an unrecognized switch ----disable-maintainer-mode.
At line 317 config.status: WARNING: 'intl/Makefile.in' seems to ignore the --datarootdir setting
At line 319 config.status: WARNING: 'po/
Makefile.in.in' seems to ignore the --datarootdir setting
aroundline 3246 and again line 3580 there are a number of warnings like
global.cc: In function 'char* numworks_gettar(size_t&)':
[spkg-install] global.cc:1411:8: warning: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)' declared with attribute 'warn_unused_result' [-Wunused-result]
[spkg-install] 1411 | fread(buffer,numworks_maxtarsize,1,f);
line3828 a few like
pari.cc: In function 'giac::gen giac::in_pari(const gen&, const context*)':
[spkg-install] pari.cc:836:26: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
[spkg-install] 836 | argvec[k]= (GEN) v[j].val;
[spkg-install] | ^~~~~~~~~~~~~~
line 4736
[spkg-install] /opt/sage/sage-10.4/var/tmp/sage/build/giac-1.9.0.15p0/src/src/icas.cc:500:(.text+0x3925): warning: the use of `tmpnam' is dangerous, better use `mkstemp'
I wouldn't have expected the deprecation warnings to hva produced the proble. Unfortunately I am totally unfamiliar with the Sagemath and giac code
the config.log files have some errors re gcc which may be pertinent or may simply be checks
I don't see anything in the abovethat would have caused the load failure. ANy help appreciated.