py-tables uses wrong flags with hdf5 module

[barracuda156]

/opt/local/bin/gcc-mp-14 -bundle -undefined dynamic_lookup -L/opt/local/lib -Wl,-headerpad_max_install_names -Wl,-read_only_relocs,suppress -Wl,-force_cpusubtype_ALL -arch ppc -arch ppc -isysroot/ build/temp.macosx-10.6-ppc-cpython-311/hdf5-blosc/src/blosc_filter.o build/temp.macosx-10.6-ppc-cpython-311/hdf5-blosc2/src/blosc2_filter.o build/temp.macosx-10.6-ppc-cpython-311/src/H5ARRAY-opt.o build/temp.macosx-10.6-ppc-cpython-311/src/H5ARRAY.o build/temp.macosx-10.6-ppc-cpython-311/src/H5ATTR.o build/temp.macosx-10.6-ppc-cpython-311/src/H5VLARRAY.o build/temp.macosx-10.6-ppc-cpython-311/src/typeconv.o build/temp.macosx-10.6-ppc-cpython-311/src/utils.o build/temp.macosx-10.6-ppc-cpython-311/tables/hdf5extension.o -L/sw/lib64 -L/usr/local/lib -L/opt/lib -L/opt/local/lib -L/usr/lib -L/sw/lib -L/opt/local/lib64 -L/usr/lib64 -L/usr/local/lib64 -L/opt/lib64 -L/lib64 -L/lib -lhdf5 -lblosc -lblosc2 -o build/lib.macosx-10.6-ppc-cpython-311/tables/hdf5extension.cpython-311-darwin.so
ld: warning: directory '/sw/lib64' following -L not found
ld: warning: directory '/opt/lib' following -L not found
ld: warning: directory '/sw/lib' following -L not found
ld: warning: directory '/opt/local/lib64' following -L not found
ld: warning: directory '/usr/lib64' following -L not found
ld: warning: directory '/usr/local/lib64' following -L not found
ld: warning: directory '/opt/lib64' following -L not found
ld: warning: directory '/lib64' following -L not found
ld: warning: directory '/lib' following -L not found
building 'tables.tableextension' extension

[reneeotten (Renee Otten)]

but it also adds -L/opt/local/lib so the build should succeed - correct? So you're worried about upstream looking into too many different places that don't exists and show a warning? How about just ignoring the warning as none of the other location should be present anyway; is there a benefit of patching them out?

[barracuda156]

Replying to reneeotten:

but it also adds -L/opt/local/lib so the build should succeed - correct? So you're worried about upstream looking into too many different places that don't exists and show a warning? How about just ignoring the warning as none of the other location should be present anyway; is there a benefit of patching them out?

This will create a linking mess on Linux at least, where /use/local/lib64 may exist, or on macOS with Fink installed along with MacPorts, where /sw/lib exists.

[reneeotten (Renee Otten)]

Nobody should have installed multiple package managers on macOS but yes it could result in errors on Linux, but to be fair that’s not a real concern. Feel free to submit a PR to change this.