Re: Why lang/gcc14-devel builds are failing on the build servers: needs USES= compiler:c++14-lang (or higher) instead of compiler:c++11-lang

On Thursday, February 8th, 2024 at 18:11, Mark Millard wrote: > > > > > On Feb 7, 2024, at 23:40, Nuno Teixeira edua...@freebsd.org wrote: > > > USES compiler is somehow deprecated as clang and gcc on base and ports > > supports capable compiler described in handbook: > > https://docs.free

Re: lang/gcc* and MULTILIB: arm64 (aarch64) is never set up, even for main

On Thursday, February 8th, 2024 at 07:12, Mark Millard wrote: > > > The lang/gcc*/Makefile codes like: > > .if exists(/usr/lib32/libc.so) > OPTIONS_DEFINE_amd64+= MULTILIB > OPTIONS_DEFAULT_amd64+= MULTILIB > OPTIONS_DEFINE_powerpc64+= MULTILIB > #OPTIONS_DEFAULT_powerpc64+= MULTILIB # > htt

Re: port shares same binary and manual names with base ztest (ZFS)

Hello! I've e-mailed upstream about it and this is getting interesting. I will paste complete reply here. ## Hello Nuno, Nuno Teixeira wrote: > I'm about to maintain Zutils FreeBSD port ( > https://www.freshports.org/archivers/zutils/ ) and I'm dealing with > conflicts with base gzip and ZFS

Re: lang/gcc* and MULTILIB: arm64 (aarch64) is never set up, even for main

On Fri, 9 Feb 2024, Lorenzo Salvadore wrote: >> [lang/gcc*] never adds MULTILIB for aarch64 (arm64). >> >> But these days arm64 (aarch64) has lib32 support: >> 14.0-RELEASE has it and main [so: 15] has it. Does anyone use this, though? (It's not like FreeBSD provides proper bi-arch support with

Re: lang/gcc* and MULTILIB: arm64 (aarch64) is never set up, even for main

On Feb 9, 2024, at 13:35, Gerald Pfeifer wrote: > On Fri, 9 Feb 2024, Lorenzo Salvadore wrote: >>> [lang/gcc*] never adds MULTILIB for aarch64 (arm64). >>> >>> But these days arm64 (aarch64) has lib32 support: >>> 14.0-RELEASE has it and main [so: 15] has it. > > Does anyone use this, though? (

Re: Subpackages: Update

Hello. I am delayed in many things on my end, so I don't have time for this kind of thing :) But... I think the following conversions need to be modified to work correctly. PKGNAME -> port origin -> PKGNAME For example, alsa-plugins-pulseaudio -> audio/alsa-plugins -> alsa-plugins-... Current

Re: port shares same binary and manual names with base ztest (ZFS)

Thanks. The last sentence in the quoted comment looks similar to my suspition (looks to be from the same background). I recently found sysutils/rust-coreutils [4] (not actually installed/used) and found it uses uu-* as their command names to avoid conflicting. Introducing conflict is an easy way

Unmaintained FreeBSD ports which are out of date

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