| Summary: | sci-libs/qd-2.3.22 - fpu.cpp: error: variable or field FC_FUNC_ declared void | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
| Component: | Current packages | Assignee: | Gentoo Science Related Packages <sci> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | base-system, mjo, sam |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://lists.gnu.org/archive/html/autoconf/2021-08/msg00000.html | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 732648 | ||
| Attachments: |
emerge-info.txt
emerge-history.txt environment etc.portage.tar.bz2 logs.tar.bz2 sci-libs:qd-2.3.22:20210310-063804.log temp.tar.bz2 emerge-info.txt emerge-history.txt environment etc.portage.tar.bz2 logs.tar.bz2 sci-libs:qd-2.3.22:20210804-160509.log temp.tar.bz2 |
||
Created attachment 690471 [details]
emerge-info.txt
Created attachment 690474 [details]
emerge-history.txt
Created attachment 690477 [details]
environment
Created attachment 690480 [details]
etc.portage.tar.bz2
Created attachment 690483 [details]
logs.tar.bz2
Created attachment 690486 [details]
sci-libs:qd-2.3.22:20210310-063804.log
Created attachment 690489 [details]
temp.tar.bz2
FWIW I tried to reproduce this and couldn't, even with the same USE flags (manually enabling fma3 on a system without it doesn't seem to hurt anything). It emerged here at the new tinderbox at few images - so I'd close this bug b/c the old hardware and their images are gone. appeared recently at the tinderbox image 17.1_desktop_gnome-j3-20210729-194103 Created attachment 730150 [details]
emerge-info.txt
Created attachment 730152 [details]
emerge-history.txt
Created attachment 730154 [details]
environment
Created attachment 730156 [details]
etc.portage.tar.bz2
Created attachment 730158 [details]
logs.tar.bz2
Created attachment 730160 [details]
sci-libs:qd-2.3.22:20210804-160509.log
Created attachment 730162 [details]
temp.tar.bz2
Ok, I've found the problem at least. The FC_FUNC macro and its underscore counterpart are supposed to name-mangle C functions to be linked with fortran. But in this case, it can't figure out how to do that: configure:8421: WARNING: unknown Fortran name-mangling scheme So, nothing gets defined in config.h, and the macro winds up "void". Ah, it's because we're using eautoreconf, and the fortran name-mangling doesn't seem to work the same in autoconf-2.71. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=71595d02b69ce844e12e2344531f6af9e437c4d1 commit 71595d02b69ce844e12e2344531f6af9e437c4d1 Author: Michael Orlitzky <mjo@gentoo.org> AuthorDate: 2021-08-05 00:00:00 +0000 Commit: Michael Orlitzky <mjo@gentoo.org> CommitDate: 2021-08-05 00:02:38 +0000 sci-libs/qd: new revision that works with autoconf-2.71. In this -r1, I've added a patch that solves bug 775215 by not setting CC=$CXX during ./configure. At the same time, I've refactored our other build system patch into a series of smaller patches (with explanatory commit messages) that can be sent upstream. Finally, I've removed USE=static-libs support from the ebuild. It doesn't do anyone any good. Closes: https://bugs.gentoo.org/775215 Package-Manager: Portage-3.0.20, Repoman-3.0.2 Signed-off-by: Michael Orlitzky <mjo@gentoo.org> ...gure.ac-update-QD_PATCH_VERSION-to-2.3.22.patch | 31 +++++++ ...c-replace-AM_CONFIG_HEADER-with-AC_CONFIG.patch | 34 +++++++ ...e.ac-replace-AC_PROG_LIBTOOL-with-LT_INIT.patch | 37 ++++++++ ....ac-fix-syntax-of-all-AC_ARG_ENABLE-calls.patch | 100 ++++++++++++++++++++ ...efile.am-fix-underlinking-of-libqdmod-and.patch | 35 +++++++ ...006-configure.ac-remove-enable-debug-flag.patch | 102 +++++++++++++++++++++ ...0007-config.h.in-remove-QD_DEBUG-constant.patch | 29 ++++++ ...c-don-t-assume-that-O2-is-a-valid-compile.patch | 47 ++++++++++ .../0009-configure.ac-don-t-set-CC-to-CXX.patch | 46 ++++++++++ ...c-don-t-manually-search-for-compiler-name.patch | 81 ++++++++++++++++ .../0011-qd-config.in-remove-REQ_CXXFLAGS.patch | 27 ++++++ ...figure.ac-remove-the-enable-warnings-flag.patch | 55 +++++++++++ sci-libs/qd/qd-2.3.22-r1.ebuild | 61 ++++++++++++ 13 files changed, 685 insertions(+) For completeness, reported to autoconf as https://lists.gnu.org/archive/html/autoconf/2021-08/msg00000.html by mjo. |
/bin/sh ../libtool --tag=CXX --mode=compile x86_64-pc-linux-gnu-c++ -DHAVE_CONFIG_H -I.. -I../include -I../include -O2 -pipe -march=native -fno-diagnostics-color -Wall -c -o fpu.lo fpu.cpp libtool: compile: x86_64-pc-linux-gnu-c++ -DHAVE_CONFIG_H -I.. -I../include -I../include -O2 -pipe -march=native -fno-diagnostics-color -Wall -c fpu.cpp -fPIC -DPIC -o .libs/fpu.o fpu.cpp:110:25: error: variable or field ‘FC_FUNC_’ declared void 110 | #define f_fpu_fix_start FC_FUNC_(f_fpu_fix_start, F_FPU_FIX_START) | ^~~~~~~~ fpu.cpp:113:6: note: in expansion of macro ‘f_fpu_fix_start’ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_systemd-20210303-131616 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-10.2.0 * clang version 11.1.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/11/bin /usr/lib/llvm/11 11.1.0 Python 3.8.8 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby27 (with Rubygems) * Available Rust versions: [1] rust-1.50.0 * The following VMs are available for generation-2: *) AdoptOpenJDK 8.282_p08 [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 Wed Mar 10 06:20:56 UTC 2021 emerge -qpvO sci-libs/qd [ebuild N ] sci-libs/qd-2.3.22 USE="fortran -doc -static-libs" CPU_FLAGS_X86="fma3 -fma4"