bug-make
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #41830] make cannot find an existing file


From: Eli Zaretskii
Subject: [bug #41830] make cannot find an existing file
Date: Tue, 11 Mar 2014 18:12:29 +0000
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:27.0) Gecko/20100101 Firefox/27.0

Update of bug #41830 (project make):

                Severity:              3 - Normal => 1 - Wish               
              Item Group:                     Bug => Enhancement            
                  Status:                    None => Duplicate              
             Open/Closed:                    Open => Closed                 
           Triage Status:                    None => Major Effort           

    _______________________________________________________

Follow-up Comment #2:

Sorry, I see that I've misread the log.  The batch file failed because it
invoked Make, and that recursive Make invocation failed.

Now the error message says:

mingw32-make[1]: *** No rule to make target
'../../../../../../../NpackdSymlinks/com.nokia.QtDev-x86_64-w64-Npackd-Release-5.2.1/qtbase/mkspecs/modules-inst/qt_lib_multimediawidgets_private.pri',
needed by 'Makefile'. Stop. 

However, the directory where Make runs is this:

mingw32-make[1]: Entering directory
'C:/Users/t/projects/windows-package-manager.npackd-scripts/build-packages/QuaZIP-static-x86_64-w32-0.6.2/quazip'

If you append the target path to this directory, you get a file name that is
260 characters long, which is 1 character more than Windows allows (256 for
file name plus 3 more for the drive letter, the colon, and the leading slash).
 Yes, this is what Windows does: it first appends the relative file name to
the current directory, and only after that normalizes the result.

So what you see is a fundamental limitation of the file-name APIs used by Make
on Windows.  Fixing this would be a major effort.  See
https://savannah.gnu.org/bugs/?40344 for a relevant discussion (this bug is
actually a duplicate of that one).

Alternatively, you can work around this issue by simplifying your file names,
or by using SUBST to create a drive letter that points to one of the
directories involved in this problem.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?41830>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]