simple-mtpfs
simple-mtpfs copied to clipboard
phatina
there is no configure file
I also got the same error, and autoreconf -fi did not work for me. However running ./autogen.sh fixed the problem.
Also, maybe it's a Fedora-only problem, but libmtp is not what I needed to build, I also needed libmtp-devel.
but libmtp is not what I needed to build, I also needed libmtp-devel.
Thank you @chefexperte. I finally found the problem, in my case I need libmtp-dev and libfuse-dev, I use Ubuntu 20.04 LTS.
I also got the same error, and
autoreconf -fidid not work for me. However running./autogen.shfixed the problem. Also, maybe it's a Fedora-only problem, but libmtp is not what I needed to build, I also needed libmtp-devel.
thanks for this - I would not have been able to manage without this. I suggest to update the README. Also I needed to install autoconf-archive as a dependency.
Run
autoreconf -fifirst. It'll generateconfigurescript for you.
Except that is NOT in the spec file, so the provided spec file does not build from this tar file Unless you add the autoconf to the spec file, or run it by hand and re-tar the file!
I also encounted 2 marcos that did not expand in the configure (left as is)...
AX_CXX_COMPILE_STDCXX_17(noext)
AX_CXXFLAGS_WARN_ALL
Prefixing 'dnl' to comment out those macros fixed the problem.
Also I needed to install autoconf-archive as a dependency.
Except it is only a dependancy on SuSE builds. Was not a probelm on fedora.
What was a problem was it fails... /usr/lib/rpm/check-rpaths
which reports it contains invalid runpaths However ignoring that check, shows that the binary is working.
Unless you try to rename a file over and existing file! But then every MTP fs program seems to fail that!
@antofthy install autoconf-archive for those extra macros. Then configure runs cleanly (at least on Fedora 38)
My summary of MTP commands I have found or looked at, including simple-mtpfs (no longer available on fedora 40). My specific focus is on Unison file transfer (sync), and vim text file editing, rather than photos and music.
https://antofthy.gitlab.io/info/misc/phone_file_transfers.txt
@antofthy --
My summary of MTP commands I have found or looked at, including simple-mtpfs (no longer available on fedora 40). My specific focus is on Unison file transfer (sync), and vim text file editing, rather than photos and music.
https://antofthy.gitlab.io/info/misc/phone_file_transfers.txt
You missed adbfs in your list.
I've been using simple-mtpfs and rdiff-backup to backup my phone to my linux laptop for the past several years, but the MTP-based solutions were timing out this past week (I had some 2+GB files to transfer). After simple-mtpfs failed, I tried gvfs (which DOES mount into a directory, by the way), and I believe I tried one other solution before arriving at adbfs -- which worked!!! And worked quickly..
For reading from phone it worked -- i didn't try anything else.
Still, it is sad state at how bad this all is.
@derekatkins
You missed adbfs in your list.
Thanks I took a look. https://github.com/zach-klippenstein/adbfs
Looks very experimental, usage not explained very well, especially for someone not familiar with the 'Android Debug Bridge', or Go programming.
But a little research later I have added quite a bit... (more to come)
I tried gvfs (which DOES mount into a directory, by the way),
You are right it does mount, but like many other MTPfs mounts very limited. And does not always act like a true file system. You can't even rename files for example!
I found android-file-transfer which is in the fedora repos to work better that simple-mtpfs (which is no longer in the repos), as it does some weird things, which DOES allow you to rename a file OVER an existing file.
Still, it is sad state at how bad this all is.
Totally agree. Wish newer phones allow normal USB filesystem mounts again, rather than limiting it to this MTP crap!
@antofthy Actually I used https://github.com/spion/adbfs-rootless.git
Totally agree. Wish newer phones allow normal USB filesystem mounts again, rather than limiting it to this MTP crap!
Agree. My FIRST android phone attached as a USB Disk. It was fantastic. Then they moved to MTP and I was like -- WTAF? Why add a layer here? Although from a security PoV it makes sense.
Actually it wasn't security POV... the phone can handle that.
It was that USB mounts can leave a file systems in a bad way if you unplug at a bad moment. MTP fixes that, but was designed for media files (music and photos) not whole directory file transfer, and file renaming, which is where MTP filesystems fail.