http://bugs.winehq.org/show_bug.cgi?id=59855 Renzo de Paoli <depaoli.renzo@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |julliard@winehq.org --- Comment #10 from Renzo de Paoli <depaoli.renzo@gmail.com> --- (In reply to Nikolay Sivov from comment #9)
It's not about symlinks being suddenly unavailable system-wide, it's more likely that reporter is building on a filesystem that doesn't support them.
Good morning Nikolay. Correct, as I stated earlier, this scenario occurs when building from a VM on a host's shared drive, where by default symlinks are disabled. There are probably many other ways to emulate the effect. As mentioned, the configure script recognises that symlinks are not available, but apparently tries to use them anyhow. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.