Re: Dependencies: non-standard path to system headers

2008-07-03 Thread Ineiev
Hello, Brian Thank you for your hint on `make' from CVS. It really works. On 7/2/08, Brian Dessent <[EMAIL PROTECTED]> wrote: > I never said that fopen("c:/foo") wouldn't work, but it's because the > Cygwin APIs simply pass-thru arguments to the underlying Win32 APIs that > don't look like POSI

Re: Dependencies: non-standard path to system headers

2008-07-02 Thread Brian Dessent
[EMAIL PROTECTED] wrote: > Some strictly positive amount of interoperability exists. > When I gcc c:/cygwin/home/15-6-1/tmp/m/sample.c, it > produced a.exe (gcc 'c:\cygwin\home\15-6-1\tmp\m\sample.c', too). > > sample.c contained > #include > int > main(void) > {FILE*f=fopen("c:\\sample.txt","w")

Re: Dependencies: non-standard path to system headers

2008-07-02 Thread ineiev
On 7/1/08, Brian Dessent <[EMAIL PROTECTED]> wrote: >The essential point is that using native Win32 tools with Cygwin causes >problems. This is because Cygwin is designed to closely emulate a POSIX >environment, and the tools aren't equipped to deal with Win32 paths with >drive letters. This is n

Re: Dependencies: non-standard path to system headers

2008-07-02 Thread ineiev
Hello, On 7/1/08, Stepan Kasal <[EMAIL PROTECTED]> wrote: >perhaps my first question is a bit naive, but why does this confuse >your make? make says something like this: Makefile:1: *** multiple target patterns. Stop. As I understand, it interprets the input as targets : target_pattern : \ so

Re: Dependencies: non-standard path to system headers

2008-07-01 Thread Brian Dessent
Ineiev wrote: > WinAVR gcc produces dependencies that shall confuse `make', > like these: The essential point is that using native Win32 tools with Cygwin causes problems. This is because Cygwin is designed to closely emulate a POSIX environment, and the tools aren't equipped to deal with Win32

Re: Dependencies: non-standard path to system headers

2008-07-01 Thread Stepan Kasal
Hello, On Tue, Jul 01, 2008 at 06:12:15AM +, Ineiev wrote: > WinAVR gcc produces dependencies that shall confuse `make', > like these: > > sampler.o: ../../../stribog/sw/auxilia/coil/sampler.c \ > c:/winavr-20080512/lib/gcc/../../avr/include/avr/io.h \ > c:/winavr-20080512/lib/gcc/../../a

Dependencies: non-standard path to system headers

2008-06-30 Thread Ineiev
Some time ago I tested build process of my project on cygwin. Some parts of the project are AVR-hosted, so I checked if WinAVR were capable to build them. WinAVR gcc produces dependencies that shall confuse `make', like these: sampler.o: ../../../stribog/sw/auxilia/coil/sampler.c \ c:/winavr-20