Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 15 Dec 2018 19:18:05 -0800
From:      Kevin Oberman <rkoberman@gmail.com>
To:        Jan Beich <jbeich@freebsd.org>
Cc:        "ports@FreeBSD.org" <ports@freebsd.org>, Gerald Pfeifer <gerald@pfeifer.com>
Subject:   Re: Massive PORTREVSION bump for gcc8
Message-ID:  <CAN6yY1vRgKTRs=S6hyjmv1LDtK=kwqkvxbpAoghQs8H2u5UFKw@mail.gmail.com>
In-Reply-To: <r2ei-jj6g-wny@FreeBSD.org>
References:  <CAN6yY1tfyOieHGKhD7XRg4ip0yz4mQx0%2BDpoT_ufyjCT0P7dZw@mail.gmail.com> <r2ei-jj6g-wny@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 15, 2018, 6:32 PM Jan Beich <jbeich@freebsd.org wrote:

> Kevin Oberman <rkoberman@gmail.com> writes:
>
> > This morning the PORTREVISION on at least hundreds of ports was bumped
> > because gcc8 was declared as the "canonical" version. As a result, I will
> > have about 300 ports to rebuild which will take many hours.
> > Why?
>
> USE_GCC embeds RPATH during build where libgcc_s, libgfortran,
> libstdc++, etc. can be found. Mixing different versions (e.g., libgcc_s
> from lang/gcc7 with libgfortran from lang/gcc8) may destabilize
> runtime. Rebuild is necessary to ensure the consistent state, mainly for
> portmaster/portupgrade that don't rebuild every time dependency is
> upgraded.
>
> USE_GCC is implicitly set by USES=compiler on architectures stuck with
> GCC in base i.e., powerpc*/sparc64/mips*/riscv*.
>
> [..]


Thanks, Jan. I must admit that I did not think of this, though I should
have.

Sorry about the noise.
--
Kevin Oberman, Retired Network Engineer



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1vRgKTRs=S6hyjmv1LDtK=kwqkvxbpAoghQs8H2u5UFKw>