Hi,

I tried to apply your solution (on ns allinone 2.29), but when I run autoconf I 
recieve the following error:

configure.in:220 error: do not use LIBOBJS directly, use AC_LIBOBJS

Someone experienced the same? Thank's,

-Matt

Am Dienstag, 26. September 2006 02:00 schrieb [EMAIL PROTECTED]:
> Date: Mon, 25 Sep 2006 17:42:31 +0300
> From: " sinem k?kten " <[EMAIL PROTECTED]>
> Subject: Re: [ns] 7624: syntax error near unexpected token `)'
>         tcl8.3.2        configuration failed!
> To: [email protected]
> Message-ID:
>         <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> Hi everyone;
> I found a solution for my problem on a website and wrote this solution here
> to help everyone who faced the same problem:
> 
> *"checking system version (for dynamic loading)... ./configure: line
> 7624: syntax error near unexpected token ')'
> ./configure: line 7624: ' OSF*)'
> tcl8.3.2 configuration failed! Exiting ...
> Tcl is not part of the ns project. Please see www.Scriptics.com to see
> if they have a fix for your problem."
> 
> So after analyzing the configure files in the following directories I could
> find the culprit and the solution:
> 
> 
> tcl: file tcl8.x.x/unix/tcl.m4.
> tk: file tk8.x.x/unix/tcl.m4.
> otcl: file otcl-1.x/configure.in.
> 
> The line generating the problem was :
> 
> system=MP-RAS-`awk ' { print $3 } '/etc/.relid'`
> 
> The problem lies in how bash 3.1.x and 4.x.x parse the configure file. This
> will simply pass through bash 3.0.x and lower versions. So in order to make
> things work I changed the above line to:
> 
> system=MP-RAS-`awk ' { print $3 } '/etc/.relid`
> 
> You will have to take following steps in order to bring the changes into
> effect:
> Remove the second last character ( ' ) from the line and do this for all the
> three files above. Now after changing the configuration files you will have
> to delete older configure file and any cache if it exists in the respective
> folders. After that do not forget to run autoconf from command line in the
> respective folders to generate a fresh configure file.

Reply via email to