Re: math/blas not compiling due to gcc7 error

[Connor McLaughlan <cont6pro3%gmail.com@localhost>]

On Thu, Aug 20, 2020 at 4:12 AM Jason Bacon <outpaddling%yahoo.com@localhost> wrote:
>
> This is a known issue that's solved by forcing the GCC package to build
> its own libgcc.
>
> In addition to that, I also make the GCC packages use pkgsrc binutils on
> my CentOS systems, since the CentOS "as" is old and doesn't understand
> some opcodes generated by newer GCC versions. The following is added to
> mk.conf automatically by auto-pkgsrc-setup (http://netbsd.org/~bacon/)
> to avoid these issues:
>
> .if exists(/etc/redhat-release) && !empty(PKGPATH:Mlang/gcc*)
>
> # RHEL systems may have an outdated "as" that cannot translate instructions
> # from current GCC code generators, so force pkgsrc binutils.
> CONFIGURE_ARGS+=        --with-gnu-as --with-as=${PREFIX}/bin/gas
> CONFIGURE_ARGS+=        --with-gnu-ld --with-ld=${PREFIX}/bin/gld
> BUILDLINK_DEPMETHOD.binutils=   full
> .  include "../../devel/binutils/buildlink3.mk"
>
> # pkgsrc gcc packages don't install libgcc_s on some platforms, to
> # avoid problems when mixing compiler versions.  This breaks our use
> # of pkgsrc gcc on EL.
> PKG_DEFAULT_OPTIONS+=   always-libgcc
> .endif  # RHEL
> .endif  # BSD_PKG_MK
>

Thanks for the advice. Unfortunately it didn't change anything in the
fortran build errors on sparc64.

What i find strange are the names of the compilers it states to search
during configuring. Possibly some parser component fail?

checking for sparc64--netbsd-xlC_r... c++
checking whether we are using the GNU C++ compiler... yes
checking whether c++ accepts -g... yes
checking whether C++ compiler c++ works... yes
configure: C++ compiler options are: -O2 -D_FORTIFY_SOURCE=2
-I/usr/pkg/include -I/usr/include   -DCOINUTILS_BUILD
configure: Trying to determine Fortran compiler name
checking for sparc64--netbsd-xlf_r... gfortran
checking for sparc64--netbsd-xlf_r... (cached) gfortran
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether gfortran accepts -g... yes

Shouldn't "xlC_r" be "g++" and "xlf_r" be "gfortran"?
So maybe the compiler is wrongly identified and used incorrectly later...

On linux it looks as i would expect it:

checking for x86_64-unknown-linux-g++... c++
checking whether we are using the GNU C++ compiler... yes
checking whether c++ accepts -g... yes
checking whether C++ compiler c++ works... yes
configure: C++ compiler options are: -O2 -D_FORTIFY_SOURCE=2
-I/usr/pkg/include -I/usr/include   -DCOINUTILS_BUILD
configure: Trying to determine Fortran compiler name
checking for x86_64-unknown-linux-gfortran... gfortran
checking for x86_64-unknown-linux-gfortran... (cached) gfortran
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether gfortran accepts -g... yes


Regards,
Connor