On Jul 14, 2022, at 8:29 PM, Bill Campbell <bill@celestial.com> wrote:
I'm fine with that. I've tried with the release release_3_2_0 tag and the v3.2.x branch, but get orders of magnitude more errors (e.g. 2.5MB build output vs about 181KB. I don't know what the mailing list maximum size is (mine are generally 40KB).
You get build errors with 3.2? The system you're building it on must be very non-standard. 3.2 builds on just about every Unix variant (maybe not Irix), but everything else should be fine.
OK, I'm attaching a gzip'ed file with the output of my most recent build attempt of the 4.0.0 branch.
The list manager deletes zip attachments. They are almost never useful. Just post a few key messages inline. You asked about -ldl / dlopen, so... post those error messages. There's no need to post a zip file with megabytes of random other messages. And if there are *errors* during the build, the build process should stop. The only reason that the build process produces megabytes of messages is that if they're all C compiler warnings. Which can generally be ignored. The "configure" stage also produces voluminous logs, most of which aren't relevant. But if "make" produces errors when compiling files, your local OS is severely broken. Alan DeKok.