FR 2.2.5 64 bit

Fajar A. Nugraha list at fajar.net
Tue May 6 05:45:58 CEST 2014


On Tue, May 6, 2014 at 10:33 AM, Mohd Alkhaldi <alwaadalhaq at gmail.com>wrote:

> Hi,
> In the beginning the compilation failed with the following error:
>  /oracle/software/adsl/freeradius-server-2.2.5/src/freeradius-devel/libradius.h:408:
> error: syntax error before "sig_t"
>
> To fix this error, I've added the following line in libradius.h after
> "#include <signal.h>"
> typedef void *sig_t;
>
> Again compilation failed with the following error:
>
> ld: fatal: file .libs/debug.o: wrong ELF class: ELFCLASS64
> ld: fatal: File processing errors. No output written to
> .libs/libfreeradius-radius--m64.so
> collect2: ld returned 1 exit status
> gmake[4]: *** [libfreeradius-radius.la] Error 1
>
> * Note even with 3.0.2 same error.
>
>

In my past experience with solaris, the first question if you want to
compile anything in 64bit is "why".

Solaris promotes the use of 32 bit userland whenever possible, allowing the
same root filesystem to be used by both 32-bit and 64-bit kernel. Plus, if
you use sparc (I assume you do, since you'll have many other OS options if
you had used x86), and your programs use less than 2GB of memory, there
might not be any percievable benefit by compiling it as 64bit. This is
different from x86 where the the 64bit extension can speed up some programs
due to additional CPU registers available.

Next, I usually had to add "export CFLAGS=-m64" before running ./configure.
>From a quick glance at your error message, it looks like some parts are
compiled as 32bit while others 64bit, so specifically forcing -m64 might
help.

Not sure about sig_t error, but if it were me I'd try using latest gcc
first.

-- 
Fajar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20140506/da521f3a/attachment-0001.html>


More information about the Freeradius-Users mailing list