Re: We need to do something about build times

Hi! > The build times have gone up to the point where they are unsustainable. Yes. Thank you for the great problem statement! -- p...@freebsd.org +49 171 3101372 Now what ?

output of RUN_DEPENDS changes unexpectedly

Hello, I noticed an anomaly today. Watch how the output of make -V RUN_DEPENDS changes for tomcat-devel as we move through the tree. This is a fresh checkout of ports [18:40 empty dan /usr/ports] % cd www/tomcat-devel [18:41 empty dan /usr/ports/www/tomcat-devel] % make -V RUN_DEPENDS

Re: We need to do something about build times

> > From: Robert Clausecker > Date: Oct 24, 2023, 12:12:13 PM > To: > Subject: We need to do something about build times > > > The build times have gone up to the point where they are unsustainable. > Frequent updates to key ports (like llvm*, rust,

Re: FreeBSD 13 + CertBot + OpenSSL 3 - status?

On 24/10/2023 18:24, Matthew Seaman wrote: On 24/10/2023 13:54, DutchDaemon - FreeBSD Forums Administrator wrote: Does anyone in 'port land' know what the current developments are wrt CertBot (or py-crypto under its hood)? CertBot is happily compiling against OpenSSL 3 from ports, but when

Re: We need to do something about build times

Hello, I am the maintainer of the GCC ports and thus I reply about this particular topic. Disabling LTO_BOOTSTRAP option by default has already been done for the devel ports on the i386, amd64 and aarch64 architectures (so for all tier 1 platforms):

Re: We need to do something about build times

Hi Lorenzo, Am Tue, Oct 24, 2023 at 08:11:29PM + schrieb Lorenzo Salvadore: > Disabling LTO_BOOTSTRAP option by default has > already been done for the devel ports on the i386, amd64 > and aarch64 architectures (so for all tier 1 platforms): >

We need to do something about build times

The build times have gone up to the point where they are unsustainable. Frequent updates to key ports (like llvm*, rust, gcc*) make it so that basically every time I prepare a new batch of commits, I have to rebuild a variety of toolchain ports across 8 jails (amd64/i386/arm64/armv7 each for

Re: We need to do something about build times

I'll reply to LLVM specific suggestions On Tue, Oct 24, 2023 at 09:12:13PM +0200, Robert Clausecker wrote: > - untangle some of the dependencies so that less ports may trigger >rebuilds of critical ports. For example, llvm docs could be moved to >separate ports so that updates in the

Re: output of RUN_DEPENDS changes unexpectedly

Hello. I don't know what it is, but as a maintainer but not a committer, I don't use features related to git branch. Changes are made directly to files that are checkout-ed, and when updates are made by pull, etc., stash takes care of everything. git stash push --all -- :/ git pull --autostash

Another morning lost to bad ports choices (perl upgrade, plus postgres)

All, I’ve lost another morning to a bad choice made by ports/pkg. Maybe this is a dumb question/rant, but recently, a routine pkg upgrade of the dayjob’s RT VM (which included an upgrade to perl) decided to leave me with no ability to connect. After following the rabbit hole, I hit a database

Avoiding OOM for armv7 ports on arm64

Greetings, One thing that bugged me for quite a while is that armv7 tasks on arm64 hosts (common case for cross-building ports) can seemingly only allocate 2 GB of memory despite having access to a full 32 bit virtual address space, which should give 4 GB of memory to play around with. This

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

Re: We need to do something about build times

Hello. In the machine where those packages are installed, there's no need to update ports that don't show up in the result of pkg version. However, since the version number is also recorded in the dependencies in the package, everything is rebuilt just to rewrite it. For example, information

FreeBSD 13 + CertBot + OpenSSL 3 - status?

Does anyone in 'port land' know what the current developments are wrt CertBot (or py-crypto under its hood)? CertBot is happily compiling against OpenSSL 3 from ports, but when running 'certbot', the crypto side of it talks to the base system OpenSSL 1.1.1, hence failing because the OpenSSL

Re: FreeBSD 13 + CertBot + OpenSSL 3 - status?

On 24/10/2023 13:54, DutchDaemon - FreeBSD Forums Administrator wrote: Does anyone in 'port land' know what the current developments are wrt CertBot (or py-crypto under its hood)? CertBot is happily compiling against OpenSSL 3 from ports, but when running 'certbot', the crypto side of it