Re: Scripts / utils for maintaining ports?

Hello, I maintain only a few ports, although some of them (the GCC ports) are very complex and time consuming to take care of. A few months ago, I found myself having much less time to maintain ports, so I made heavier use of automation. The most time consuming part for me usually is testing the

Setting of DEFAULT_VERSIONS of php and poudriere's ports compilation woes in my setup

Hi, I am following the git repository for ports and using poudriere to compile those. Today I stumbled over: 20231125: AFFECTS: users of lang/php81 AUTHOR: b...@freebsd.org The default version of PHP has been switched from 8.1 to 8.2. […] I had h

Re: Setting of DEFAULT_VERSIONS of php and poudriere's ports compilation woes in my setup

On 02/12/23 21:37, Michael Grimm wrote: Hi, I am following the git repository for ports and using poudriere to compile those. Today I stumbled over: 20231125: AFFECTS: users of lang/php81 AUTHOR: b...@freebsd.org The default version of PHP has been switc

aarch64: sysutils/cpu-x@ncurses got SIGSEGV during its initial print_activecore

Note: This is from my own poudriere-devel based build of: sysutils/cpu-x@ncurses gdb reports from the cpu-x.core that was generated: Core was generated by `cpu-x'. Program terminated with signal SIGSEGV, Segmentation fault. Address not mapped to object. #0 0x2acc3a04 in __strtok_r (s=0x1

Re: aarch64: sysutils/cpu-x@ncurses got SIGSEGV during its initial print_activecore

On Dec 2, 2023, at 23:16, Mark Millard wrote: > Note: This is from my own poudriere-devel based build of: > sysutils/cpu-x@ncurses > > gdb reports from the cpu-x.core that was generated: > > Core was generated by `cpu-x'. > Program terminated with signal SIGSEGV, Segmentation fault. > Address n