Re: [Nel] NeLNS compilation problems

[Vianney Lecroart]

Ok,

So the only reason I see could be in the Makefile or autconf/automake.
You have to wait Cedric to have an answer about this problem. He should
comes back from his holiday tomorrow.

Vianney Lecroart
---
lead network programmer / nevrax.com
icq#: 6870415
homepage: http://ace.planet-d.net
www.geekcode.com: GCS/E d- s+++: a-- C+++$ UL++ P- L+++>+$ E+>- W++ N+ o? K-
w++$ O- M- V- PS- PE? Y PGP t 5? X+ R- tv++ b- DI D+ G e++ h+ r-- y?

----- Original Message -----
From: "Zane" <address@hidden>
To: <address@hidden>
Sent: Wednesday, August 15, 2001 6:20 PM
Subject: Re: [Nel] NeLNS compilation problems


> ----- Original Message -----
> From: "Vianney Lecroart" <address@hidden>
> Sent: Wednesday, August 15, 2001 2:45 AM
>
>
> > I compiled NeL and NeLNS yesterday without any problem on our gnu/linux
> > computer.
> > It seems that the problem is that you compiled NeL *without* STLPort, so
> the
> > first parameter of the getVar function is basic_string
>
> Actually since Monday it's been compiling just fine.  I've always been
> compiling with stlport.  Here's my compile procedure (I run it from a
> script, it was the same Monday as it was Friday when it didn't work):
>
> bootstrap
>
configure --with-stlport=/usr/src/STLPort-4.0 --with-freetype=/usr/include/f
> reetype2 --with-python=/usr/include/python-1.5
> make
>
> I have a similar script for NeLNS that uses STLPort. (has
the --with-stlport
> option).  If I recall correctly you MUST specifically tell it not to use
> STLPort.  Regardless, some change was made Monday or over the weekend that
> fixed my compiling problem.
>
> -E.J. Wilburn
>
>
> _______________________________________________
> Nel mailing list
> address@hidden
> http://www.nevrax.org/mailman/listinfo.cgi/nel
>