https://bugs.kde.org/show_bug.cgi?id=497135
--- Comment #2 from f...@studiofuga.com ---
Hi, thanks for your comment.
I did a small test, since I could not remove the working libmtp, I entered
init3 to avoid interferences from other daemons, rebuilt libmtp all static and
linked mtp-filetree statically. I used ./configure --enable-static
--disable-shared CFLAGS="-static" and then built the examples with
CFLAGS="-static". that seems to have worked:
```
$ldd mtp-filetree
linux-vdso.so.1 (0x00007fb6db565000)
libusb-1.0.so.0 => /lib64/libusb-1.0.so.0 (0x00007fb6db51c000)
libc.so.6 => /lib64/libc.so.6 (0x00007fb6db200000)
libudev.so.1 => /lib64/libudev.so.1 (0x00007fb6db4d7000)
/lib64/ld-linux-x86-64.so.2 (0x00007fb6db567000)
libcap.so.2 => /lib64/libcap.so.2 (0x00007fb6db4c9000)
```
And then
```
$ mtp-filetree
Attempting to connect device(s)
Android device detected, assigning default bug flags
Device: Bridgemate 3 Scoring Device Storage
Storage: Data
2 ColdStorage.db
Storage: LogFiles
8 hald.log
7 crash
6 update.log
5 system.log
Storage: Updates
OK.
```
I'm not sure the test is 100% valid here, it would have been better to use the
system mtp-1.1.22 but I cannot break it, I need the mtp working.
Let me know if I can do any other test.
--
You are receiving this mail because:
You are watching all bug changes.
