AOLserver on 64-bit Linux

Everyone,

Through John Buckman's loaning me the temporary use of a
2-CPU Xeon E5335
Clovertown (quad-core) box, I've been able to figure out how
to get
64-bit AOLserver running on it.

The recent suggestion of CC="gcc -nostartfiles" to
get AOLserver to
compile and link (due to the _init symbol issue) yields a
nsd binary
that doesn't run properly when 64-bit.  What I believe is
the correct
"fix" to the problem is to edit include/ns.mak
like so:

Change:

    LDLIB           = $ -shared $ $

to:

    LDLIB           = $ -nostartfiles -shared $
$

Adding the -nostartfiles to only the LDLIB variable allows
AOLserver to
link, but produces a nsd binary that appears to run without
the segfault
problem on 64-bit Linux.

I'd like to hear from others who have access to 64-bit
platforms if this
fixes your issue, as well.

-- Dossy

-- 
Dossy Shiobara              | dossypanoptic.com | http://dossy.org/
Panoptic Computer Network   | http://panoptic.com/
  "He realized the fastest way to change is to laugh at
your own
    folly -- then you can let go and quickly move on."
(p. 70)


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
<listservlistserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message.
You can leave the Subject: field of your email blank.

On 2007.09.24, Tom Jackson <tomRMADILO.COM> wrote:
> I know I didn't make this change, but my include/ns.mak
file has this:
...
> LDLIB           = gcc -pipe -shared -nostartfiles

This is likely a Tcl version related issue--older versions
of Tcl (i.e.,
tclConfig.sh) had the LDLIB you see above, but newer
versions of Tcl
(not sure exactly which version, maybe 8.4.15) had the line
that John's
ns.mak had.

If your LDLIB looks like what you see above, you shouldn't
need to make
*any* changes in order for AOLserver to build and link
properly, I
believe.  I could be wrong--I haven't tested very
rigorously.

-- Dossy

-- 
Dossy Shiobara              | dossypanoptic.com | http://dossy.org/
Panoptic Computer Network   | http://panoptic.com/
  "He realized the fastest way to change is to laugh at
your own
    folly -- then you can let go and quickly move on."
(p. 70)


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
<listservlistserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message.
You can leave the Subject: field of your email blank.

I know I didn't make this change, but my include/ns.mak file
has this:
# $Header: /cvsroot/aolserver/aolserver/include/ns.mak.in,v
1.5 2006/06/27 
17:00:55 jgdavidson Exp $

.....

LDLIB           = gcc -pipe -shared -nostartfiles

tom jackson

On Sunday 23 September 2007 15:40, Dossy Shiobara wrote:
> Everyone,
>
> Through John Buckman's loaning me the temporary use of
a 2-CPU Xeon E5335
> Clovertown (quad-core) box, I've been able to figure
out how to get
> 64-bit AOLserver running on it.
>
> The recent suggestion of CC="gcc
-nostartfiles" to get AOLserver to
> compile and link (due to the _init symbol issue) yields
a nsd binary
> that doesn't run properly when 64-bit.  What I believe
is the correct
> "fix" to the problem is to edit
include/ns.mak like so:
>
> Change:
>
>     LDLIB           = $ -shared $
$
>
> to:
>
>     LDLIB           = $ -nostartfiles -shared
$ $
>
> Adding the -nostartfiles to only the LDLIB variable
allows AOLserver to
> link, but produces a nsd binary that appears to run
without the segfault
> problem on 64-bit Linux.
>
> I'd like to hear from others who have access to 64-bit
platforms if this
> fixes your issue, as well.
>
> -- Dossy


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
<listservlistserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message.
You can leave the Subject: field of your email blank.

Hi!

I'm not sure if my post is off-topic, but when I did compile
Aolserver 
in my x86-64 machine I had problems with TCL, tDOM (not
Aolserver).

You can see my problem in: 
http://openacs.org/forums/message-view?message_id=369867


It was a problem I had installing Aolserver. I think it
doesn't matter 
here but perhaps it is.

Cesareo

Dossy Shiobara escribió:
> On 2007.09.24, Tom Jackson <tomRMADILO.COM> wrote:
>> I know I didn't make this change, but my
include/ns.mak file has this:
> ...
>> LDLIB           = gcc -pipe -shared -nostartfiles
> 
> This is likely a Tcl version related issue--older
versions of Tcl (i.e.,
> tclConfig.sh) had the LDLIB you see above, but newer
versions of Tcl
> (not sure exactly which version, maybe 8.4.15) had the
line that John's
> ns.mak had.
> 
> If your LDLIB looks like what you see above, you
shouldn't need to make
> *any* changes in order for AOLserver to build and link
properly, I
> believe.  I could be wrong--I haven't tested very
rigorously.
> 
> -- Dossy
> 


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
<listservlistserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message.
You can leave the Subject: field of your email blank.

Dossy,

You are right, previously I posted my info because I'm
running on 64-bit AMD 
and AOLserver was running without problems. I have Tcl
8.4.14.

I wasn't sure what the command was to detect 64-bit, but I
just found 
that 'file exename' works:

$ file nsd
nsd: ELF 64-bit LSB executable, AMD x86-64, version 1
(SYSV), for GNU/Linux 
2.6.9, dynamically linked (uses shared libs), for GNU/Linux
2.6.9, not 
stripped

I wonder why Tcl made these changes? The -pipe is also
missing.

tom jackson


On Monday 24 September 2007 09:18, Dossy Shiobara wrote:
> On 2007.09.24, Tom Jackson <tomRMADILO.COM> wrote:
> > I know I didn't make this change, but my
include/ns.mak file has this:
>
> ...
>
> > LDLIB           = gcc -pipe -shared -nostartfiles
>
> This is likely a Tcl version related issue--older
versions of Tcl (i.e.,
> tclConfig.sh) had the LDLIB you see above, but newer
versions of Tcl
> (not sure exactly which version, maybe 8.4.15) had the
line that John's
> ns.mak had.
>
> If your LDLIB looks like what you see above, you
shouldn't need to make
> *any* changes in order for AOLserver to build and link
properly, I
> believe.  I could be wrong--I haven't tested very
rigorously.
>
> -- Dossy


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
<listservlistserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message.
You can leave the Subject: field of your email blank.

> I'm not sure if my post is off-topic, but when I did
compile  
> Aolserver in my x86-64 machine I had problems with TCL,
tDOM (not  
> Aolserver).
> You can see my problem in: http://openac
s.org/forums/message-view? 
> message_id=369867
> It was a problem I had installing Aolserver. I think it
doesn't  
> matter here but perhaps it is.

I use tDOM on the 64 bit machine, and instead of installign
tDOM from  
a tea file, I installed from the tarfile, with the command:

../configure --enable-threads --with-tcl=/usr/local/lib/ 
--enable-64bit

and didn't have any problems with tDOM under 64 bit
aolserver.

-john


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
<listservlistserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message.
You can leave the Subject: field of your email blank.