This is a tricky problem. I find that when a list of errors occurs, it's good practice to focus on the first one in the list, since once the first error occurs, it can create a cascade of errors that are only occurring because of that first error and no longer appear once that initial error is cleared.
The first line mentions GLIBC_2.17. My research indicates that some people have had problems with LIBC after doing an upgrade. They fixed their problem by doing an update of LIBC to ensure that they had the latest version of it.
sudo apt-get update
sudo apt-get install libc6
The problem has been solved by upgrading from L4T28.2 to JetPack-L4T-3.2-linux-x64_b157.run.
If you have a problem with libudev.h error at the build time, execute the following command.
$sudo apt-get install libudev-dev