On a 32-bit cygwin I get
$ uname -a
CYGWIN_NT-6.1-WOW64 panamint 1.7.20(0.266/5/3) 2013-06-07 11:11 i686 Cygwin
$ find /usr -name Xlib.h -print
/usr/include/X11/Xlib.h
/usr/x86_64-pc-cygwin/sys-root/usr/include/X11/Xlib.h
/usr/lib/perl5/vendor_perl/5.14/i686-cygwin-threads-64int/Tk/pTk/Xlib.h
and using either gcc or x86_64-pc-cygwin-gcc I can build X apps, but if I
use i686-pc-cygwin-gcc I have some of the X headers but not (eg) Xlib.h.
On 64-bit cygwin despite having installed every packaged with cygwin32 in
its name as per the setup serach box I get
CYGWIN_NT-6.1 panamint 1.7.21(0.266/5/3) 2013-06-10 17:39 x86_64 Cygwin
$ find /usr -name Xlib.h -print
/usr/include/X11/Xlib.h
acn1@panamint usr
and so while gcc works i686-pc-cygwin-gcc will build console but not X
apps. However it "wants" to:
$ find /usr -name X.h -print
/usr/i686-pc-cygwin/sys-root/usr/include/X11/X.h
/usr/include/X11/X.h
since a cygwin32 X.h is provided.
My presumption is that this is just a transitory feature of the 64-bit
release (which is very welcome indeed - thanks so much) getting sorted
out. I had been trying using an explicit "--host=.." with a view to being
able to build both 32 and 64-bit versions of my code regardless of whether
I was on a 32 or 64-bit shell platform.
Arthur
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
