This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Problems with path resolution
I am also seeing some strange path problems with 1.3.2
I say
ls -l /cygdrive/f/foo
and it lists it.
I say
file /cygdrive/f/foo
and I get an error 'No such file or directory'
foo is some binary file.
I could even be in the same directory, and it wont make a difference.
But since this only affect file with 'x' bit set on them, and I know allready there is
a problem with setting 'x' on files (it does not work), I guess this is related to the same
thing. of course all of this might not be related to your problem :)
Nasser
----- Original Message -----
From: "Churchill, Dan (MN65)" <churchill_dan@htc.honeywell.com>
To: <cygwin@cygwin.com>
Sent: Friday, August 24, 2001 3:24 PM
Subject: Problems with path resolution
> Ladies and Gentlemen,
>
> I'm experiencing a very odd problem with path resolution on the latest
> version of Cygwin, DLL: 1.3.2, installer 2.78.2.3
>
> Basically, the problem is the following: when we run a compiler, -I options
> which include cygwin paths aren't resolving, leading to include files being
> missed and dying compiles.
>
> Attached are the mount tables and an example of the problem...
>
> C:\cygwin\bin on /usr/bin type system (textmode)
> C:\cygwin\lib on /usr/lib type system (textmode)
> \\mn65-bay2\C on /Owen/c type user (textmode)
> C:\cygwin on / type system (textmode)
> c: on /c type user (binmode)
>
> Compiling thus:
> cd
> /c/Data/Boldstroke/OCP/OCP/Infrastructure/PlatformServices/ACE_Wrappers/ace
> ccppc -fno-implicit-templates
>
> -B/c/Tornado/host/x86-win32/lib/gcc-lib/powerpc-wrs-vxworks/gcc-2.96/
> -DCPU=PPC604 -DVXWORKS -D_REENTRANT -ansi -fno-exceptions
> -fno-builtin -fno-defer-pop -fvolatile -nostdlib -W -Wall
> -Wno-format
> -fno-rtti
> -DACE_LACKS_RTTI
> -I/c/Tornado/target/h
>
> -I/c/Data/Boldstroke/OCP/OCP/Infrastructure/PlatformServices/ACE_Wrappers
> -c -o .obj/Basic_Types.o Basic_Types.cpp
>
> Fails with missing headers which are present in the
> /c/Data/Boldstroke/OCP/OCP/Infrastructure/PlatformServices/ACE_Wrappers
> directory.
>
> However, moving to the directory
> /c/Data/Boldstroke/OCP/OCP/Infrastructure/PlatformServices/ACE_Wrappers/ace
> in bash and utilizing the following compile line results in a partial
> success(until a file needs to be included from another Cygwin directory)
>
> ccppc -fno-implicit-templates
>
> -B/c/Tornado/host/x86-win32/lib/gcc-lib/powerpc-wrs-vxworks/gcc-2.96/
> -DCPU=PPC604 -DVXWORKS -D_REENTRANT -ansi -fno-exceptions
> -fno-builtin -fno-defer-pop -fvolatile -nostdlib -W -Wall
> -Wno-format
> -fno-rtti
> -DACE_LACKS_RTTI
> -I/c/Tornado/target/h
>
> -I/c/Data/Boldstroke/OCP/OCP/Infrastructure/PlatformServices/ACE_Wrappers
> -I.. # <----- Note relative path!
> -c -o .obj/Basic_Types.o Basic_Types.cpp
>
> Any ideas why this would be happening? It seems to be a problem unique to
> this machine --nobody else who uses Cygwin here has seen it before.
>
> ccppc is a standard GCC 2.96 cross-compiler provided as part of the
> WindRiver toolkit for embedded systems.
>
> Sincerely,
> Dan Churchill
> Honeywell Labs
>
> --
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting: http://cygwin.com/bugs.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/