turning on warnings during a recompile?

[Randall]

Goal:

Turn on visibility of compiler warnings during compile phase, inside a %make build command run

I did a change in one pyx unit and then ran the

% make build

command and the following was logged:

***********************************************
make[2]: Entering directory '/home/owner/sage/sage-9.5/build/make'
make --no-print-directory /home/owner/sage/sage-9.5/local/var/lib/sage/installed/.dummy
make[3]: '/home/owner/sage/sage-9.5/local/var/lib/sage/installed/.dummy' is up to date.
make --no-print-directory /home/owner/sage/sage-9.5/local/var/lib/sage/installed/.dummy
make[3]: '/home/owner/sage/sage-9.5/local/var/lib/sage/installed/.dummy' is up to date.
make --no-print-directory /home/owner/sage/sage-9.5/local/var/lib/sage/installed/.dummy
make[3]: '/home/owner/sage/sage-9.5/local/var/lib/sage/installed/.dummy' is up to date.
make --no-print-directory /home/owner/sage/sage-9.5/local/var/lib/sage/installed/.dummy
make[3]: '/home/owner/sage/sage-9.5/local/var/lib/sage/installed/.dummy' is up to date.
make --no-print-directory all-sage
make --no-print-directory sagelib-SAGE_VENV-no-deps
[sagelib-9.5.rc3] Discovering Python/Cython source code....
[sagelib-9.5.rc3] distributions = ['']
[sagelib-9.5.rc3] Discovered Python/Cython sources, time: 1.94 seconds.
[sagelib-9.5.rc3] running build
[sagelib-9.5.rc3] Generating auto-generated sources
[sagelib-9.5.rc3] Building interpreters for fast_callable
[sagelib-9.5.rc3] running build_cython
[sagelib-9.5.rc3] Enabling Cython debugging support
[sagelib-9.5.rc3] Compiling sage/algebras/letterplace/free_algebra_letterplace.pyx because it changed.
[sagelib-9.5.rc3] [1/1] Cythonizing sage/algebras/letterplace/free_algebra_letterplace.pyx
[sagelib-9.5.rc3] Executing 1 command (using 1 thread)
[sagelib-9.5.rc3] [1/1] Time to execute 1 command: 9.62 seconds.
[sagelib-9.5.rc3] Total time spent compiling C/C++ extensions: 9.78 seconds.
[sagelib-9.5.rc3] warning: no files found matching '*.hh' anywhere in distribution
[sagelib-9.5.rc3] warning: no files found matching '*.inc' anywhere in distribution
[sagelib-9.5.rc3] no previously-included directories found matching '.tox'
[sagelib-9.5.rc3] warning: no directories found matching 'sage/libs/gap/test'
[sagelib-9.5.rc3] no previously-included directories found matching 'sage_setup'
[sagelib-9.5.rc3] Cleaning up stale file: /home/owner/sage/sage-9.5/local/var/lib/sage/venv-python3.9.9/lib/py
thon3.9/site-packages/sage/ext_data/nbconvert/__pycache__/postprocess.cpython-39.pyc
[sagelib-9.5.rc3]  
[sagelib-9.5.rc3] real  0m32.475s
[sagelib-9.5.rc3] user  0m11.840s
[sagelib-9.5.rc3] sys   0m1.311s
make[2]: Leaving directory '/home/owner/sage/sage-9.5/build/make'

real    0m33.560s
user    0m12.155s
sys     0m1.342s
Sage build/upgrade complete!
make[1]: Leaving directory '/home/owner/sage/sage-9.5'

-------------------------

Okay, but I would expect and I need to see any warnings in the C++ compile, so how is exposure given to these warnings and messages during that compile? During a main build taking several hours, during the cynthonizing phase, many lines of compiler warnings are printed. I need to see them again each time one file is changed.

Randall

[Michael Orlitzky]

On Sat, 2022-01-22 at 14:09 -0800, Randall wrote:
> [sagelib-9.5.rc3] Executing 1 command (using 1 thread)
> [sagelib-9.5.rc3] [1/1] Time to execute 1 command: 9.62 seconds.

Between these two lines, the C or C++ compilation takes place. If you
don't see any warnings, there weren't any.

It's a crime that you can't see the actual compile/link commands, but I
don't know how to change that.