Thread: Re: [Plib-devel] patch for compiling on Solaris 10
Brought to you by:
sjbaker
From: Fay J. F Dr C. U. AFSEO/SK <joh...@eg...> - 2006-12-11 18:22:58
|
Vikas, I'm a little confused about the "socklen_t" problem you mention. I looked around the Linux system header files a bit and find #ifndef __socklen_t_defined typedef __socklen_t socklen_t #endif The only place I see "socklen_t" used in PLIB is in "netSocket.cxx", where it is defined to be "int" under MSVC if it has not already been defined. As such, perhaps the problem lies with the "configure" adding that flag to your compile line. Does anybody know what causes it? I am similarly confused by the addition of "(char *)" to the "strstr" call in netChat.cxx. The "strstr" function already returns a value of type "char *" so the cast should be unnecessary. Is there something about the Sun Studio 11 compiler that is nonstandard? If there is, I will certainly be willing to add the explicit cast, but if not I would just as soon leave it out. (Perhaps we should use a "#ifdef UL_BB" block here.) John F. Fay Technical Fellow Jacobs/Sverdrup TEAS Group 850-883-1294 -----Original Message----- From: pli...@li... [mailto:pli...@li...] On Behalf Of Vikas N Kumar Sent: Sunday, December 10, 2006 2:24 AM To: pli...@li... Subject: [Plib-devel] patch for compiling on Solaris 10 Hi To compile with the Sun Studio 11 compilers on Solaris 10 on a SPARC I had to do the following changes to make plib compile cleanly. When I run configure, the flag "-Dsocklen_t=int" is added to my compile line for all files. Hence I have to undefine it in 2 files to get them to compile properly since socklen_t is defined as a typedef of "uint32_t" in those files. Regards, Vikas <snip> |
From: Vikas N K. <vik...@us...> - 2006-12-11 19:17:18
|
Hi John, The configure script added the -Dsocklen_t=int in my compile line. Why it did that I have no idea, I did not look. I will look at it and let you know. The sun studio 11 C++ compiler was giving an error in saying strstr was returning a const char*. I guess that is how it is on Solaris 10. I shall look into that too. You could however use the UL_BB #ifdefs and do it instead of the explicit cast. Even for the socklen_t=int problem, one could test for UL_SOLARIS and then do the #undef statements as given in the patch as opposed to undefining it without any Operating system checks. Regards, Vikas > From: Fay John F Dr CTR USAF AFSEO/SK <joh...@eg...> > Subject: Re: [Plib-devel] patch for compiling on Solaris 10 > Vikas, > > I'm a little confused about the "socklen_t" problem you mention. I > looked around the Linux system header files a bit and find > > #ifndef __socklen_t_defined > typedef __socklen_t socklen_t > #endif > > The only place I see "socklen_t" used in PLIB is in "netSocket.cxx", where > it is defined to be "int" under MSVC if it has not already been defined. As > such, perhaps the problem lies with the "configure" adding that flag to your > compile line. Does anybody know what causes it? > > I am similarly confused by the addition of "(char *)" to the > "strstr" call in netChat.cxx. The "strstr" function already returns a value > of type "char *" so the cast should be unnecessary. Is there something > about the Sun Studio 11 compiler that is nonstandard? If there is, I will > certainly be willing to add the explicit cast, but if not I would just as > soon leave it out. (Perhaps we should use a "#ifdef UL_BB" block here.) > > John F. Fay > Technical Fellow > Jacobs/Sverdrup TEAS Group > 850-883-1294 -- http://www.vikaskumar.org/ |
From: Vikas N K. <vik...@us...> - 2006-12-12 04:35:32
|
Hi John, The socklen_t problem is occurring since you have the following in your configure.in Here are the details in config.log for the Sun Studio 11 compiler running on Solaris 10. socklen_t is defined in /usr/include/sys/socket.h but yet, the test below (at the end of the email) fails. Why? Because of the "-Wall" option. Sun Studio 11 compilers on Solaris 10 do not support the -Wall option. Hence the exit code $? is 1 because of which socklen_t gets defined as int instead of size_t or uint32_t. You could try "+w2" for a certain level of warnings. In any case, we should not check for socklen_t since it is defined on most systems. This checking is very antiquated on Unixes. If you look at configure.in the check has been added for Unix98. Even if it is defined in the header files, if socklen_t gets into the compile line as -Dsocklen_t=int or -Dsocklen_t=size_t, we will still have to undefine it before it is typedef'd in <netinet/in.h> Regarding strstr(), on Solaris10 in the header files the strstr() function returns a const char* for __cplusplus>=199711L which apparently is some C++ standard (ISO/IEC 14882:1998) (lifted this off the header file, i.e. in /usr/include/iso/string_iso.h) The header file /usr/include/string.h uses this iso/string_iso.h header file for all its string functions. Regards, Vikas configure:7169: checking for socklen_t configure:7191: /opt/SUNWspro/bin/cc -c -g -Wall -I/export/home/vicash/FLIGHTGEAR/run/include conftest.c >&5 cc: illegal option -Wall configure:7197: $? = 1 configure: failed program was: | /* confdefs.h. */ | | #define PACKAGE_NAME "" | #define PACKAGE_TARNAME "" | #define PACKAGE_VERSION "" | #define PACKAGE_STRING "" | #define PACKAGE_BUGREPORT "" | #define PACKAGE "plib" | #define VERSION "1.8.4" | #ifdef __cplusplus | extern "C" void exit (int); | #endif | #define HAVE_LIBPTHREAD 1 | #define HAVE_LIBGL 1 | #define HAVE_LIBDL 1 | #define STDC_HEADERS 1 | #define HAVE_SYS_TYPES_H 1 | #define HAVE_SYS_STAT_H 1 | #define HAVE_STDLIB_H 1 | #define HAVE_STRING_H 1 | #define HAVE_MEMORY_H 1 | #define HAVE_STRINGS_H 1 | #define HAVE_INTTYPES_H 1 | #define HAVE_STDINT_H 1 | #define HAVE_UNISTD_H 1 | /* end confdefs.h. */ | | #include <sys/types.h> | #include <sys/socket.h> | socklen_t apa; | | int | main () | { | | ; | return 0; | } configure:7240: /opt/SUNWspro/bin/cc -c -g -Wall -I/export/home/vicash/FLIGHTGEAR/run/include conftest.c >&5 cc: illegal option -Wall configure:7246: $? = 1 configure: failed program was: | /* confdefs.h. */ | | #define PACKAGE_NAME "" | #define PACKAGE_TARNAME "" | #define PACKAGE_VERSION "" | #define PACKAGE_STRING "" | #define PACKAGE_BUGREPORT "" | #define PACKAGE "plib" | #define VERSION "1.8.4" | #ifdef __cplusplus | extern "C" void exit (int); | #endif | #define HAVE_LIBPTHREAD 1 | #define HAVE_LIBGL 1 | #define HAVE_LIBDL 1 | #define STDC_HEADERS 1 | #define HAVE_SYS_TYPES_H 1 | #define HAVE_SYS_STAT_H 1 | #define HAVE_STDLIB_H 1 | #define HAVE_STRING_H 1 | #define HAVE_MEMORY_H 1 | #define HAVE_STRINGS_H 1 | #define HAVE_INTTYPES_H 1 | #define HAVE_STDINT_H 1 | #define HAVE_UNISTD_H 1 | /* end confdefs.h. */ | | #include <sys/types.h> | #include <sys/socket.h> | int accept (int, struct sockaddr *, size_t *); | | int | main () | { | | ; | return 0; | } configure:7273: result: int |
From: Fay J. F Dr C. U. AFSEO/SK <joh...@eg...> - 2006-12-14 21:33:21
|
Gentlemen, It appears from the message below that the "configure" test for "socklen_t" fails on Sun Studio 11 compilers because they do not support "-Wall". I see three options: (1) Drop the "-Wall" flag. I do not like this option because I like the compiler to warn me when things are iffy. (2) Quit checking for "socklen_t" in the "configure" step. Vijay Kumar, who flagged the error, supports this option. The reasoning is that "socklen_t" is pretty much universal by now. (3) Make the "-Wall" flag system-dependent and don't use it Sun Studio 11 compilers. Is such a thing possible? John F. Fay Technical Fellow Jacobs/Sverdrup TEAS Group 850-883-1294 -----Original Message----- From: pli...@li... [mailto:pli...@li...] On Behalf Of Vikas N Kumar Sent: Monday, December 11, 2006 10:36 PM To: pli...@li... Subject: Re: [Plib-devel] patch for compiling on Solaris 10 Hi John, The socklen_t problem is occurring since you have the following in your configure.in Here are the details in config.log for the Sun Studio 11 compiler running on Solaris 10. socklen_t is defined in /usr/include/sys/socket.h but yet, the test below (at the end of the email) fails. Why? Because of the "-Wall" option. Sun Studio 11 compilers on Solaris 10 do not support the -Wall option. Hence the exit code $? is 1 because of which socklen_t gets defined as int instead of size_t or uint32_t. You could try "+w2" for a certain level of warnings. In any case, we should not check for socklen_t since it is defined on most systems. This checking is very antiquated on Unixes. If you look at configure.in the check has been added for Unix98. Even if it is defined in the header files, if socklen_t gets into the compile line as -Dsocklen_t=int or -Dsocklen_t=size_t, we will still have to undefine it before it is typedef'd in <netinet/in.h> Regarding strstr(), on Solaris10 in the header files the strstr() function returns a const char* for __cplusplus>=199711L which apparently is some C++ standard (ISO/IEC 14882:1998) (lifted this off the header file, i.e. in /usr/include/iso/string_iso.h) The header file /usr/include/string.h uses this iso/string_iso.h header file for all its string functions. Regards, Vikas configure:7169: checking for socklen_t configure:7191: /opt/SUNWspro/bin/cc -c -g -Wall -I/export/home/vicash/FLIGHTGEAR/run/include conftest.c >&5 cc: illegal option -Wall configure:7197: $? = 1 configure: failed program was: | /* confdefs.h. */ | | #define PACKAGE_NAME "" | #define PACKAGE_TARNAME "" | #define PACKAGE_VERSION "" | #define PACKAGE_STRING "" | #define PACKAGE_BUGREPORT "" | #define PACKAGE "plib" | #define VERSION "1.8.4" | #ifdef __cplusplus | extern "C" void exit (int); | #endif | #define HAVE_LIBPTHREAD 1 | #define HAVE_LIBGL 1 | #define HAVE_LIBDL 1 | #define STDC_HEADERS 1 | #define HAVE_SYS_TYPES_H 1 | #define HAVE_SYS_STAT_H 1 | #define HAVE_STDLIB_H 1 | #define HAVE_STRING_H 1 | #define HAVE_MEMORY_H 1 | #define HAVE_STRINGS_H 1 | #define HAVE_INTTYPES_H 1 | #define HAVE_STDINT_H 1 | #define HAVE_UNISTD_H 1 | /* end confdefs.h. */ | | #include <sys/types.h> | #include <sys/socket.h> | socklen_t apa; | | int | main () | { | | ; | return 0; | } configure:7240: /opt/SUNWspro/bin/cc -c -g -Wall -I/export/home/vicash/FLIGHTGEAR/run/include conftest.c >&5 cc: illegal option -Wall configure:7246: $? = 1 configure: failed program was: | /* confdefs.h. */ | | #define PACKAGE_NAME "" | #define PACKAGE_TARNAME "" | #define PACKAGE_VERSION "" | #define PACKAGE_STRING "" | #define PACKAGE_BUGREPORT "" | #define PACKAGE "plib" | #define VERSION "1.8.4" | #ifdef __cplusplus | extern "C" void exit (int); | #endif | #define HAVE_LIBPTHREAD 1 | #define HAVE_LIBGL 1 | #define HAVE_LIBDL 1 | #define STDC_HEADERS 1 | #define HAVE_SYS_TYPES_H 1 | #define HAVE_SYS_STAT_H 1 | #define HAVE_STDLIB_H 1 | #define HAVE_STRING_H 1 | #define HAVE_MEMORY_H 1 | #define HAVE_STRINGS_H 1 | #define HAVE_INTTYPES_H 1 | #define HAVE_STDINT_H 1 | #define HAVE_UNISTD_H 1 | /* end confdefs.h. */ | | #include <sys/types.h> | #include <sys/socket.h> | int accept (int, struct sockaddr *, size_t *); | | int | main () | { | | ; | return 0; | } configure:7273: result: int ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ plib-devel mailing list pli...@li... https://lists.sourceforge.net/lists/listinfo/plib-devel |
From: Vikas N K. <vik...@us...> - 2006-12-15 15:45:39
|
Hi John, my comments below. On 12/14/06, Fay John F Dr CTR USAF AFSEO/SK <joh...@eg...> wrote: > It appears from the message below that the "configure" test for > "socklen_t" fails on Sun Studio 11 compilers because they do not support > "-Wall". I see three options: > > (1) Drop the "-Wall" flag. I do not like this option because I like the > compiler to warn me when things are iffy. Actually John, the "-Wall" flag is required for the GNU compilers to show all the warnings. The Sun Studio 11 compilers show all the warnings by default, and the "-Wall" flag is not accepted. Hence, you might just need to keep the "-Wall" flag for GNU compilers. > > (2) Quit checking for "socklen_t" in the "configure" step. Vijay Kumar, > who flagged the error, supports this option. The reasoning is that > "socklen_t" is pretty much universal by now. I am not sure about Windows & *BSDs in this regard. socklen_t is present in Linux and Solaris for sure. If someone has a *BSD or Windows and can check for the presence of socklen_t in " netinet/in.h" and "sys/socket.h" then we can remove it from the configure.in script. Is plib supported on IRIX too ? I have an IRIX 6.2 system at home but I am not sure what version of IRIX you currently support. I can check there for socklen_t. > > (3) Make the "-Wall" flag system-dependent and don't use it Sun Studio 11 > compilers. Is such a thing possible? yes this should be possible. If you want I can look into doing this. Regards, Vikas |
From: Bert D. <dri...@pl...> - 2006-12-15 16:16:24
|
On Thu, 14 Dec 2006, Fay John F Dr CTR USAF AFSEO/SK wrote: > It appears from the message below that the "configure" test for > "socklen_t" fails on Sun Studio 11 compilers because they do not support > "-Wall". I see three options: > > (1) Drop the "-Wall" flag. I do not like this option because I like the > compiler to warn me when things are iffy. > > (2) Quit checking for "socklen_t" in the "configure" step. Vijay Kumar, > who flagged the error, supports this option. The reasoning is that > "socklen_t" is pretty much universal by now. > > (3) Make the "-Wall" flag system-dependent and don't use it Sun Studio 11 > compilers. Is such a thing possible? My two cents: dropping the check for socklen_t is not the desirable solution. It was obviously put there for a reason, and PLIB is used on platforms some of us haven't even heard of. So unless someone recalls what platforms were unbroken by adding that check, I would not call dropping it a safe change. Obviously, when a compiler barfs on -Wall, we should not add -Wall to the compiler options. There is autoconf magic to check for GCC and set -Wall as required (I seem to recall that the AC_PROG_CPP does the appropriate magic). |
From: Fay J. F Dr C. U. AFSEO/SK <joh...@eg...> - 2006-12-14 22:08:50
|
Vikas, I've not looked at the "socklen_t" problem yet. I fixed the "strstr" typecast problem by adding a conditional compilation--it seems that the Borland compiler does the same thing, so I set the "UL_BB" flag--but changed its name to "UL_EXPLICIT_CASTS". John F. Fay Technical Fellow Jacobs/Sverdrup TEAS Group 850-883-1294 -----Original Message----- From: pli...@li... [mailto:pli...@li...] On Behalf Of Vikas N Kumar Sent: Monday, December 11, 2006 1:17 PM To: pli...@li... Subject: Re: [Plib-devel] patch for compiling on Solaris 10 Hi John, The configure script added the -Dsocklen_t=int in my compile line. Why it did that I have no idea, I did not look. I will look at it and let you know. The sun studio 11 C++ compiler was giving an error in saying strstr was returning a const char*. I guess that is how it is on Solaris 10. I shall look into that too. You could however use the UL_BB #ifdefs and do it instead of the explicit cast. Even for the socklen_t=int problem, one could test for UL_SOLARIS and then do the #undef statements as given in the patch as opposed to undefining it without any Operating system checks. Regards, Vikas > From: Fay John F Dr CTR USAF AFSEO/SK <joh...@eg...> > Subject: Re: [Plib-devel] patch for compiling on Solaris 10 > Vikas, > > I'm a little confused about the "socklen_t" problem you mention. I > looked around the Linux system header files a bit and find > > #ifndef __socklen_t_defined > typedef __socklen_t socklen_t > #endif > > The only place I see "socklen_t" used in PLIB is in "netSocket.cxx", where > it is defined to be "int" under MSVC if it has not already been defined. As > such, perhaps the problem lies with the "configure" adding that flag to your > compile line. Does anybody know what causes it? > > I am similarly confused by the addition of "(char *)" to the > "strstr" call in netChat.cxx. The "strstr" function already returns a value > of type "char *" so the cast should be unnecessary. Is there something > about the Sun Studio 11 compiler that is nonstandard? If there is, I will > certainly be willing to add the explicit cast, but if not I would just as > soon leave it out. (Perhaps we should use a "#ifdef UL_BB" block here.) > > John F. Fay > Technical Fellow > Jacobs/Sverdrup TEAS Group > 850-883-1294 -- http://www.vikaskumar.org/ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ plib-devel mailing list pli...@li... https://lists.sourceforge.net/lists/listinfo/plib-devel |
From: Fay J. F Dr C. U. AFSEO/SK <joh...@eg...> - 2006-12-15 17:52:16
|
Vikas, I have a Windows box and it does not have "sys/socket.h" at all. I do not have Cygwin and so have not been able to check that. Of note, Windows does not define "socklen_t" at all. I think out best bet would be to make the "-Wall" flag system-dependent. It is necessary on some systems and creates an error on other systems, so the most logical step would (in my mind) be to make it system-dependent. Do please look into how we do this. John F. Fay Technical Fellow Jacobs/Sverdrup TEAS Group 850-883-1294 -----Original Message----- From: pli...@li... [mailto:pli...@li...] On Behalf Of Vikas N Kumar Sent: Friday, December 15, 2006 9:46 AM To: PLIB Developers Subject: Re: [Plib-devel] patch for compiling on Solaris 10 Hi John, my comments below. On 12/14/06, Fay John F Dr CTR USAF AFSEO/SK <joh...@eg...> wrote: > It appears from the message below that the "configure" test for > "socklen_t" fails on Sun Studio 11 compilers because they do not support > "-Wall". I see three options: > > (1) Drop the "-Wall" flag. I do not like this option because I like the > compiler to warn me when things are iffy. Actually John, the "-Wall" flag is required for the GNU compilers to show all the warnings. The Sun Studio 11 compilers show all the warnings by default, and the "-Wall" flag is not accepted. Hence, you might just need to keep the "-Wall" flag for GNU compilers. > > (2) Quit checking for "socklen_t" in the "configure" step. Vijay Kumar, > who flagged the error, supports this option. The reasoning is that > "socklen_t" is pretty much universal by now. I am not sure about Windows & *BSDs in this regard. socklen_t is present in Linux and Solaris for sure. If someone has a *BSD or Windows and can check for the presence of socklen_t in " netinet/in.h" and "sys/socket.h" then we can remove it from the configure.in script. Is plib supported on IRIX too ? I have an IRIX 6.2 system at home but I am not sure what version of IRIX you currently support. I can check there for socklen_t. > > (3) Make the "-Wall" flag system-dependent and don't use it Sun Studio 11 > compilers. Is such a thing possible? yes this should be possible. If you want I can look into doing this. Regards, Vikas ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ plib-devel mailing list pli...@li... https://lists.sourceforge.net/lists/listinfo/plib-devel |
From: Vikas N K. <vik...@us...> - 2006-12-15 19:54:55
|
Hi John, Below is the patch for setting the "-Wall" flag to null if the compiler is not GCC. It works, for both Linux and Solaris. Regards, Vikas Index: configure.in =================================================================== --- configure.in (revision 2112) +++ configure.in (working copy) @@ -346,6 +346,10 @@ if test "x$CXX" = "xicpc" || test "x$CXX" = "xicc"; then WFLAG="-w1" fi + if test "x$GCC" != xyes; then + # if the compiler is not GCC we reset WFLAG to null for safety + WFLAG="" + fi ;; esac |
From: Fay J. F Dr C. U. AFSEO/SK <joh...@eg...> - 2006-12-15 20:12:08
|
Vikas, OK, I have put it into SVN. Please check that I have done it correctly. John F. Fay Technical Fellow Jacobs/Sverdrup TEAS Group 850-883-1294 -----Original Message----- From: pli...@li... [mailto:pli...@li...] On Behalf Of Vikas N Kumar Sent: Friday, December 15, 2006 1:55 PM To: PLIB Developers Subject: Re: [Plib-devel] patch for compiling on Solaris 10 Hi John, Below is the patch for setting the "-Wall" flag to null if the compiler is not GCC. It works, for both Linux and Solaris. Regards, Vikas Index: configure.in =================================================================== --- configure.in (revision 2112) +++ configure.in (working copy) @@ -346,6 +346,10 @@ if test "x$CXX" = "xicpc" || test "x$CXX" = "xicc"; then WFLAG="-w1" fi + if test "x$GCC" != xyes; then + # if the compiler is not GCC we reset WFLAG to null for safety + WFLAG="" + fi ;; esac ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ plib-devel mailing list pli...@li... https://lists.sourceforge.net/lists/listinfo/plib-devel |
From: Vikas N K. <vik...@us...> - 2006-12-16 02:34:53
|
Hi John, Thanks for doing that. It fixes the socklen_t problem as well. Regards, Vikas On 12/15/06, Fay John F Dr CTR USAF AFSEO/SK <joh...@eg...> wrote: > > > > Vikas, > > OK, I have put it into SVN. Please check that I have done it > correctly. > > John F. Fay > Technical Fellow > Jacobs/Sverdrup TEAS Group > 850-883-1294 > > -----Original Message----- > From: pli...@li... > [mailto:pli...@li...] On Behalf > Of Vikas N Kumar > > Sent: Friday, December 15, 2006 1:55 PM > To: PLIB Developers > Subject: Re: [Plib-devel] patch for compiling on Solaris 10 > > > Hi John, > Below is the patch for setting the "-Wall" flag to null if the > compiler is not GCC. It works, for both Linux and Solaris. > > Regards, > Vikas > > > Index: configure.in > =================================================================== > --- configure.in (revision 2112) > +++ configure.in (working copy) > @@ -346,6 +346,10 @@ > if test "x$CXX" = "xicpc" || test "x$CXX" = "xicc"; then > WFLAG="-w1" > fi > + if test "x$GCC" != xyes; then > + # if the compiler is not GCC we reset WFLAG to null for safety > + WFLAG="" > + fi > ;; > esac > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > plib-devel mailing list > pli...@li... > https://lists.sourceforge.net/lists/listinfo/plib-devel > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > plib-devel mailing list > pli...@li... > https://lists.sourceforge.net/lists/listinfo/plib-devel > > > -- http://www.vikaskumar.org/ |