> On 1 Sep 2020, at 10:50, kristof.mul...@telenet.be wrote:
>
> Beware of the location where you unzip the build output.
> I copied the build output to a folder on my Ubuntu VM that
> is shared with the Windows host OS. Unzipping it there -
> even though it's done on the Ubuntu VM - kills all the
> symlinks.
In case this is not clear enough: the problematic folder was not 'shared with
the Windows host'. More accurately it can be defined as 'a Windows shared
resource mounted on Linux'. As usual for Windows, that shared resource was
actually located in a NTFS folder. Even when mounted on Linux, the folder
remains a NTFS folder, with all specific traits, including the poor support for
symbolic links.
Unfortunately the tool used to extract the archive in that folder mounted in
Linux did not complain, so it looked ok, but the resulted expanded /bin folder
lacked the links used to address the shared libraries. Thus the 'error while
loading shared libraries' seen while starting openocd.
As a conclusion, don't expand the distribution archives on Windows filesystems
or on any other filesystems that do not support symlinks.
Regards,
Liviu
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
