X-Spam-Check-By: sourceware.org Message-ID: <98d558bd0701310150o60d1adf6m57707cffbc86f456@mail.gmail.com> Date: Wed, 31 Jan 2007 09:50:49 +0000 From: "Stephen Henry" To: cygwin AT cygwin DOT com Subject: Relative vs. Absolute path problem MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Hi, I have a really strange problem with my Cygwin installation. It concerns a filename parameter given to a application launched from the bash command prompt. The problem is as follows: I have an application that takes a filename parameter. The application uses the 'fopen' command to open the filename and process the file (very simple really). The problem is that when I type the filename as an absolute path, the file cannot be read, but when it is typed as a relative path, it works fine. For example, This works perfectly (from a directory in my home directory): $ ./x264.exe -o out.h264 ../../../testseq/yuv420/COASTGUARD-YUV420-CIF 352x288 Whilst this does not: ./x264.exe -o out.264 /testseq/yuv420/COASTGUARD-YUV420-CIF 352x288 The obvious problem would be that the two paths are not equal, but I can assure you that this is not the case -they both point to the same file. The only difference is that one path is relative and the other is absolute. The permissions are set so all users can read the file. I'm not exactly new to Cygwin/UNIX, but this problem has me completely stumped. Any ideas? Thanks for your help, Stephen -- 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/