I am trying to compile sctplib-1.0.0-pre18.tar.gz on the cygwin platform. The ./configure script indicates that the following options are available:Does this mean that you are testing the sctplib on a Windows machine? If you get it up and running, please send the patches.
There is NO way using the sctplib without the glib. The MacOSX stuff does not necessary apply to your environment. The FLAGS are specific for the Apple gcc. In the glib distribution there is a README.win32. Have you looked at this?root@LIVINGROOM /cygdrive/e/phill/sctp/sctplib-1.0.0-pre18...
$ ./configure --help
--disable-ipv6 turn off IPv6 support...
--disable-gtktest Do not try to compile and run a test GTK program...
--disable-glibtest Do not try to compile and run a test GLIB progra
So I tried with:
./configure --disable-ipv6 --disable-gtktest --disable-glibtest
However, the --disable-glibtest option seems to be ignored. I am not an autoconf expert, but it doesn't appear that it is even tested for in the script.
So, I get messages similar to those encountered by the Mac OS X person that Michael advised several weeks ago. That person asked:
Is really GLIB required?
and Michael responded:
The glib is really needed. To install it do the following
but, that does not seem to be an option for me. (Tried it, failed.)
So I'm curious... perhaps I misunderstand the purpose of glib, but it appears to be part of the Gnome GUI. Why is a GUI library required to build a transport protocol implementation (assuming I don't want or need any of the sample applications?) Is there set of convenience functions (not related to graphics) that are being used in the core sctplib? Is there any reasonable way around this?The gnome guys use the glib and the gtklib. The gtklib is the X11 stuff, so it is not needed. The glib provides implementations of single linked lists, double linked list, hash tables and so on. That stuff is quite helpful when building a transport layer protocol and the glib is running on a lot of platforms. So it does not limit the portability. That is why we have chosen to use it.
Or as an alternative, has anyone been successful in compiling glib stuff under cygwin? (Michael's trick for Mac OS X of copying the more recent /usr/share/libtool/config.* files doesn't seem to work.. those files don't exist under cygwin).As I mentioned above, the hints are specific for MacOSX, which has a FreeBSD base. So it does not apply to Windows.
Michael.Tuexen AT micmac.franken.de
Any help or suggestions would be appreciated.
Phill
_______________________________________________
discussion mailing list
discussion AT sctp.de
http://www.sctp.de/mailman/listinfo/discussion
Archive powered by MHonArc 2.6.19+.