I think there are two choices. One worked for me, just compile the last 
develop version. For the other one, there are some PR that can be applied, 
but I am not sure if it will work.

El martes, 11 de junio de 2024 a las 19:42:48 UTC+2, Todd Hesla escribió:

> Hi,
>
> I'm trying to build Sagemath 10.3 from the source tarball in my new Fedora 
> 40
> system (details below), but am experiencing a problem with "make" not 
> noticing
> existing packages that are already installed on my system:
>
>   gcc-14.1.1-4
>   openssl-3.2.1-2
>
> Instead, "make" built gcc-12.2.0 from the included source (which finished
> successfully after many hours), and it tried to build openssl-3.0.12 from 
> the
> included source, but this aborted with an error (see the attached log 
> file).
>
> Is there any way to force "make" to use my existing "gcc" and "openssl"
> packages, rather than trying to compile them from source (unsuccessfully 
> in the
> case of openssl)?  This would save many hours of compiling of "gcc" from 
> source,
> and would presumably circumvent the error building "openssl" from source.
>
> I've attached the log files:
>
>   /usr/local/sage/sage-10.3/logs/pkgs/openssl-3.0.12.log
>   /usr/local/sage/sage-10.3/config.log
>
> Regards,
>
> Todd Hesla
> Minneapolis MN
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> System details:
>
>   Operating System: Fedora Linux 40
>   KDE Plasma Version: 6.0.5
>   KDE Frameworks Version: 6.2.0
>   Qt Version: 6.7.1
>   Kernel Version: 6.8.11-300.fc40.x86_64 (64-bit)
>   Graphics Platform: Wayland
>   Processors: 8 x Intel Core i7 CPU 920 @ 2.67GHz
>   Memory: 5.8 GiB of RAM
>   Graphics Processor: llvmpipe
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a6200f54-8074-43a7-84ef-7dd9e3984ca2n%40googlegroups.com.

Reply via email to