HDF5 port is broken

2022-07-20 Thread Steve Kargl
This commit % git log -r a43418b81530f7 commit a43418b81530f7e897abfbe18dd59f44265a1a0f Author: Po-Chuan Hsieh Date: Mon Jul 18 20:50:16 2022 +0800 science/hdf5: Update to 1.12.2 Changes:https://portal.hdfgroup.org/display/support/HDF5+1.12.0 https://p

Re: HDF5 port is broken

2022-07-20 Thread Steve Kargl
On Wed, Jul 20, 2022 at 11:27:28AM -0700, Manfred Antar (KN6KBS) wrote: > I think I got around this by uninstalling hdf5 then do “cd > /usr/ports/science/hdf5;make clean all install". > Yep, after looking at the build failure more closely, I realized that the search path for the module files wa

Re: HDF5 port is broken

2022-07-20 Thread Steve Kargl
On Wed, Jul 20, 2022 at 08:50:56PM +0200, Christoph Moench-Tegeder wrote: > ## Steve Kargl (s...@troutmask.apl.washington.edu): > > > tH5F.F90:(.text+0x1f20): undefined reference to `h5fget_fileno_f_' > > Building in-system? Remove the old version first. > Yes. Remov

FLAVOR fallout?

2022-07-20 Thread Steve Kargl
% portmaster -Byd qt5-assistant [1/1] Deleting files for qt5-sqldrivers-sqlite3-5.15.2p263: 100% pkg-static: POST-DEINSTALL script failed ===>>> Starting check for runtime dependencies ===>>> Gathering dependency list for databases/qt5-sqldrivers-sqlite3 from ports ===>>> The dependency for dat

Re: FLAVOR fallout?

2022-07-20 Thread Steve Kargl
abases/sqlite3 defines FLAVORS but no FLAVOR is written > in *_DEPENDS of Mk/Uses/sqlite.mk like > libsqlite3.so:databases/sqlite3@default. > > I think python's FLAVOR is a perfect FLAVOR implementation, but sqlite3's > FLAVOR is a branch that should not use FLAVOR :)

Re: FLAVOR fallout?

2022-07-21 Thread Steve Kargl
/Uses/sqlite.mk was not relevant :) > > Regards. > > > Steve Kargl wrote on 2022/07/21 13:41: > > I'm in flavor of not breaking the ports system. > > Once again, removing old ports, and going into > > the spcific broken port and manual installing > > the port fixing the problem. > > -- Steve

Re: FLAVOR fallout?

2022-07-21 Thread Steve Kargl
On Fri, Jul 22, 2022 at 02:18:39PM +0900, Tatsuki Makino wrote: > Hello. > > So no matter how hard I tried I could not reproduce it, but that was a > problem that had already been fixed 😹 > The portmaster must have been updated from 3.21 to 3.22 during the update > that caused the problem. > Fre

Re: HEADS-UP: Upcoming move of WWW definitions in all ports

2022-09-06 Thread Steve Kargl
On Tue, Sep 06, 2022 at 08:09:24PM +0200, Stefan Esser wrote: > PortMgr has just accepted a change that has been in the making for some time: > > The move of the "WWW:" entries at the end of the ports' pkg-descr files into > the ports' Makefiles in the form of "WWW=" definitions. > > The WWW line

Re: HEADS-UP: Upcoming move of WWW definitions in all ports

2022-09-06 Thread Steve Kargl
On Tue, Sep 06, 2022 at 09:04:10PM +0200, Stefan Esser wrote: > Am 06.09.22 um 20:31 schrieb Steve Kargl: > > On Tue, Sep 06, 2022 at 08:09:24PM +0200, Stefan Esser wrote: > > > PortMgr has just accepted a change that has been in the making for some > > > time: > &

lang/llvm15 -- Why is flang being built?

2023-01-30 Thread Steve Kargl
Why does the lang/llvm15 port default to building flang (ie., the Fortran compiler)? % flang15 -o z a.f90 error: /usr/ports/devel/llvm15/work/llvm-project-15.0.7.src/flang/lib/Optimizer/CodeGen/Target.cpp:312: not yet implemented: target not implemented % flang-new15 -o z a.f90 error: /usr/port

Re: lang/llvm15 -- Why is flang being built?

2023-01-30 Thread Steve Kargl
On Mon, Jan 30, 2023 at 09:17:07PM +0300, Gleb Popov wrote: > On Mon, Jan 30, 2023 at 7:59 PM Steve Kargl > wrote: > > > > Why does the lang/llvm15 port default to building flang > > (ie., the Fortran compiler)? > > > > % flang15 -o z a.f90 > > err

