Macport build fails on Big Sur
Description
Environment
Activity
Forcing the port to autoreconf fixed it. I have to assume I built the distribution with a slightly out of date libtool and that the next round of builds would fix it.
I believe the problem may be that I built the distributions with /opt/local/lib in front of my path, causing the macports libtool to get used, and I guess that one is the broken one. Apple's would probably work. I'm trying a workaround to force an autoreconf in the port build, but it's a little odd if they actually force that to rely on Apple's copy and not their own.
Had occasion to look at this again and it appears this may be a libtool glitch that's operating differently between my command line and macports. There's an ld flag on the Mac, "-undefined" that needs to be set to dynamic_lookup to build plugins and I have to assume my CLI build is setting it but the port isn't. Need to verify by unsilenting the command line's libtool generates for the final link step on the Apache module.
Even if that's the cause I don't know how to fix it.
Still broken in 3.2.0. The issue is that it wants to find all the Apache ap_XXX calls in the module, which don't exist until you actually load it, but the linker now wants them defined, so something changed and I have no particular insight into how to fix that.
Nope, still broken, same linking issue. What is definitely broken is that it won't locate apxs anymore and needs a --with-apxs2 option, so I can do that, but I don't know that I can do anything obvious about the build.
The port is not building because of some linking issue I haven't reproduced with a direct build out of the source tree. It fails due to missing Apache symbols linking the module.
I've seen a decent number of ports failing at this point.
About all I can think to do is to compare the libtool commands pretty closely.