Hi,
did you check the include path of the compiler in use?
Erich
Shay wrote:
Hi
I am sorry to ask this but I really searched before.
I would like to compile a C program but includes are not found :
The file 'stdio.h' cannot be opened
The file 'stdarg.h' cannot be opened
I installed cygw
Hi
I am sorry to ask this but I really searched before.
I would like to compile a C program but includes are not found :
The file 'stdio.h' cannot be opened
The file 'stdarg.h' cannot be opened
I installed cygwin with the mingw runtime.
stdio.h is present in :
cygwin\include
cygwin\usr\
Bill C. Riemers wrote:
> Not necessarily. Not every application is designed to work across different
> platforms.
Fine. In that case, read answer #1:
>> Cygwin != Linux.
Your program is obviously doomed, since you intend it to run only on
Linux. Remember, Cygwin isn't a linux kernel with linu
> It doesn't. Cygwin != Linux.
>
> Also, AFAIK, if a Linux application is directly including linux/*, it is
> broken.
Not necessarily. Not every application is designed to work across different
platforms. Sometimes a programmer may choice to sacrifice portability for
some other advantage. In f
On Sat, 15 Nov 2003, Martin Bündgens wrote:
> i started using cygwin today and i got a small problem with some C progs.
> How does Cygwin compensate file includes like linux/ip.h or linux/tcp.h.
> Thanks for your help.
>
It doesn't. Cygwin != Linux.
Also, AFAIK, if a Linux application is directl
Hallo,
i started using cygwin today and i got a small problem with some C progs.
How does Cygwin compensate file includes like linux/ip.h or linux/tcp.h.
Thanks for your help.
Regards,
Martin Bündgens.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: h
Brian Ford wrote:
These questions are mainly directed at Andre Bleau (Cygwin's OpenGL
maintainer).
I am glad that the ambiguity in gcc include search paths has been
resolved. However, the OpenGL includes in w32api/GL are from Mesa, and
are thus more complete and up-to-date.
Well, I hope that Earn
These questions are mainly directed at Andre Bleau (Cygwin's OpenGL
maintainer).
I am glad that the ambiguity in gcc include search paths has been
resolved. However, the OpenGL includes in w32api/GL are from Mesa, and
are thus more complete and up-to-date.
What are the long term plans, if any, f
I'd like to report that the problem that I reported about gcc 3.2 in:
http://sources.redhat.com/ml/cygwin/2003-02/msg01556.html
is no longer present with gcc 3.3.1
For those who might care, it was a problem of include files in
/usr/include/w32api wrongly taking precedence over those in /usr/in
9 matches
Mail list logo
