[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: TclCL compilation error




Eddie

Thanks a lot for the workaround. I have successfully compiled
(and started to use) ns.

Murali

      <Eddie Hsu> writes:
>
>Hi Murali,
>
>I have just solved the problem a few days ago with the suggestions from 
>Tony Lee of NASA Ames. The following is the list of changes made on the 
>Sun server running SunOS 4.1.3_U1 and Gcc 2.8.1.
>
>Hope this helps.
>
>Eddie
>
>Enclosure.
>
>
>
>diff nilist.cc.org nilist.cc    
>42c42
><     t i = lnk->info;
>---
>>     T i = lnk->info;
>
>
>diff nilist.h.org nilist.h    
>96c96
><          { slist_Base::insert(new Tlink<T>(a));}
>---
>>          { slist_base::insert(new Tlink<T>(a));}
>98c98
><          { slist_Base::append(new Tlink<T>(a));}
>---
>>          { slist_base::append(new Tlink<T>(a));}
>
>
>diff tcp-fack.cc.org tcp-fack.cc    
>55c55
><       win = int((cwnd_ < wnd_ ? cwnd_ : wnd_) + wintrim_);
>---
>>       win = int((cwnd_ < wnd_ ? (double) cwnd_ : (double) wnd_) + wintrim_);
>
>
>diff tcp-rbp.cc.org tcp-rbp.cc    
>177c177
><               cwnd_ = MIN(cwnd_, rbwin_vegas);
>---
>>               cwnd_ = MIN(cwnd_, (TracedDouble) rbwin_vegas);
>346c346
><               cwnd_ = MIN(cwnd_, rbwin_reno);
>---
>>               cwnd_ = MIN(cwnd_, (TracedDouble) rbwin_reno);
>
>
> diff tcp-sack1.cc.org tcp-sack1.cc    
>65c65
><         return(int(cwnd_ < wnd_ ? cwnd_ : wnd_));
>---
>>         return(cwnd_ < wnd_ ? (int) cwnd_ : (int) wnd_);
>
>
>diff tcp.cc.org tcp.cc    
>398c398
><       return (int(cwnd_ < wnd_ ? cwnd_ : wnd_));
>---
>>       return (cwnd_ < wnd_ ? (int) cwnd_ : (int) wnd_);
>
>
>And in Tclcl:
>
>diff tclcl-mappings.h tclcl-mappings.h.org
>42d41
>< class Tcl;
>
>
>
>
>On Thu, 23 Apr 1998, kris wrote:
>
>> 
>> Eddie
>> 
>> I am trying to compile NS-AllInOne on Solaris 2.5.1 using gcc 2.8.1.
>> I get the same message that you had posted to the mailing list.
>> I wonder if you got any help from someone or found a way yourself.
>> 
>> I would much appreciate your reply to this query.
>> 
>> Thank you,
>> Murali Krishnaswamy
>> [email protected]
>