http://bugs.winehq.org/show_bug.cgi?id=58500
--- Comment #7 from Renzo de Paoli depaoli.renzo@gmail.com --- (In reply to Alexandre Julliard from comment #6)
The underlying problem is that your VM doesn't support ln -s.
Obviously that shouldn't break the build, but you still may want to fix that.
Good afternoon Alexandre.
My approach is to keep my test setups as much as possible as "out of the box" (to make it as easy as possible to reproduce). In this case out-of-the-box VirtualBox VM settings.
With symbolic linking enabled by - setting host RAMdisk permissions in /etc/fstab RAMdisk /mnt/RAMdisk tmpfs defaults,noatime,mode=1777,size=64G 0 0 - enabling VirtualBox symbolic linking (VM VirtualBox manual chapter 4.3) VBoxManage setextradata "VM-64" VBoxInternal2/SharedFoldersEnableSymlinksCreate/RAMdisk 1 the results are different.
Executing wine from the build directory WINEARCH=win64 WINEPREFIX=$HOME/wine.win64.noinst ./wine winecfg works now.
The error messages about 'ole' and others are the same as before.
"sudo make install" finishes now as well.
Running the installed wine WINEARCH=win64 WINEPREFIX=$HOME/wine.win64.inst wine winecfg works, too.
In conclusion, it is a problem of the configure script's handling of having no symbolic links available, so your assumption is correct.
I guess that leaves 2 options - either remove the "cp -pR" option from the configure script altogether and make it fail early on, - or fix the "cp -pR" option of the configure script and have some extra build test cases that pick up on problems like this.
My preference would be the latter, but even the first would be better than the current situation.