>> And many other errors coming from unknown items because of seemingly not
>> or badly read include files.
>>
>> However the same line works fine if the project lies on a local drive.
>
> Have you tried adding "--save-temps" to your CFLAGS so that you can capture
>the pre-processor output and ta
>> PROBLEM - Still get 'bash' is not recognized as an internal or external
>> command.
>>
>> Any suggestions please?
>
> Tell us what's going on because we're not mind-readers?
>
> Actually some of us are. *puts fingers to forehead, closes eyes, frowns
>with concentration* I'm getting somethi
>But it seems there is no alternative. I had not expected that Windows would
>not log such events, like starting up or having some user logged in...
Windows does log such events in the system protocol/event log :)
But I don't know if you can get this info from cygwin...
bye Fabi
--
Unsubscrib
At 19:34 09.01.2009 +, Dave Korn wrote:
> Have you tried adding "--save-temps" to your CFLAGS so that you can capture
>the pre-processor output and take a look at the corruption? It might just
>give us a clue.
I have tried a different file and will show the include structure as well as
the
At 11:28 08.01.2009 -0500, Larry Hall (Cygwin) wrote:
>Fabian Cenedese wrote:
>>At 12:22 07.01.2009 -0500, Larry Hall (Cygwin) wrote:
>>>Fabian Cenedese wrote:
>>>>However if the whole C++ project is moved from the local drive to a
>>>>share (samba, proba
At 12:22 07.01.2009 -0500, Larry Hall (Cygwin) wrote:
>Fabian Cenedese wrote:
>>However if the whole C++ project is moved from the local drive to a
>>share (samba, probably also windows) the compilation may fail with
>>various errors. The main problem seems to be that include
Hi
I have a problem that may be cygwin or not. I'll just ask here if anybody knows
something (or to show me some better place to go to).
We use a quite old cross-gcc (2.95.2), built with cygwin and running on various
windows (since NT on to vista). The currently used cygwin is version
1.5.19-cr-0
7 matches
Mail list logo
