discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] Error installing wxPython on CYGWIN in Windows XP


From: Don Ward
Subject: Re: [Discuss-gnuradio] Error installing wxPython on CYGWIN in Windows XP
Date: Tue, 12 Jan 2010 10:36:51 -0500

Shabbir Ahmed wrote:

i. Down to business I am having errors in installing wxPython on CYGWIN in
Windows XP.

ii. Have been referring to
http://gnuradio.org/redmine/wiki/gnuradio/WxPythonCygwin for installation
guide.

iii. In the above, Steps 1, 2, 3, 4 and 4a works like a charm, I am still
attaching the output files in case you need to refer to them.

iv. In Steps 5 i get the following warnings and error:

In file included from ../src/msw/utils.cpp:56:
/usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../include/w32api/winsock.h:479:
error: declaration of C function ‘int select(int, _types_fd_set*,
_types_fd_set*, _types_fd_set*, const timeval*)’ conflicts with
/usr/include/sys/select.h:31: error: previous declaration ‘int select(int,
_types_fd_set*, _types_fd_set*, _types_fd_set*, timeval*)’ here

As Bob McGwier reported to the list on 3 Jan, there has been a major update to Cygwin, including a switch to gcc 4.3.4. I don't know if anyone has tried to install GNU Radio with the new version and I know that the instructions in the wiki have not been updated for the the new version.

The immediate problem is that both winsock.h and select.h have been included, leading to a conflict. You may be able to avoid this by editing build-local/lib/wx/include/msw-ansi-release-2.8/wx/setup.h so that HAVE_SYS_SELECT_H is undefined. Of course this might just be the first of many such errors that are not easily fixed.

Another possibility is that another include file in gcc 4.3.4 is including select.h. If that is the case, we will need to see what can be done.

It should be noted that the latest Cygwin FAQ states you can't use winsock functions in Cygwin (even though the winsock.h header file is included in the distribution). So they may have changed it so it just won't work.

Checking out the new Cygwin is on my list of things to do, but it probably won't happen soon.

Please let us know what you find.

-- Don W.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]