Fwd: Re: Fwd: New Port: Security/liblurch & Security/Pidgin-lurch

2022-08-26 Thread Ronald Klop
Forgot to send the reply to the list. Van: Ronald Klop Datum: vrijdag, 26 augustus 2022 10:12 Aan: "Michael A. Oshin" Onderwerp: Re: Fwd: New Port: Security/liblurch & Security/Pidgin-lurch Mmm, lets take another look at it. From /usr/ports/Mk/bsd.ports.mk: "# Set these variables if your po

pkg builds on arm-v6 broken?

2022-08-26 Thread Ronald Klop
Hi, See https://pkg-status.freebsd.org/builds?type=package&all=1. Pkg builds for armv6 are broken for quite a while on the main branch. The build if ports-mgmt/pkg already fails. The error log indicates that it can't find the compiler "/nxb-bin/usr/bin/cc". Why does it use such a weird locatio

Ports with version numbers going backwards: emulators/libretro-ppsspp, emula...

2022-08-26 Thread portmgr
** The following ports have a version number that sorts before a previous one ** For many package tools to work correctly, it is of utmost importance that version numbers of a port form a monotonic increasing sequence over time. Refer to the FreeBSD Porter's Handbook, 'Package Naming Convention

Upgrade of gcc11-11.3.0 to gcc11-11.3.0_1 requires >= 4.8G /tmp

2022-08-26 Thread David Wolfskill
Saw this on a couple of laptops, each of which is configured to use a swap-backed tmpfs for /tmp -- started at 2G, which didn't work so well. Looks as if they are over the worst of it, and I've seen /tmp/get to 4.8G used -- in cdase this helps someone else avoid some of the hassle. (This was amd6

Re: Upgrade of gcc11-11.3.0 to gcc11-11.3.0_1 requires >= 4.8G /tmp

2022-08-26 Thread Jan Beich
David Wolfskill writes: > Saw this on a couple of laptops, each of which is configured to use a > swap-backed tmpfs for /tmp -- started at 2G, which didn't work so well. > > Looks as if they are over the worst of it, and I've seen /tmp/get to > 4.8G used -- in cdase this helps someone else avoid

Re: Upgrade of gcc11-11.3.0 to gcc11-11.3.0_1 requires >= 4.8G /tmp

2022-08-26 Thread David Wolfskill
On Fri, Aug 26, 2022 at 04:06:39PM +0200, Jan Beich wrote: > ... > Disable LTO_BOOTSTRAP port option or see > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265254 Good to know; thanks. In any case, one of the laptops finished OK (after having increased tmpfs to 8G). (I had needed to suspend

Re: pkg builds on arm-v6 broken?

2022-08-26 Thread Felix Palmen
* Ronald Klop [20220826 10:33]: > The build if ports-mgmt/pkg already fails. The error log indicates > that it can't find the compiler "/nxb-bin/usr/bin/cc". Why does it use > such a weird location for the compiler? Other architectures don't need > to do this. Th

Re: Fwd: New Port: Security/liblurch & Security/Pidgin-lurch

2022-08-26 Thread Felix Palmen
* Ronald Klop [20220826 19:07]: > On 8/26/22 17:26, Michael A. Oshin wrote: > > 2) Next, try use the GH repo (Preferred) and you will see the below error: That's not preferred. Only use it for projects that *don't* provide explicit distfiles. > > On a final note, what

Unmaintained FreeBSD ports which are out of date

2022-08-26 Thread portscout
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

New Port: Security/liblurch & Security/Pidgin-lurch

2022-08-26 Thread Michael A. Oshin
Thanks Ronald and other folks, It now builds and deploys into the right dir. I needed to get rid of the LD_CONFIG too. See the makefile at https://github.com/micadeyeye/freebsd-ports/blob/master/security/liblurch/Makefile . 1) However, how do I get rid of the below error? - ===> Generati

security/clamav: /ar/run on TMPFS renders the port broken by design

2022-08-26 Thread FreeBSD User
Hello, I'm referencing to Bug 259699 [2] and Bug 259585 [1]. Port security/clamav is without doubt for many of FreeBSD users an important piece of security software so I assume a widespread usage. It is also a not uncommon use case to use NanoBSD or any kind of low-memory-footprint installatio