Re: Shared object "libicuuc.so.70" not found on RPi4

2023-02-03 Thread Steve Kargl
On Fri, Feb 03, 2023 at 10:03:16AM -0800, bob prohaska wrote: > When trying to start inkscape on a Pi4 running -current the > system reports: > ld-elf.so.1: Shared object "libicuuc.so.70" not found, required by > "libvisio-0.1.so.1" > > The inkscape port was built using poudriere and is recent, b

Re: Shared object "libicuuc.so.70" not found on RPi4

2023-02-03 Thread Steve Kargl
On Fri, Feb 03, 2023 at 11:34:07AM -0800, bob prohaska wrote: > On Fri, Feb 03, 2023 at 10:25:26AM -0800, Steve Kargl wrote: > > % cat /etc/libmap.conf > > # $FreeBSD$ > > includedir /usr/local/etc/libmap.d > > libicui18n.so.71 libicuio.so.72 > >

devel/llvm16 -- flang is still broken

2023-02-09 Thread Steve Kargl
TL:DR: Please disable building flang in devel/llvm16. I was hoping to test the to Fortran compilers included in devel/llvm16. Unfortunately, neither flang16 nor flang-new16 are usable. % flang16 -o z a.f90 ld: error: undefined symbol: _FortranAioBeginExternalFormattedOutput >>> referenced by F

Re: devel/llvm16 -- flang is still broken

2023-02-09 Thread Steve Kargl
On Thu, Feb 09, 2023 at 02:07:11PM -0800, Steve Kargl wrote: > TL:DR: Please disable building flang in devel/llvm16. > > > I was hoping to test the to Fortran compilers included in > devel/llvm16. Unfortunately, neither flang16 nor flang-new16 > are usable. > This seems

Re: devel/llvm16 -- flang is still broken

2023-02-09 Thread Steve Kargl
On Fri, Feb 10, 2023 at 01:07:39AM +, Brooks Davis wrote: > On Thu, Feb 09, 2023 at 04:59:45PM -0800, Steve Kargl wrote: > > On Thu, Feb 09, 2023 at 02:07:11PM -0800, Steve Kargl wrote: > > > TL:DR: Please disable building flang in devel/llvm16. > > > > > >

perl build failure?

