2.1.3 and Solaris 9 compile errors
I'm trying to get freeradius v2.1.3 to compile on a Solaris 9 box. I have openssl installed in /usr/local/ssl/openssl and have pointed the includes and libraries at that directory. I still get compile errors during install. Perl is v5.6.1 OpenSSL is v0.9.6e ./configure runs fine without any errors, but when I run a make/gmake on it, I get the following errors: ld: fatal: relocations remain against allocatable but non-writable sections collect2: ld returned 1 exit status gmake[6]: *** [rlm_perl.la] Error 1 gmake[6]: Leaving directory `/usr/local/src/freeradius-server-2.1.3/src/modules/rlm_perl' gmake[5]: *** [common] Error 2 gmake[5]: Leaving directory `/usr/local/src/freeradius-server-2.1.3/src/modules' gmake[4]: *** [all] Error 2 gmake[4]: Leaving directory `/usr/local/src/freeradius-server-2.1.3/src/modules' gmake[3]: *** [common] Error 2 gmake[3]: Leaving directory `/usr/local/src/freeradius-server-2.1.3/src' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/local/src/freeradius-server-2.1.3/src' gmake[1]: *** [common] Error 2 gmake[1]: Leaving directory `/usr/local/src/freeradius-server-2.1.3' gmake: *** [all] Error 2 I'm looking for JUST the VMPS functionality of freeradius. Anyway to try disabling all the other functionality and just compile the VMPS portion of freeradius? I can't seem to find a list of all the options to disable with the --disabl-"FEATURE" option from ./configure. --greg
Greg Fuller wrote:
I'm trying to get freeradius v2.1.3 to compile on a Solaris 9 box. I have openssl installed in /usr/local/ssl/openssl and have pointed the includes and libraries at that directory. I still get compile errors during install.
Perl is v5.6.1 OpenSSL is v0.9.6e
./configure runs fine without any errors, but when I run a make/gmake on it, I get the following errors: ... `/usr/local/src/freeradius-server-2.1.3/src/modules/rlm_perl'
$ cd /usr/local/src/freeradius-server-2.1.3/ $ rm -rf src/modules/rlm_perl
I'm looking for JUST the VMPS functionality of freeradius.
If you don't want the Perl module, just delete it. It causes problems on a LOT of platforms.
Anyway to try disabling all the other functionality and just compile the VMPS portion of freeradius? I can't seem to find a list of all the options to disable with the --disabl-"FEATURE" option from ./configure.
FreeRADIUS is still mostly a RADIUS server. So most of the functionality of RADIUS is built in, and can't be removed. Most of the modules *don't* implement RADIUS, however. So they're all built as part of the VMPS effort. Alan DeKok.
Greg Fuller wrote:
I'm trying to get freeradius v2.1.3 to compile on a Solaris 9 box. I have openssl installed in /usr/local/ssl/openssl and have pointed the includes and libraries at that directory. I still get compile errors during install.
Perl is v5.6.1 OpenSSL is v0.9.6e
./configure runs fine without any errors, but when I run a make/gmake on it, I get the following errors: ... `/usr/local/src/freeradius-server-2.1.3/src/modules/rlm_perl'
$ cd /usr/local/src/freeradius-server-2.1.3/ $ rm -rf src/modules/rlm_perl This is not solution. I am know how resolve this problem. If anyone need this. Please ask me. May be this solution need for developers. I am long time useing FreeRadius on Solaris. And I am know how to do this.
Anatoly S. Zimin wrote:
Greg Fuller wrote: [snip] $ cd /usr/local/src/freeradius-server-2.1.3/ $ rm -rf src/modules/rlm_perl
This is not solution. I am know how resolve this problem. If anyone need this. Please ask me. May be this solution need for developers. I am long time useing FreeRadius on Solaris. And I am know how to do this.
Post it to the list, and document it in the Wiki. Someone is bound to need a real solution to this problem. //anders
On 10:32 Thu 25 Dec , Anders Holm wrote:
Anatoly S. Zimin wrote:
Greg Fuller wrote: [snip] $ cd /usr/local/src/freeradius-server-2.1.3/ $ rm -rf src/modules/rlm_perl
This is not solution. I am know how resolve this problem. If anyone need this. Please ask me. May be this solution need for developers. I am long time useing FreeRadius on Solaris. And I am know how to do this.
Post it to the list, and document it in the Wiki. Someone is bound to need a real solution to this problem.
//anders OK. How to build rlm_perl module on Solaris 9/10. Work on FreeRadius 1.x and 2.x Set shell environment like LDFLAGS, LD_OPTIONS, and others.
# export PATH=$PATH:/usr/sbin:/usr/bin:/opt/csw/bin:/usr/sbin:/usr/bin:/usr/dt/bin:/usr/openwin/bin:/usr/ccs/bin:/usr/local/bin:/usr/sfw/bin # export LDFLAGS='-L/usr/sfw/lib -R/usr/sfw/lib -L/lib -R/lib' # export LD_OPTIONS='-L/usr/sfw/lib -R/usr/sfw/lib -L/lib -R/lib' # export CFLAGS='-I/usr/include -I/usr/sfw/include -I/usr/include/kerberosv5 -I/zones/src/freeradius-server-2.1.3/libltdl' # /usr/sfw/bin/gtar -xvjf freeradius-* # cd freeradius-* # patch < solaris.rlm_perl.patch File to patch: src/modules/rlm_perl/configure done. # ./configure --prefix=/path/to/install --with-openssl-includes=/usr/sfw/include --with-openssl-libraries=/usr/sfw/lib # gmake # gmake install P.S. patch file in attach. Where I got it? I am read this in manual for gcc! :) ######################## -mimpure-text -mimpure-text, used in addition to -shared, tells the compiler to not pass -z text to the linker when linking a shared object. Using this option, you can link position-dependent code into a shared object. -mimpure-text suppresses the ``relocations remain against allocat- able but non-writable sections'' linker error message. However, the necessary relocations will trigger copy-on-write, and the shared object is not actually shared across processes. Instead of using -mimpure-text, you should compile all source code with -fpic or -fPIC. This option is only available on SunOS and Solaris. ######################## And please somebody put this on freeradius Wiki. Or include in main branch of freeradius. Thanks a lot. -- Anatoly S. Zimin
Thanks Anatoly. Hopefully Alan will pick this up.... Sent from my iPhone On 25 Dec 2008, at 13:21, "Anatoly S. Zimin" <anatolyz@team.co.ru> wrote:
On 10:32 Thu 25 Dec , Anders Holm wrote:
Anatoly S. Zimin wrote:
Greg Fuller wrote: [snip] $ cd /usr/local/src/freeradius-server-2.1.3/ $ rm -rf src/modules/rlm_perl
This is not solution. I am know how resolve this problem. If anyone need this. Please ask me. May be this solution need for developers. I am long time useing FreeRadius on Solaris. And I am know how to do this.
Post it to the list, and document it in the Wiki. Someone is bound to need a real solution to this problem.
//anders OK. How to build rlm_perl module on Solaris 9/10. Work on FreeRadius 1.x and 2.x Set shell environment like LDFLAGS, LD_OPTIONS, and others.
# export PATH=$PATH:/usr/sbin:/usr/bin:/opt/csw/bin:/usr/sbin:/usr/ bin:/usr/dt/bin:/usr/openwin/bin:/usr/ccs/bin:/usr/local/bin:/usr/ sfw/bin # export LDFLAGS='-L/usr/sfw/lib -R/usr/sfw/lib -L/lib -R/lib' # export LD_OPTIONS='-L/usr/sfw/lib -R/usr/sfw/lib -L/lib -R/lib' # export CFLAGS='-I/usr/include -I/usr/sfw/include -I/usr/include/ kerberosv5 -I/zones/src/freeradius-server-2.1.3/libltdl' # /usr/sfw/bin/gtar -xvjf freeradius-* # cd freeradius-* # patch < solaris.rlm_perl.patch File to patch: src/modules/rlm_perl/configure done. # ./configure --prefix=/path/to/install --with-openssl-includes=/usr/ sfw/include --with-openssl-libraries=/usr/sfw/lib # gmake # gmake install
P.S. patch file in attach. Where I got it? I am read this in manual for gcc! :)
######################## -mimpure-text -mimpure-text, used in addition to -shared, tells the compiler to not pass -z text to the linker when linking a shared object. Using this option, you can link position-dependent code into a shared object.
-mimpure-text suppresses the ``relocations remain against allocat- able but non-writable sections'' linker error message. However, the necessary relocations will trigger copy-on-write, and the shared object is not actually shared across processes. Instead of using -mimpure-text, you should compile all source code with -fpic or -fPIC.
This option is only available on SunOS and Solaris. ########################
And please somebody put this on freeradius Wiki. Or include in main branch of freeradius.
Thanks a lot.
-- Anatoly S. Zimin <solaris.rlm_perl.patch> - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Anders Holm wrote:
Thanks Anatoly. Hopefully Alan will pick this up....
Feel free to fix the patch so: 1) It doesn't patch "configure" 2) It doesn't break builds for for non-GCC compilers 3) It doesn't break builds for non-Solaris systems. In case no one noticed, FreeRADIUS builds with non-GCC compilers, and on non-Solaris systems. Patches that "fix" it on one platform, and break it on every *other* platform are not acceptable. Alan DeKok.
Hi!
Anders Holm wrote:
Thanks Anatoly. Hopefully Alan will pick this up....
Feel free to fix the patch so:
1) It doesn't patch "configure" why?
2) It doesn't break builds for for non-GCC compilers Yes.
3) It doesn't break builds for non-Solaris systems. Yes.
In case no one noticed, FreeRADIUS builds with non-GCC compilers, and on non-Solaris systems. Patches that "fix" it on one platform, and break it on every *other* platform are not acceptable.
Yes.
Alan DeKok.
Of course this patch _ONLY_ for Solaris OS and only for gcc compiler. But this is solution. -- Anatoly.
Anatoly S. Zimin wrote:
Hi!
Anders Holm wrote:
Thanks Anatoly. Hopefully Alan will pick this up.... Feel free to fix the patch so:
1) It doesn't patch "configure" why?
"configure" is an auto-generated file. Like a ".o" file. It will change every time it's re-generated.
2) It doesn't break builds for for non-GCC compilers Yes.
3) It doesn't break builds for non-Solaris systems. Yes.
In case no one noticed, FreeRADIUS builds with non-GCC compilers, and on non-Solaris systems. Patches that "fix" it on one platform, and break it on every *other* platform are not acceptable. Yes.
Alan DeKok.
Of course this patch _ONLY_ for Solaris OS and only for gcc compiler. But this is solution.
The server isn't a collection of random patches for different systems. Asking someone to track this patch *manually* is not a good engineering practice. I'm willing to integrate the changes into the server source control. That *is* the best place for them. However, the changes have to be updated to fix the above problems. Otherwise, they: a) have to tracked manually on a Wiki somewhere or b) they will break builds on every non-GCC and non-Solaris system. Alan DeKok.
Anatoly S. Zimin wrote:
How to build rlm_perl module on Solaris 9/10. Work on FreeRadius 1.x and 2.x Set shell environment like LDFLAGS, LD_OPTIONS, and others. ... P.S. patch file in attach.
This is not a solution.
Where I got it? I am read this in manual for gcc! :)
Which isn't in the GCC manual *I* have access to.. because I don't run Solaris.
And please somebody put this on freeradius Wiki. Or include in main branch of freeradius.
No. Or at least, not until the patch is fixed. Why? Because this is a patch for *GCC* on *SOLARIS*. Q: What happens when this patch is used on Solaris for non-GCC systems? Q: What happens when this patch is used on non-Solaris systems? Alan DeKok.
Anatoly S. Zimin wrote:
How to build rlm_perl module on Solaris 9/10. Work on FreeRadius 1.x and 2.x Set shell environment like LDFLAGS, LD_OPTIONS, and others. ... P.S. patch file in attach.
This is not a solution.
Where I got it? I am read this in manual for gcc! :)
Which isn't in the GCC manual *I* have access to.. because I don't run Solaris. gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)
And please somebody put this on freeradius Wiki. Or include in main branch of freeradius.
No. Or at least, not until the patch is fixed. Why? Because this is a patch for *GCC* on *SOLARIS*. I am understand this.
Q: What happens when this patch is used on Solaris for non-GCC systems? Q: What happens when this patch is used on non-Solaris systems? I do not know...
Alan DeKok.
OK. When I have more time, I test it. And report. -- Anatoly S. Zimin
participants (4)
-
Alan DeKok -
Anatoly S. Zimin -
Anders Holm -
Greg Fuller