Re: Applying distribution patches for u-boot-rpi4-2020.04 fails during build (poudriere-devel context)

On 2020-Apr-25, at 02:00, Emmanuel Vadot wrote: > On Sat, 25 Apr 2020 10:56:47 +0200 > Emmanuel Vadot wrote: > >> On Sat, 25 Apr 2020 00:43:27 -0700 >> Mark Millard via freebsd-uboot wrote: >> >>> From the log file: >>> >>> ===> Patching for u-boot-rpi4-2020.04 >>> ===> Applying

aarch64 based sysutils/u-boot-rpi[34] (and more?) builds fail for: "aarch64-none-elf-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found"

The below where based on poudriere-devel based build attempts. /usr/ports/ was based on head -r532972 and aarch64 FreeBSD was based on head -r360311 . amd64 FreeBSD did not have the build problem for the aaarch64-targeted u-boot ports. The overall build is still going and more aarch64-targeted

FreeBSD ports you maintain which are out of date

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,

Re: python 2.7 marked as deprecated and EOL while 2.7.18 RC is available

On Sat, 25 Apr 2020 16:21:25 -0700 (PDT) Roger Marquis wrote: > Kurt Jaeger wrote: > > I prepared a patch to build lyx without the 2.7 restriction. The > > patch needs a run-test, can you test and report back ? > > Has anyone enumerated the ports and applications which don't work with >

math/R: Upcoming major version update

Hello all, You are receiving this message because you maintain a port that has a run-time dependency on math/R. This is a heads-up that math/R will be updated to version 4.0.0. As this is a major version change, R packages will also need to be rebuilt. Unless there are some unforeseen

Using pkg in documentation

What is the way of mentioning about installing a py-package in documentation? Let’s say now the default version of python is 3.7 so in most of the cases we can write in our documentation that do the following: # pkg install py37-babel But when the default version of python is changed this is no

Re: aarch64 host based sysutils/u-boot-{pine64, rock64, rpi[34]} builds fail for: "aarch64-none-elf-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found"

On 2020-Apr-26, at 01:14, Mark Millard wrote: > The below where based on poudriere-devel based build attempts. > /usr/ports/ was based on head -r532972 and aarch64 FreeBSD was > based on head -r360311 . amd64 FreeBSD did not have the build > problem for the aaarch64-targeted u-boot ports. >

Re: Using pkg in documentation

Hi, What about using the meta-port lang/python ? You could write something like the following lines in your documentation: PY=`pkg rquery -r FreeBSD "%dn" lang/python | head -n 1 | sed "s/python//"` pkg install py${PY}-babel "-r FreeBSD" can indeed be ommited in a default configuration where the

Re: python 2.7 marked as deprecated and EOL while 2.7.18 RC is available

I have submitted a bug, bugzilla/show_bug.cgi?id=245799 , to update math/gnumeric to run with python3. It's a bit odd because the current version in ports builds and runs with either python 2 or 3 by default, but the FreeBSD port does not

Re: Using pkg in documentation

> PY=`pkg rquery -r FreeBSD "%dn" lang/python | head -n 1 | sed "s/python//"` You can even replace head with a sed command if you need to save some characters on the line: PY=`pkg rquery -r FreeBSD "%dn" lang/python | sed "s/python//;1q"` > ___