Tru64 again
Adharsh P
adharshp.enc at gmail.com
Wed Oct 5 11:03:18 CEST 2005
Hello Tim Winders,
When you run configure in Tru64, configure sets GETHOSTBYADDRRSTYLE
and GETHOSTBYNAMERSTYLE to GNUSTYLE in src/include/autoconf.h
Modify the two lines in src/include/autoconf.h
-#define GETHOSTBYADDRRSTYLE GNUTYPE
-#define GETHOSTBYNAMERSTYLE GNUTYPE
to
+#undef GETHOSTBYADDRRSTYLE
+#undef GETHOSTBYNAMERSTYLE
Also undef OSFC2 if you haven't already done this.
do a make and make install.
Run radiusd. It should be work.
---adharsh
RE: Tru64 again
Tim Winders
Thu, 15 Sep 2005 08:17:25 -0700 responding to my own
post. I saw a message about looking at the core dump
in another thread. So, I followed those instructions. Here is the output
from gdb:
This GDB was configured as "alphaev67-dec-osf5.1"...
BFD: Unhandled OSF/1 core file section type 4464
BFD: Unhandled OSF/1 core file section type 528
BFD: Unhandled OSF/1 core file section type 0
BFD: Unhandled OSF/1 core file section type 7
BFD: Unhandled OSF/1 core file section type 16384
BFD: Unhandled OSF/1 core file section type 8192
BFD: Unhandled OSF/1 core file section type 0
BFD: Unhandled OSF/1 core file section type 32768
BFD: Unhandled OSF/1 core file section type 49152
BFD: Unhandled OSF/1 core file section type 49152
BFD: Unhandled OSF/1 core file section type 7
BFD: Unhandled OSF/1 core file section type 57344
BFD: Unhandled OSF/1 core file section type 49152
warning: big endian file does not match little endian target.
Core was generated by `
'.
Program terminated with signal 1, Hangup.
warning: Couldn't find general-purpose registers in core file.
warning: Couldn't find general-purpose registers in core file.
#0 0x00000000 in ?? ()
when I did bt in gdb I got the same "#0 0x00000000 in ?? ()" response and
nothing else.
But, in reading the above, it seems a big endian v. little endian problem.
Does this help in getting freeradius to work on Tru64?
---
Tim Winders
Associate Dean of Information Technology
South Plains College
Levelland, TX 79336
Problem replying to my email? Click the "Sign" button in the OE toolbar or,
better yet, get your own FREE Personal E-Mail Digital ID:
http://www.thawte.com/email/index.html
> -----Original Message-----
> From: Tim Winders [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 14, 2005 11:35 AM
> To: 'freeradius-users at lists.freeradius.org'
> Subject: Tru64 again
>
> I'm back at trying to get freeradius working under Tru64.
> This time using 1.0.5.
>
> I have an older cvs version working, but I can't remember
> what I did to make it work. :-( The working version I have
> is marked 1.1.0-pre0 built on Feb 17, 2005.
>
> First, in src/main/radiusd.c I have commented out the OSFC2
> define. I do this because I'm not running C2, but it is
> always found and enabled, which kills the make. Then, I run
> configure with these options:
>
> CFLAGS="-I/usr/local/ssl/include -I/usr/local/include"
> LDFLAGS="-L/usr/local/ssl/lib -L/usr/local/lib" LIBS="-lssl
> -lcrypto -lsecurity" ./configure \
> --disable-shared \
> --enable-ltdl-install=no \
> --with-openssl-includes=/usr/local/ssl/include \
> --with-openssl-libraries=/usr/local/ssl/lib \
> --without-mysql --disable-mysql
>
> radiusd seems to compile, but with many warnings. However,
> when I run it, it immediately seg faults and dumps core.
> Unfortunately, I am not a programmer, so I don't know how to
> begin troubleshooting this and try to help get freeradius
> working under Tru64.
>
> I remember being told that none of the development team uses
> Tru64. So, it's possible this will never work "right". But,
> I'm willing to help out in whatever limited capacity I can,
> including CPU/shell account.
>
> Any useful suggestions are welcome.
More information about the Freeradius-Users
mailing list