Scanners fail to find dependencies on Cygwin

[bdbaddog]

This issue was originally created at: 2010-07-18 15:58:34.
This issue was reported by: mitchfrazier.
mitchfrazier said at 2010-07-18 15:58:34

On Cygwin the scanner (for C at least) fails to correctly determine the .h file dependencies of .c files. FS.py is upper-casing file names before searching for files. This causes the search to fail for any header files whose names contain lower case.

If I change this in FS.py it then finds things correctly:

## if os.path.normcase("TeSt") == os.path.normpath("TeSt") and not _is_cygwin:
if os.path.normcase("TeSt") == os.path.normpath("TeSt"):

I'm not sure what the motivation is for upper-casing file names on Cygwin so I'm not sure what else this might impact.

stevenknight said at 2010-08-03 08:14:18

Is this using a Cygwin Python, or a non-Cygwin Python (e.g. from python.org) with a Cygwin toolchain?

mitchfrazier said at 2010-08-03 09:56:11

A cygwin version (v2.6.5).

gregnoel said at 2010-08-08 12:48:39

Bug party triage.

magnusr said at 2010-09-28 04:48:05

This fault makes it impossible to include files from a variant directory (since the dependency is missed, they are not duplicated to there). This is a regression from version 1.3.1.

magnusr said at 2010-12-08 05:50:33

This issue is a regression that breaks VariantDir, which is a fairly important feature of scons. Is there any reason it should not be a 2.1 blocker?

garyo said at 2011-04-10 11:00:11

Bill, I'll defer to you but seems to me if cygwin can behave case-insensitively then this patch seems correct to me.

jpommier said at 2012-12-05 04:41:53

Hi version 2.2 is out and scons is still broken on cygwin ! Please apply this fix, FS.py should not upcase filenames or nothing works. See also issue #2723.

dirkbaechle said at 2013-09-11 13:18:07

*** Issue #2723 has been marked as a duplicate of this issue. ***

ajf58 said at 2014-07-10 05:02:05

The duplicate has been resolved, so presumably this issue should be resolved too?

dirkbaechle said at 2014-07-12 05:21:00

Nope, the related bug was only resolved because it got marked as a duplicate.

This is the remaining issue, that we have to care about...so there's some actual work required here. ;)

Votes for this issue: 24.

dirkbaechle said this issue is duplicated by #2723 at 2013-09-11 13:18:07.