> The key trick there is 'in the xpack-dev-tools/openocd Git repo'. Right, so I stay in the git repo that I cloned like this:
$ curl -L https://github.com/xpack-dev-tools/openocd-xpack/raw/xpack/scripts/git-clone.sh | bash $ cd ~/Downloads/openocd-xpack.git So the "merge from upstream/master" is simply the pull command, and I don't need to specifically clone the official OpenOCD repo (git://git.code.sf.net/p/openocd/code)? ----- Oorspronkelijk bericht ----- Van: "Liviu Ionescu" <[email protected]> Aan: "kristof mulier" <[email protected]> Cc: "openocd-devel" <[email protected]>, "johan" <[email protected]>, "matic" <[email protected]> Verzonden: Zaterdag 29 augustus 2020 18:45:08 Onderwerp: Re: Missing libusb shared object file in xPack build. > On 29 Aug 2020, at 19:42, [email protected] wrote: > > To keep the development repository in sync with the original OpenOCD > repository, in the xpack-dev-tools/openocd Git repo: The key trick there is 'in the xpack-dev-tools/openocd Git repo'. But this will probably not solve your problem. Use ldd -v to check dependencies. Regards, Liviu _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
