[Ns-developers] [Bug 452] Cygwin won't build NSC

[Sam Jansen]

Moving to mailing list...
Is there any sort of official line on support of cygwin? I haven't really
been following the mailing list for a while so I could have missed this.

Certainly putting in reasonable error messages at configure time seems like
a good idea in the case of NSC. I'll be happy to send a patch if there is
existing practice of doing this I can copy from ;)


2008/12/19 <code at nsnam.ece.gatech.edu>

> http://www.nsnam.org/bugzilla/show_bug.cgi?id=452
>
>
>
>
>
> --- Comment #2 from Gavin Weng <gavinweng at gmail.com>  2008-12-20 02:59:18
> EDT ---
> Actually, that's the reason why I posted it again since it behaves a lot
> different. It comes out to me that maybe this could be fixed.
>
> I suggest enable-nsc be notified NOT supporting cygwin, just as the module
> "python bindings" does, which was also reported by me with the resolution
> WONTFIX.
>
> > Gavin, you reported that NSC doesn't work in cygwin in bug 360. Is still
> > doesn't work, and as I reported there, using a VM is the best solution to
> > running it.
> > Unfortunately there are some very difficult technical problems to solve
> to make
> > NSC work under Cygwin and I do not know of anyone with the time to work
> on them
> > (not me for sure.)
> > You can still build ns-3 without NSC; just do not enable NSC at compile
> time.
> > The particular symptom you report looks a bit different. It is probably a
> good
> > idea for the ns-3 build system to check for NSC+Cygwin and respond with a
> > reasonable error message. That is probably a feature request rather than
> a bug.
>
>
> --
> Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
> You are the assignee for the bug.
>