bug-binutils
[Top][All Lists]
Advanced

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

[Bug ld/25713] New: Linker(ld.exe) runs in Windows unable to find file i


From: jaydeepchauhan1494 at gmail dot com
Subject: [Bug ld/25713] New: Linker(ld.exe) runs in Windows unable to find file if path length is more than 260 characters.
Date: Mon, 23 Mar 2020 08:15:42 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=25713

            Bug ID: 25713
           Summary: Linker(ld.exe) runs in Windows unable to find file if
                    path length is more than 260 characters.
           Product: binutils
           Version: 2.33
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ld
          Assignee: unassigned at sourceware dot org
          Reporter: jaydeepchauhan1494 at gmail dot com
  Target Milestone: ---

Created attachment 12399
  --> https://sourceware.org/bugzilla/attachment.cgi?id=12399&action=edit
Patch to fix linker (ld.exe) path limit of 260 characters for windows

In Windows OS for ld.exe getting error message " no such file or directory", if
the object file whose full path length exceed 260 characters.

Command:
ld.exe
C:\msys64\home\Jaydeep\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepah\increasepath\increasepath\increasepath\increasepath\test.o

Error:
ld.exe: cannot find
C:\msys64\home\Jaydeep\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepat
h\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\increasepath\test.o:
No such file or directory

To solve this problem, As per Microsoft suggestion to prefix "\\?\" to filename
(object-file) to make it work and it is working for absolute Path .

Please find the attached patch (ld.patch) which fixes this issue.

Also let me know if there is any other alternate way to handle this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

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