• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 101 subscribers
  • Views 737 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

XDCtools cygwin1.dll version upgrade?

ejs
Intellectual 2930 points

Hello,

one of my customers is facing issues on his Windows 7 system when using the cygwin1.dll version 1.5.25, which is part of our current (and older) XDCtools deliveries. He thinks that this old version of cygwin1.dll does not play well on his system, especially together with Symantec Endpoint Protection.

The issue that he was facing is about some "permission denied" error. It seems that configuro is using the cygwin cp command to generate new linker.cmd files, but makes it read-only. Following writes (to modify) the linker.cmd files will fail with a permission denied then. 

He was able to solve his issue be replacing the cygwin1.dll with a new version (1.7.33) from the cygwin.org site.

Would it make sense to upgrade cygwin1.dll that comes with the XDCtools to a newer version?

  • 0
    TI__Mastermind 37985 points

    ejs,
    we had problems with different versions of cygwin before, and unfortunately we never devised a complete solution for that problem. For the specific problem with permissions for linker.cmd we recommend setting the environment variable CYGWIN as described in this thread.

    Any solution that changes the version of cygwin DLL that comes with XDCtools may potentially break bin/sh.exe in the XDCtools installation. It may work for your customer for one project, but then break as soon as a more complex make file is generated in another project. More details about cygwin and bin/sh.exe dependency can be found in this thread.

    So, I would try setting the environment variable first.