octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #62715] ./configure could cache more values fo


From: Rik
Subject: [Octave-bug-tracker] [bug #62715] ./configure could cache more values for better performance
Date: Wed, 6 Jul 2022 18:12:03 -0400 (EDT)

URL:
  <https://savannah.gnu.org/bugs/?62715>

                 Summary: ./configure could cache more values for better
performance
                 Project: GNU Octave
               Submitter: rik5
               Submitted: Wed 06 Jul 2022 03:12:01 PM PDT
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Performance
                  Status: Confirmed
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: Any


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Wed 06 Jul 2022 03:12:01 PM PDT By: Rik <rik5>
Apparently the configure script used in building Octave is not caching as many
variables as it could.  I ran configure with the '-C' option to generate a
cache and then immediately re-ran configure.  I made a list of the items that
did not have "(cached)" next to them indicating that the value had been pulled
from the cache.  I'm attaching that list and also putting it in the text of
the bug report.  It shouldn't be too difficult to edit configure.ac or
m4/acinclude.m4 to make use of the AC_CACHE_CHECK macro.


checking whether build environment is sane... yes
checking whether UID '1000' is supported by ustar format... yes
checking whether GID '1000' is supported by ustar format... yes
checking whether make supports the include directive... yes (GNU style)
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking pkg-config is at least version 0.9.0... yes
checking for bison 3.0 or newer... 3.8.2, ok
checking for options to make reproducible archives with GNU tar... --owner=0
--group=0 --numeric-owner --sort=name
checking whether ln -s works... yes
checking for python... no
checking C++ compiler version number... 11.2.0
checking C compiler version number... 11.2.0
checking whether a usable Fortran compiler was found... yes
checking whether pthreads work with "-pthread" and "-lpthread"... yes
checking how to print strings... printf
checking for dlltool... no
checking for sysroot... no
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking how to run the C++ preprocessor... g++ -E
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
checking how to hardcode library paths into programs... immediate
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking whether the gfortran linker (/usr/bin/ld -m elf_x86_64) supports
shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking if sgemm_ is being linked in already... no
checking for sgemm_ in -framework vecLib... no
checking whether LSAME is called correctly from Fortran... yes
checking whether ISAMAX is called correctly from Fortran... yes
checking whether SDOT is called correctly from Fortran... yes
checking whether DDOT is called correctly from Fortran... yes
checking whether CDOTU is called correctly from Fortran... yes
checking whether ZDOTU is called correctly from Fortran... yes
checking BLAS library integer size... 4
checking whether POSIX threads API is available... yes
checking for ld... /usr/bin/ld -m elf_x86_64
checking for multithread API to use... posix
checking for MAP_ANONYMOUS... yes
checking for freetype2... yes
checking for FreeType2 version >= 9.03... yes
checking Qt version 5... checking for Qt5Core Qt5Gui Qt5Help Qt5Network
Qt5PrintSupport Qt5Xml... yes
checking for moc-qt5... no
checking for uic-qt5... no
checking for rcc-qt5... no
checking for lrelease-qt5... no
checking for qcollectiongenerator-qt5... no
checking for qhelpgenerator-qt5... no
checking whether SUNDIALS API provides the necessary functions... yes
checking for Java version... 11.0.15
checking for libjvm.so... /usr/lib/jvm/java-11-openjdk-amd64/lib/server
checking for include file <jni.h>...
/usr/lib/jvm/java-11-openjdk-amd64/include







    _______________________________________________________
File Attachments:


-------------------------------------------------------
Date: Wed 06 Jul 2022 03:12:01 PM PDT  Name: configure_cache.list  Size: 3KiB 
 By: rik5

<http://savannah.gnu.org/bugs/download.php?file_id=53403>

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62715>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]