[Mingw-notify] [ mingw-Bugs-442957 ] Problem with long filenames and paths

[<no...@so...>]

Bugs item #442957, was opened at 2001-07-19 22:53
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102435&aid=442957&group_id=2435

Category: gcc
Group: None
>Status: Closed
>Resolution: Out of Date
Priority: 5
Submitted By: Eric Friedman (ebf)
>Assigned to: Earnie Boyd (earnie)
Summary: Problem with long filenames and paths

Initial Comment:
I am using the newest (as of 7/19/2001) MinGW packages 
as well as the "gcc-2.95.3-20010613-W95patch.tar.gz" 
patch.

I am using Windows 2000 Professional.

When MinGW is installed in "C:\Program Files\MinGW," 
running "gcc -v" gives the following output:

  Using builtin specs.
  gcc version 2.95.3-4 (mingw special)

and any attempts to compile a C++ file gives the cpp0 
not found error.

When I have MinGW installed in "C:\MinGW," I get what 
seems to be the correct output:

  Reading specs from \mingw\lib\gcc-lib\mingw32\2.95.3-
4\specs
  gcc version 2.95.3-4 (mingw special)

and attempts to compile simple source C++ files work 
fine.

When headers that are in directories with spaces in 
their names are included, the compiler reports that 
the headers cannot be found, despite their paths being 
specified in the CPP_INCLUDE_PATH and the 
C_INCLUDE_PATH environment variables.

 *** MY CONCLUSION:
The only conclusion I have been able to make from this 
behavior is that the current release of MinGW does not 
recognize long filenames/paths or maybe just those 
with spaces in them.

Could anyone confirm that this is indeed a bug, and, 
if so, when it might be addressed?  Thanks.

----------------------------------------------------------------------

Comment By: Luke Dunstan (infidel)
Date: 2002-05-22 09:20

Message:
Logged In: YES 
user_id=30442

Tested on Windows 98 by:

Putting gcc in C:\Program Files\gcc-3.1
In command prompt: set PATH="%PATH%;C:\Program 
Files\gcc-3.1\bin"
Output of gcc -v:

Reading specs from C:/PROGRA~1/GCC-3.1/BIN/../lib/gcc-
lib/mingw32/3.1/specs
Configured with: ../gcc/configure --with-gcc --with-gnu-ld --with-
gnu-as --host=
mingw32 --target=mingw32 --prefix=/mingw --enable-threads --
disable-nls --enable
-languages=f77,c++,objc,ada --disable-win32-registry --disable-
shared
Thread model: win32
gcc version 3.1

Note that the quotes are needed to insert spaces in PATH, 
but the quotes are not actually stored in the PATH variable. I 
think this bug can be closed.


----------------------------------------------------------------------

Comment By: Paul Garceau (pgarceau)
Date: 2001-07-25 17:27

Message:
Logged In: YES 
user_id=1762

Standard behaviour for cmd.exe is to convert spaces in path names to appropriate MS backslashes (\) 
unless the directory name (folder in question) is enclosed in quotes.  For example, setting a path name for 
Mingw to "Program Files\mingw.." solves this problem.  You should not be setting CPP_INCLUDE_PATH or 
C_INCLUDE_PATH as those are defined by Mingw.

Installation instructions specifically state that distribution should be dearchived into a root drive reference in 
order to accomodate this Win32api (cmd.exe) "feature".  That is, when installing, the distribution should be 
dearchived to something like "mingw_test" or "mingw", in order to yield (drive reference) "<drive>:\mingw" or 
"<drive>:\mingw_test".  If you must put your directory in "Program Files" (Extremely Atypical and Not 
Recommended), then you must include and define a base directory which includes quotes as part of path 
reference (eg. "c:\my mingw\mingw" or "c:\program files\mingw".  Notice spaces in path name.).

----------------------------------------------------------------------

Comment By: Paul Garceau (pgarceau)
Date: 2001-07-25 17:27

Message:
Logged In: YES 
user_id=1762

Not a MinGW bug.

Although your problem may be interesting and causing you problems you wish answers to, it is not a problem with the 
MinGW project.  Your BUG report has therefore been deleted.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102435&aid=442957&group_id=2435