dlopen issues on Almalinux9
I'm trying to build freeradius from the git version 4.0.0 on Almalinux9, but having problems with failures building the included dlopen.c. Building under the OpenPKG package management system. # uname -a Linux almadev9.mi.celestial.com 5.14.0-70.13.1.el9_0.x86_64 #1 SMP PREEMPT Tue May 17 15:53:11 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux gcc-11.2.0 binutils-2.38 automake-1.16.5 autoconf-2.71 libtool-2.4.6 The compile is failing with __GLIBC_USE and __GNUC_PREREQ errors. The configure script finds the system's -ldl, but I haven't been able to figure out how to use that instead of the included dlopen. I've had similar results trying to build on the latest versions of 64-bit Raspberry Pi Linux. Bill -- INTERNET: bill@celestial.com Bill Campbell; Celestial Software LLC URL: http://www2.celestial.com/ 6641 E. Mercer Way Mobile: (206) 947-5591 PO Box 820 Fax: (206) 232-9186 Mercer Island, WA 98040-0820
On Jul 14, 2022, at 7:37 PM, Bill Campbell <bill@celestial.com> wrote:
I'm trying to build freeradius from the git version 4.0.0 on Almalinux9,
So if v4 works, great. Otherwise, it's largely unreleased, and unsupported. We're actively developing it, and it may (or may not) work on a day-to-day basis.
but having problems with failures building the included dlopen.c.
You haven't posted any actual error messages, so it's a little difficult to tell what's going on.
Building under the OpenPKG package management system.
# uname -a Linux almadev9.mi.celestial.com 5.14.0-70.13.1.el9_0.x86_64 #1 SMP PREEMPT Tue May 17 15:53:11 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux
gcc-11.2.0 binutils-2.38 automake-1.16.5 autoconf-2.71 libtool-2.4.6
None of that really matters.
The compile is failing with __GLIBC_USE and __GNUC_PREREQ errors.
Perhaps it would be useful to post the actual error messages.
The configure script finds the system's -ldl, but I haven't been able to figure out how to use that instead of the included dlopen.
The file scripts/build/dlopen.c doesn't implement the dlopen() API. The system libdl.so implements that.
I've had similar results trying to build on the latest versions of 64-bit Raspberry Pi Linux.
If only there was some way to post actual error messages, instead of vague descriptions about the underlying platform. It should be blatantly obvious that the best approach is to post the error messages. Alan DeKok.
On Thu, Jul 14, 2022, Alan DeKok wrote:
On Jul 14, 2022, at 7:37 PM, Bill Campbell <bill@celestial.com> wrote:
I'm trying to build freeradius from the git version 4.0.0 on Almalinux9,
So if v4 works, great. Otherwise, it's largely unreleased, and unsupported.
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).
We're actively developing it, and it may (or may not) work on a day-to-day basis.
but having problems with failures building the included dlopen.c.
You haven't posted any actual error messages, so it's a little difficult to tell what's going on.
I didn't want initially to post a fairly large message to the list, hoping that somebody already had addressed this problem.
It should be blatantly obvious that the best approach is to post the error messages.
OK, I'm attaching a gzip'ed file with the output of my most recent build attempt of the 4.0.0 branch. Bill -- INTERNET: bill@celestial.com Bill Campbell; Celestial Software LLC URL: http://www2.celestial.com/ 6641 E. Mercer Way Mobile: (206) 947-5591 PO Box 820 Fax: (206) 232-9186 Mercer Island, WA 98040-0820 Currencies do not float, they sink at different rates.
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.
participants (2)
-
Alan DeKok -
Bill Campbell