On Wed, 19 Jul 2017 22:50:04 +0200 (CEST)
Gerald Pfeifer wrote:
> On Fri, 14 Apr 2017, Alexander Kabaev wrote:
> > it was suggested multiple times that the whole fixinc step is
> > ultimately harmful and serves no useful purpose and probably should
> > be disabled in built
On Fri, 14 Apr 2017, Alexander Kabaev wrote:
> it was suggested multiple times that the whole fixinc step is
> ultimately harmful and serves no useful purpose and probably should be
> disabled in built packages outright. Is there a reason not to do it?
> Even Redhat appears to do the slimming in
emulators/virtualbox-ose is failing on head for some time and I found ar
is causing the trouble. The earliest failures noticed by package
builders are here:
http://docs.freebsd.org/cgi/mid.cgi?201706170249.v5H2nUVZ039286
http://docs.freebsd.org/cgi/mid.cgi?201706170238.v5H2cZTZ054493
The core
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
--- Comment #6 from commit-h...@freebsd.org ---
A commit references this bug:
Author: dim
Date: Wed Jul 19 18:22:32 UTC 2017
New revision: 321222
URL: https://svnweb.freebsd.org/changeset/base/321222
Log:
Pull in r229281 from upstream
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
--- Comment #5 from Dimitry Andric ---
I'll merge libc++ r229281 into stable/10 later today, at least it'll appear in
10.4-RELEASE then. Jan, is it worth bumping __FreeBSD_version for this?
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
--- Comment #4 from Gerald Pfeifer ---
(In reply to Jan Beich from comment #2)
> Alternatives are locking the ports to USE_GCC < 6 (if gerald is OK)
> or laying on BROKEN_FreeBSD_10 deathbed.
I prefer the latter,