Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
# pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
Updating zs64 repository catalogue...
zs64 repository is up to date.
All repositories are up to date.
Checking for upgrades (431 candidates): 100%
Processing candidates (431 candidates): 100%
Checking integrity
Upgraded my -CURRENT system today, and httpd dies on a SIGSEGV, and I can't
build
print/texinfo.
anyone else having issues building texinfo on -CURRENT?
panic: bad free, ->next->prev=80509aaa0, header=80509aaa0,
->prev->next=a5a5a5a5a5a50020 at ../tp/Texinfo/Parser.pm line 3907.
panic: bad free
Hi all,
Testing the latest www/gohugo port so I can submit a patch. I’ve tested the
port with the following:
> poudriere bulk -f pkglist -p local -tC -j 12Ci386
Where pkglist contains a single line with “www/gohugo”. For all other jails
(10.3 and 11.0 i386 and amd64, and 12.0-CURRENT amd64)
> On 26 Jun, 2017, at 7:54, Miroslav Lachman <000.f...@quip.cz> wrote:
>
> Vanilla Hsu wrote on 2017/05/16 01:37:
>> I got the same problem too, but after update to 2.5-rc2, all issues gone.
>>
>> maybe you can try to update to 2.5-rc2 (2.5 not yet released) by yourself.
>
> Opening this again.
[It looks like USE_GCC=any is broken and leads to system-clang use.]
On 2017-Jun-29, at 5:58 PM, Gerald Pfeifer wrote:
> Am 29. Juni 2017 18:55:59 GMT+08:00 schrieb Mark Millard
> :
>> I'm not currently set up to run more than head on
>> any of amd64, powerpc64, powerpc, aarch64, or armv6/7
>>
[Looks like output from "make test-gcc" is appropriate,
so I'm adding such.]
On 2017-Jul-2, at 7:53 PM, Mark Millard wrote:
> [It looks like USE_GCC=any is broken and leads to system-clang use.]
>
> On 2017-Jun-29, at 5:58 PM, Gerald Pfeifer wrote:
>
>> Am 29. Juni 2017 18:55:59 GMT+08:00 sch
[More on the behavior: it is more complicated than
previously shown.]
On 2017-Jul-2, at 8:12 PM, Mark Millard wrote:
> [Looks like output from "make test-gcc" is appropriate,
> so I'm adding such.]
>
> On 2017-Jul-2, at 7:53 PM, Mark Millard wrote:
>
>> [It looks like USE_GCC=any is broken an
