This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Empty include file on samba share
Fabian Cenedese wrote:
> make: Entering directory `Q:/Machine/Control'
> gcc.exe -mcpu=603 -c -g -fno-exceptions -fno-rtti -Wall -Wconversion -Wsign-compare -O2 -fverbose-asm \
> -S \
> -IN:/IMD/Include32 -IQ:/Machine/Control/firmware/info_ppc/inc -IQ:/Machine/Control/firmware/info_ppc/hal -IQ:/Machine/Control/os/inos/inc -IQ:/Machine/Control/os/inco/inc -IQ:/Machine/Control/os/inos/hal -IQ:/Machine/Control/application/syscalls/include -IQ:/Machine/Control/application/handling/include -IQ:/Machine/Control/application/axes/include -IQ:/Machine/Control/application/syscalls/hal -IQ:/Machine/Common/include \
> -DPPC603 -DINFO_SAM -DINOS_OLD_BITS -D_DEBUG -DINOS_NG -DINOS_LIBC_REENTRANCY_SUPPORT \
> Q:/Machine/Control/Application/Axes/Source/CAxis.cpp -o Q:/Machine/Control/bin32/CAxis.s
> In file included from Q:/Machine/Control/os/inos/inc/CINOSProcessImage.h:194,
> from Q:/Machine/Control/firmware/info_ppc/inc/info_acs.h:198,
> from /cygdrive/c/Temp/cc30zQvv.ii:49:
> Q:/Machine/Control/os/inos/inc/CINOSAdcChannel.h:54: parse error before `{'
> ...
> 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 take a look at the corruption? It might just
give us a clue.
cheers,
DaveK
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/