2024-08-10 Thread Steve Kargl
How is perl 5.36.3 the default version when it dies with WARNING: re-sorting MANIFEST *** [MANIFEST.srt] Error code 1 make: stopped making "all" in /usr/ports/lang/perl5.36/work/perl-5.36.3 --- lib/auto/re/re.so --- Unsuccessful make(ext/re): code=1536 at make_ext.pl line 584. *** [lib/auto/re/re

Re: perl build failure?

2024-08-10 Thread Steve Kargl
On Sat, Aug 10, 2024 at 08:05:25PM -0700, Steve Kargl wrote: > How is perl 5.36.3 the default version when it dies with > > WARNING: re-sorting MANIFEST > *** [MANIFEST.srt] Error code 1 > > make: stopped making "all" in /usr/ports/lang/perl5.36/work/perl-5.

Re: perl build failure?

2024-08-10 Thread Steve Kargl
On Sat, Aug 10, 2024 at 08:31:19PM -0700, David Wolfskill wrote: > On Sat, Aug 10, 2024 at 08:05:25PM -0700, Steve Kargl wrote: > > How is perl 5.36.3 the default version when it dies with > > > > WARNING: re-sorting MANIFEST > > *** [MANIFEST.srt] Error code 1 > &g

UPDATING providing misinformation

2024-08-10 Thread Steve Kargl
Updating a circ Feb 2024 system with python 3.9. Following ports/UPDATING # sh # portmaster -o lang/python311 python39 # REINSTALL="$(pkg info -oq '*py39*')" # pkg delete -f "*py39*" # portmaster $REINSTALL # REBUILD=$(pkg query -g "%n:%dn" '*' | grep py3 | grep -v py311 | cut -d : -f

Re: UPDATING providing misinformation

2024-08-11 Thread Steve Kargl
On Sun, Aug 11, 2024 at 07:53:50AM +, Alexander Burke wrote: > Hi Steve, > > >usr/ports/devel/py-setuptools_scm does not exist > > >py-setuptools-scm/ > > Just a teensy-weensy difference... > > >   # REINSTALL="$(pkg info -oq '*py39*')" > >   # pkg delete -f "*py39*" It's a gratuitous chan

Re: perl build failure?

2024-08-11 Thread Steve Kargl
On Sat, Aug 10, 2024 at 08:50:20PM -0700, Steve Kargl wrote: > On Sat, Aug 10, 2024 at 08:31:19PM -0700, David Wolfskill wrote: > > On Sat, Aug 10, 2024 at 08:05:25PM -0700, Steve Kargl wrote: > > > How is perl 5.36.3 the default version when it dies with > > > > &g

Re: perl build failure?

2024-08-11 Thread Steve Kargl
On Sun, Aug 11, 2024 at 10:21:31AM -0700, Steve Kargl wrote: > > Well, that was fun. Seems that either perl or clang do not > like "CPUTYPE?=amdfam10" in /etc/make.conf. > https://github.com/llvm/llvm-project/issues/89008 -- Steve

Re: Use of lang/gcc*'s g++* via the likes of USE_GCC=11:build+ in ports when a -Wl,-rpath=/usr/local/lib/gcc* is required: How?

2022-04-17 Thread Steve Kargl
On Sun, Apr 17, 2022 at 07:21:11PM -0700, Mark Millard wrote: > I'll use g++11 as an example here. By no means is the issue > limited to g++11 . Also, the general issue is not limited > to the specifics of the other aspects of the example I report > below. > > > EXAMPLE PROBLEM: > > FreeBSD's /l

Re: lang/gccXXX ports likely broken with -static option

2025-01-30 Thread Steve Kargl
On Wed, Jan 29, 2025 at 10:02:30AM -0800, Steve Kargl wrote: > On Tue, Jan 28, 2025 at 12:02:09PM -0800, Steve Kargl wrote: > > JFYI, > > > > The ports of lang/gcc are likely effected by > > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118685 > > >

lang/gccXXX ports likely broken with -static option

2025-01-28 Thread Steve Kargl
JFYI, The ports of lang/gcc are likely effected by https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118685 If one uses -static and ctor/dtor's are involved, the resulting executable will segfault at exit. -- Steve

Re: lang/gccXXX ports likely broken with -static option

2025-01-29 Thread Steve Kargl
On Tue, Jan 28, 2025 at 12:02:09PM -0800, Steve Kargl wrote: > JFYI, > > The ports of lang/gcc are likely effected by > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118685 > > If one uses -static and ctor/dtor's are involved, > the resulting executable will seg

phantom version numbers?

2025-02-26 Thread Steve Kargl
Recently update a freebsd-current system and all ports. Prior to updating the ports, I did % cd /usr/ports % git pull -ff % make fetchindex After the update I see, % pkg version -vl '<' | grep drm drm-515-kmod-5.15.160.1500031_3 < needs updating (index has 5.15.160.1500033_3) OK, first, attempt

Re: phantom version numbers?

2025-02-26 Thread Steve Kargl
On Thu, Feb 27, 2025 at 07:28:41AM +0900, Tomoaki AOKI wrote: > On Wed, 26 Feb 2025 13:25:20 -0800 > Steve Kargl wrote: > > > Recently update a freebsd-current system and all ports. > > Prior to updating the ports, I did > > > > % cd /usr/ports > &g

Re: phantom version numbers?

2025-02-26 Thread Steve Kargl
On Wed, Feb 26, 2025 at 02:42:14PM -0800, Steve Kargl wrote: > On Thu, Feb 27, 2025 at 07:28:41AM +0900, Tomoaki AOKI wrote: > > On Wed, 26 Feb 2025 13:25:20 -0800 > > Steve Kargl wrote: > > > > > Recently update a freebsd-current system and all ports. > >

Re: phantom version numbers?

2025-02-27 Thread Steve Kargl
On Thu, Feb 27, 2025 at 09:27:56PM +0900, Tomoaki AOKI wrote: > > Just a prediction, but possibly build cluster for main (15-Current) are > running on 1500033, while your build environment is running on 1500031. > That is exactly the problem. Someone tracking freebsd-current may have slightly d

Re: phantom version numbers?

2025-02-28 Thread Steve Kargl
On Thu, Feb 27, 2025 at 09:02:48PM -0800, Mark Millard wrote: > Steve Kargl wrote on > Date: Thu, 27 Feb 2025 18:52:17 UTC : > > > IMHO, the solution is clearly wrong. INDEX-15 is only > > valid for short period of time. Hmmm, it seems that > > the Porte

Re: phantom version numbers?

2025-02-28 Thread Steve Kargl
On Fri, Feb 28, 2025 at 12:43:20PM +0900, Tatsuki Makino wrote: > Hello. > > This may bring the topic back to the beginning, but how about adding the -P > option when using pkg-version? > In my environment, both take the same amount of time to the extent that > having an INDEX-* pre-built makes