seems to be a tonne of opportunity to smoke fink

[Gagan Sidhu]

… but i guess we’re shorthanded.

today i built nodejs18 with a couple of flags anyone could find if they attempted it (after removing the OS check via sudo port edit), and then hard-coding (lol it was a test) -L/opt/local/libexec/llvm-17/lib/libc++

it works completely fine if i put that path on LD_LIBRARY_PATH (“just?” lol)
	- i know that’s a huge siren for the maintainers here lol, i get it, but the point isn’t that this version was ready for distribution)

given the static libc++ included in the ports llvm, it seems to me there is a tonne of opportunity to use the static libc++ from newer llvms to supplement the older /usr/lib/libc++ to take our game to the next level.

of course it may not be that simple. i’m far from a compiler expert, acknowledge the library name clash of /usr/lib/libc++ and the static in /opt/local/libexec/llvm-<version>, and this may be what the macports libc++ was designed to alleviate.

i just thought it was pretty interesting to have a newish node on an “old” OS with relatively little effort.
	- i bet this experience would apply to a lot of ports, hence my first line (underhanded).


Thanks,
Gagan