tech-pkg archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Can we make gfortran the default Fortran?
On 26 December 2017 at 21:10, Jason Bacon <bacon4000%gmail.com@localhost> wrote:
>
> As a prototype for the upcoming changes Greg mentioned, I've been avoiding
> this whole issue on CentOS using the following combo in mk.conf. Basically
> require the same pkgsrc gcc for everything except gcc and its dependencies.
> This should work for other platforms as long as bootstrap uses GCC. There
> are unresolved issues on clang-based systems.
>
> I'm moving to gcc5 now, as the impact is only a few dozen broken packages.
> Using gcc6 still causes hundreds of added failures.
>
> The exemptions below cover gcc4x, 5, and 6. Hence both bzip2 and xz, which
> are deps for different gcc packages. You should only need to change the gcc
> package name to switch between versions.
>
> PKGSRC_FORTRAN= gfortran
>
> .if \
> empty(PKGPATH:Marchivers/bzip2) && \
> empty(PKGPATH:Marchivers/pax) && \
> empty(PKGPATH:Marchivers/xz) && \
> empty(PKGPATH:Mconverters/help2man) && \
> empty(PKGPATH:Mconverters/p5-Unicode-EastAsianWidth) && \
> empty(PKGPATH:Mdevel/autoconf) && \
> empty(PKGPATH:Mdevel/gettext-lib) && \
> empty(PKGPATH:Mdevel/gettext-tools) && \
> empty(PKGPATH:Mdevel/gmp) && \
> empty(PKGPATH:Mdevel/gtexinfo) && \
> empty(PKGPATH:Mdevel/libtool-base) && \
> empty(PKGPATH:Mdevel/m4) && \
> empty(PKGPATH:Mdevel/ncurses) && \
> empty(PKGPATH:Mdevel/nbpatch) && \
> empty(PKGPATH:Mdevel/p5-gettext) && \
> empty(PKGPATH:Mlang/gcc5) && \
> empty(PKGPATH:Mlang/gcc5-libs) && \
> empty(PKGPATH:Mlang/perl5) && \
> empty(PKGPATH:Mmath/cloog) && \
> empty(PKGPATH:Mmath/isl) && \
> empty(PKGPATH:Mmath/mpcomplex) && \
> empty(PKGPATH:Mmath/mpfr) && \
> empty(PKGPATH:Mmisc/p5-Locale-libintl) && \
> empty(PKGPATH:Mpkgtools/cwrappers) && \
> empty(PKGPATH:Mpkgtools/digest) && \
> empty(PKGPATH:Mpkgtools/pkg_install-info) && \
> empty(PKGPATH:Msysutils/checkperms) && \
> empty(PKGPATH:Mtextproc/p5-Text-Unidecode)
>
> GCC_REQD+=4.8
>
> .endif # GCC_REQD
Possibly related thought - rather than hand curating sets of PKGPATH
checks, would something of the form
- 'set _BUILDING_COMPILER' when building the compiler
- Only set GCC_REQD if _BUILDING_COMPILER is unset
work?
Home |
Main Index |
Thread Index |
Old Index