I guess I saw warnings and thought it wasn't compiling on 16.04, but now that I cleaned the build folders, and reran cmake and make, everything compiles fine.

Thanks for the help,


Louis McCarthy replied to the topic '3rdParty Build Failure' in the forum. 6 years ago

Thanks to Jean-Luc it's now compiling under Ubuntu 14.04. I moved the special mchp libusb link:

cd  /usr/local/lib/
sudo mv libusb-1.0.so.0 libusb-1.0-special.so.0
and libindi found the correct library without a recompile.

I'll try to get 16.04 working before marking this solved.


Louis McCarthy replied to the topic '3rdParty Build Failure' in the forum. 6 years ago

Thanks Jean-Luc,
I think you're on to something!
I do have MPLAB installed on both computers. On my previous post, I pasted the ldd from Ubuntu 14. When I ran ldd from Ubuntu 16 machine this morning, it points to a different libusb.so file (/lib/x86_64-linux-gnu/libusb-1.0.so.0 (0x00007fb3b928f000)). I did quite a bit of hacking on that system last night, though, so let me try to get back to a clean slate and see if I can get it to work.

I also have some ARM cross compile toolchains installed, I'll have to see if those are "helping" too.
Thanks again,


Louis McCarthy replied to the topic '3rdParty Build Failure' in the forum. 6 years ago

Thanks for the reply. Here is the result from running make:

compeoree@Midnight:~/indi/build/3rdparty$ make
[  0%] Linking CXX executable indi_eqmod_telescope
/usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libindidriver.so: undefined reference to `libusb_error_name'
collect2: error: ld returned 1 exit status
indi-eqmod/CMakeFiles/indi_eqmod_telescope.dir/build.make:384: recipe for target 'indi-eqmod/indi_eqmod_telescope' failed
make[2]: *** [indi-eqmod/indi_eqmod_telescope] Error 1
CMakeFiles/Makefile2:85: recipe for target 'indi-eqmod/CMakeFiles/indi_eqmod_telescope.dir/all' failed
make[1]: *** [indi-eqmod/CMakeFiles/indi_eqmod_telescope.dir/all] Error 2
Makefile:149: recipe for target 'all' failed
make: *** [all] Error 2


Louis McCarthy created a new topic ' 3rdParty Build Failure' in the forum. 6 years ago

I'm having trouble building the 3rdparty code. I've tried on two different Ubuntu systems, one running 14.04 and the other 16.04.

The linker fails with

/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libindidriver.so: undefined reference to `libusb_error_name'
whether I try to compile all 3rdparty code, or just indi-gphoto.

If I call ldd on /usr/lib/x86_64-linux-gnu/libindidriver.so, this is the result
	linux-vdso.so.1 =>  (0x00007ffc4a159000)
	libusb-1.0.so.0 => /usr/local/lib/libusb-1.0.so.0 (0x00007f4b3b4e1000)
	libnova-0.14.so.0 => /usr/lib/x86_64-linux-gnu/libnova-0.14.so.0 (0x00007f4b3af5a000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f4b3ad3c000)
	libcfitsio.so.3 => /usr/lib/x86_64-linux-gnu/libcfitsio.so.3 (0x00007f4b3a984000)
	libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f4b3a76b000)
	libjpeg.so.8 => /usr/lib/x86_64-linux-gnu/libjpeg.so.8 (0x00007f4b3a516000)
	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f4b3a212000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f4b39f0c000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f4b39cf6000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4b39931000)
	librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f4b39729000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f4b3ba38000)

libindi was built and installed from the git commit, 6240aaa, which is the same commit used to attempt to compile the 3rdparty modules.

I followed the README.md instructions line-by-line, and have triple checked the pre-requisites.

It looks like libusb-1.0 is there. Am I missing something?


Ah, maybe not. I have the Starshoot Pro V2.0 Deep Space Color.

Good to hear that you got yours working. I'll keep chugging away and see if I can make any more progress with mine.

I really want my camera to work under Linux. I tried Windows on a Minnowboard MAX, but it decided not to boot one night, and I didn't like having to lug a monitor, keyboard, mouse, and inverter, 600' to my backyard to try to fix it. I ended up having to do a complete reinstall. Bleh.


Great timing, I just started looking into this too....

I think we can split the research into two sections:
1) Plug in and enumeration
2) Image capture

Plug in and enumeration would be where firmware upload, if it does it, would occur. I'm not sure if the USB sniffing tools I have can do this. Can anyone else get a dump during this phase?

I've created a dump, of image capture, using Wireshark Version 2.2.0 (v2.2.0-0-g5368c50 from master-2.2) and the bundled version of USBPcapCMD (
It consists of starting MaximDL, capturing a 5 second frame, and then closing MaximDL.

I've configured the fan speed to be low. When the camera is plugged into USB, the fan stays high until the MaximDL software is started. It's a nice indicator of important USB activity.

I've attached the dump here, but if that doesn't work you can download from Dropbox: www.dropbox.com/s/tj2l2m873sf6e1g/sspro-...photo.pcapng.xz?dl=0