checking for fl32... no checking for af77... no checking for linker flag to name executables... configure: error: Could not determine flag to name executables See `config.log' for more details. !!! Please attach the following file when seeking support: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_hardened-science-20201120-101602 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-10.2.0 * /usr/lib/llvm/11 11.0.0 Available Python interpreters, in order of preference: [1] python3.9 [2] python3.8 (fallback) [3] python3.7 (fallback) [4] python2.7 (fallback) [5] pypy3 (fallback) Available Ruby profiles: [1] ruby25 (with Rubygems) [2] ruby26 (with Rubygems) [3] ruby27 (with Rubygems) * Available Rust versions: [1] rust-bin-1.48.0 * The following VMs are available for generation-2: *) AdoptOpenJDK 8.272_p10 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.8.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Mon Nov 30 07:35:28 AM UTC 2020 emerge -qpvO sci-libs/fox [ebuild N ] sci-libs/fox-4.1.2-r2 USE="dom fast sax wcml wkml wxml -debug -doc"
Created attachment 675892 [details] emerge-info.txt
Created attachment 675895 [details] emerge-history.txt
Created attachment 675898 [details] environment
Created attachment 675901 [details] etc.portage.tbz2
Created attachment 675904 [details] logs.tbz2
Created attachment 675907 [details] sci-libs:fox-4.1.2-r2:20201130-083430.log
Created attachment 675910 [details] temp.tbz2
Created attachment 711825 [details] ebuildtester emerge log ebuildtester emerge log
Created attachment 711828 [details] etc/portage
Created attachment 711831 [details] emerge --info
Created attachment 711834 [details] emerge-history.txt
Created attachment 711837 [details] emerge.log
Created attachment 712068 [details] build.log of hardened profile and without fortran flag
Created attachment 712071 [details] config.log of hardened profile and without fortran flag
Created attachment 712074 [details] emerge-history.txt of hardened profile and without fortran flag
Created attachment 712077 [details] emerge-info.txt of hardened profile and without fortran flag
Created attachment 712080 [details] enviroment of hardened profile and without fortran flag
Created attachment 712083 [details] etc/portage of hardened profile and without fortran flag
This bug requires a patch to the sci-libs/fox ebuild. This patch must require gcc to have the fortran use flag enabled. I managed to get this bug to repeat by switching to the hardened profile inside of an isolated gentoo stage 3 docker image. By default, the hardened profile disables the fortran use flag on gcc. When I tried to emerge fox within the hardened image without the fortran use flag, the bug repeated. The attached logs specified "hardened profile and without fortran flag" are from this attempt. Initially, I did not understand this bug report because when I initially emerged fox inside of a clean stage 3 isolated docker image, it compiled and installed corretly. My first attached logs are from this successful attempt. Furthermore, the comment by the reporter which indicated this bug report blocks "sys-devel/autoconf-2.70 issues" suggested it had something to do with autoconf. However, this is not the case and this bug report has nothing to do with autoconf. In addition, the reporter's emerge-info.txt shows that he has the latest version-2.69-r5-installed. Therefore I had to look closer at the log files. The reporter's config.log from logs.tbz2 shows specically that the configure phase failed at step "configure:1942: checking for Fortran compiler version". When I compared it to my successful emerge, the same step succeeded with message "checking for x86_64-pc-linux-gnu-gfortran... x86_64-pc-linux-gnu-gfortran". Therefore, I looked at which package supplied the gfortran compiler and realized that it was gcc. Upon closer inspection, I realized gcc had a use flag which enabled the fortran compiler. Additionally, when I inspected the reporter's use flags from the file emerge-info.txt, I saw that the USE variable lacked fortran while my USE flag had it enabled. I then took the steps mentioned in the second paragraph where I switched to a hardened profile and reproduced the bug. This is how I solved the bug. The next step is creating the patch I described in the first paragraph.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/proj/sci.git/commit/?id=4b888966f7c6ff0d86ba8b1802457d946c747bb3 commit 4b888966f7c6ff0d86ba8b1802457d946c747bb3 Author: Lucas Mitrak <lucas@lucasmitrak.com> AuthorDate: 2021-05-30 22:47:25 +0000 Commit: Andrew Ammerlaan <andrewammerlaan@gentoo.org> CommitDate: 2021-06-01 09:30:25 +0000 sci-libs/fox: add inherit fortran-2 Currently, sci-libs/fox does not require a fortran compiler to be installed. If sci-libs/fox is emerged without the fortran compiler, the configure phase will check for a fortran compiler, and the configure phase will fail. For example, the hardened profile disables the fortran USE flag in sys-devel/gcc, so sci-libs/fox will fail. With this commit, sci-libs/fox will require a fortran compiler to be installed. Without this commit, sci-libs/fox will fail on any system which does not have the fortran compiler, which by default is all hardened profiles. This commit was tested in a docker image with dev-util/ebuildtester. This commit was written, tested, and submitted by Lucas Mitrak. Closes: https://bugs.gentoo.org/757771 Signed-off-by: Lucas Mitrak <lucas@lucasmitrak.com> Closes: https://github.com/gentoo/sci/pull/1083 Signed-off-by: Andrew Ammerlaan <andrewammerlaan@gentoo.org> sci-libs/fox/fox-4.1.2-r2.ebuild | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) https://gitweb.gentoo.org/proj/sci.git/commit/?id=8968649e1fa253daf020d91607ad8da1cb53f218 commit 8968649e1fa253daf020d91607ad8da1cb53f218 Author: Lucas Mitrak <lucas@lucasmitrak.com> AuthorDate: 2021-05-29 04:11:22 +0000 Commit: Andrew Ammerlaan <andrewammerlaan@gentoo.org> CommitDate: 2021-06-01 09:30:12 +0000 sci-libs/fox: DEPEND of fortran USE flag for gcc * add a DEPEND which will require the fortran USE flag in sys-devel/gcc Currently, sci-libs/fox does not require sys-devel/gcc to have the fortran USE flag set. If sci-libs/fox is emerged without the fortran USE flag, the configure phase will check for a fortran compiler, and the configure phase will fail. By default, the hardened profile disables the fortran USE flag in sys-devel/gcc, so sci-libs/fox will fail. With this commit, sci-libs/fox depends on sys-devel/gcc having a the fortran USE flag set. Without this commit, sci-libs/fox will fail on any system which does not have the fortran USE flag in sys-devel/gcc, which by default is all hardened profiles. This commit was tested in a docker image with dev-util/ebuildtester. This commit was written, tested, and submitted by Lucas Mitrak. Closes: https://bugs.gentoo.org/757771 Signed-off-by: Lucas Mitrak <lucas@lucasmitrak.com> Signed-off-by: Andrew Ammerlaan <andrewammerlaan@gentoo.org> sci-libs/fox/fox-4.1.2-r2.ebuild | 2 ++ 1 file changed, 2 insertions(+)
