>> $ ( export PATH= ; /cygdrive/c/cygwin/bin/gcc-4.exe -v -E - < /dev/null )
I figured that cc1 depends on /usr/bin. A user invoking cc1 directly could
figure the missing dependency. Invoking cc1 indirectly from /usr/bin/gcc-4
without /usr/bin in PATH will break cc1 against expectation of /usr/bin/gcc-4
passing its containing directory to cc1 as a library search directory.
> $ cygcheck /usr/lib/gcc/i686-pc-cygwin/4.5.3/cc1.exe
> C:\cygwin\lib\gcc\i686-pc-cygwin\4.5.3\cc1.exe
> C:\cygwin\bin\cygcloog-0.dll
> C:\cygwin\bin\cyggcc_s-1.dll
> C:\cygwin\bin\cygwin1.dll
> C:\WINDOWS\system32\ADVAPI32.DLL
> C:\WINDOWS\system32\KERNEL32.dll
> C:\WINDOWS\system32\ntdll.dll
> C:\WINDOWS\system32\RPCRT4.dll
> C:\WINDOWS\system32\Secur32.dll
> C:\cygwin\bin\cyggmp-3.dll
> C:\cygwin\bin\cygppl_c-2.dll
> C:\cygwin\bin\cygppl-7.dll
> C:\cygwin\bin\cygstdc++-6.dll
> C:\cygwin\bin\cyggmpxx-4.dll
> C:\cygwin\bin\cygiconv-2.dll
> C:\cygwin\bin\cygintl-8.dll
> C:\cygwin\bin\cygmpc-1.dll
> C:\cygwin\bin\cygmpfr-1.dll
> C:\cygwin\bin\cygmpfr-4.dll
> C:\cygwin\bin\cygz.dll
>
> $ PATH= /usr/bin/cygcheck /usr/lib/gcc/i686-pc-cygwin/4.5.3/cc1.exe
> C:\cygwin\lib\gcc\i686-pc-cygwin\4.5.3\cc1.exe
> C:\WINDOWS\system32\KERNEL32.dll
> C:\WINDOWS\system32\ntdll.dll
> cygcheck: WARNING: PATH is not set
>
> cygcheck: track_down: could not find cygcloog-0.dll
>
> cygcheck: track_down: could not find cygwin1.dll
>
> cygcheck: track_down: could not find cyggmp-3.dll
>
> cygcheck: track_down: could not find cygiconv-2.dll
>
> cygcheck: track_down: could not find cygintl-8.dll
>
> cygcheck: track_down: could not find cygmpc-1.dll
>
> cygcheck: track_down: could not find cygmpfr-4.dll
>
> cygcheck: track_down: could not find cygppl_c-2.dll
>
> cygcheck: track_down: could not find cygz.dll
>
Cheers.
--
--
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
