Dear port maintainers,
The portscout new distfile checker has detected that one or more
unmaintained 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. Please consider also adopting this po
Note, more recent process creations towards top, older ones towards bottom:
PID JID USERNAMEPRI NICE SIZE RES STATEC TIME CPU
COMMAND
. .
3369319 root 680 6524Ki3252Ki wait 3 0:00 0.00%
/usr/bin/make -C /usr/ports/lang/gcc13 build
33692
Did you get binaries? If so, install manually.
Best regards,
Jussi Korkala
> On 20. Mar 2024, at 22.16, Michael Grimm wrote:
>
> Hi
>
> Disclaimer:
>
> I am trying to create a new port (knot-resolver-current) developed under
> Linux upstream. A so-called manager functionality is brand new
Gleb Popov wrote:
>
> On Wed, Mar 20, 2024 at 11:16 PM Michael Grimm wrote:
>> Compilation fails:
>>
>> cc -pthread -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG
>> -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -fPIC
>> -I/usr/local/include/python3.9 -c
>> knot_res
On 21/03/24 13:35, Martin Waschbüsch wrote:
Hi all,
if a committer could kindly look at this PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277682
Many thanks!
Martin
Took
Hi all,
if a committer could kindly look at this PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277682
Many thanks!
Martin
On Wed, Mar 20, 2024 at 11:16 PM Michael Grimm wrote:
>
> Hi
>
> Disclaimer:
>
> I am trying to create a new port (knot-resolver-current) developed under
> Linux upstream. A so-called manager functionality is brand new in comparison
> to the previous knot-resolver. The corresponding git reposito
