I just tried cloning this onto a machine running Redhat 7.5 and it threw an error saying it couldn't create the file README.md because it was symlinking to a file with a path that was too long.
Digging into the error a bit I found that the problematic thing was that the file system thought that README.md was a symlink and the contents (on linux at least) should just be the path of the destination (for soft symlinks) so it tried to do this:
README.md -> [](https://travis-ci.org/VirusTotal/c-vtapi)^J^JVirusTotal C API library^JThis libary is designed to work with both the:^I^J * The public API https://www.virustotal.com/en/documentation/public-api/^J * The private API https://www.virustotal.com/en/documentation/private-api/^J^JRuntime Dependencies^J * curl or libcurl (curl-devel package on some distributions)^J * janson version 2.2 (min) (2.5 or newer recommeded. janson-devel on some distros)^J^JCompiling Dependencies^J * automake, autoconf (might be autotools package on your platform)^J * gcc^J * libtool^J^JDebian or Ubuntu Dependencies:^J```^Jsudo apt-get install automake autoconf libtool libjansson-dev libcurl4-openssl-dev^J```^J^JRedhat, Fedora, Centos or RPM based distros:^J```^Jyum install libtool jansson-devel^J```^J^JTo compile on Linux, BSD, or Mac OS X:^J```^Jautoreconf -fi^J./configure^Jmake^Jsudo make install^J```^J^JIf you wish to build the examples in the 'examples' directory:^J```^Jautoreconf -fi^J./configure --enable-examples^Jmake^Jsudo make install^J```^J^JIf you have doxygen installed on your system you may optionally generate developer doxygen docs:^J ```^Jmake doxygen-doc^J```^J^JUsage on MS Windows is partially functioal now, but requires more patches to be fully supported.^J^JWindows compilation:^J```^J* Installl mingw^J * mingw32 gcc-g++^J * mingw32-autoconf^J * mingw32-automake^J* compile libcurl (See their docs on windows compile)^J```^J^JWindows compilation (MS Visual Studio)^J * install MS Visual Studio 2013^J * install CMake^J * Compile jansson (see janson docs)^J * Compile curl (see janson docs)^J^I^J^JSee Examples in examples/^JFor some example test programs using API.^J^Jurl --apikey=YOUR_KEY --scan http://youtube.com^Jurl --apikey=YOUR_KEY --report http://youtube.com^J^J^Jscan --help^J./scan --apikey YOUR_KEY --filescan /bin/ls^J./scan --apikey YOUR_KEY --report HASH^J
which obviously doesn't work all that well. Doing a git diff (once you get past the strange symlinky stuff) interprets it weirdly as well and shows a symlink to /dev/null.
Not sure if this is an OS compatibility thing but it definitely had be confused for a few minutes.
I just tried cloning this onto a machine running Redhat 7.5 and it threw an error saying it couldn't create the file README.md because it was symlinking to a file with a path that was too long.
Digging into the error a bit I found that the problematic thing was that the file system thought that README.md was a symlink and the contents (on linux at least) should just be the path of the destination (for soft symlinks) so it tried to do this:
which obviously doesn't work all that well. Doing a git diff (once you get past the strange symlinky stuff) interprets it weirdly as well and shows a symlink to /dev/null.
Not sure if this is an OS compatibility thing but it definitely had be confused for a few minutes.