[SOLVED] Installing mtpfs 1.1.tar gz for Fedora 19
FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
"easy" (when you do this every day ); compile was successful, but you tried to install into /usr/local/bin from user, not root, and have no permission to do that: "ls -l /usr/local/ | grep bin" show you "rwxr-xr-x root root", meaning only root can write in it, then?
just use "sudo make install", or do "make install" as root
ADD: as you see, program is installed in /usr/local/bin instead of /usr/bin, this is a default for every program you build manually, to change it, add "--prefix=/usr" to the ./configure, as "./configure --prefix=/usr" (as said by JohnVV)
"prefix" is a parameter for configure, it tells to the script that will generate the makefiles where we want the files go, saying --prefix=/usr, the makefile will be generated so binaries will go in /usr/bin, include in /usr/include, libraries in /usr/lib(64) etc
"prefix" is a parameter for configure, it tells to the script that will generate the makefiles where we want the files go, saying --prefix=/usr, the makefile will be generated so binaries will go in /usr/bin, include in /usr/include, libraries in /usr/lib(64) etc
Thanks for explaining. Still having trouble and I lack the experience that you have.
Code:
[redcat@localhost mtpfs-1.1]$ ./configure --prefix=/usr/bin
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for FUSE... yes
checking for MTP... yes
checking for GLIB... yes
checking for MAD... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: executing depfiles commands
[redcat@localhost mtpfs-1.1]$ su
Password:
[root@localhost mtpfs-1.1]# make install
make[1]: Entering directory `/home/redcat/Downloads/mtpfs-1.1'
test -z "/usr/bin/bin" || /usr/bin/mkdir -p "/usr/bin/bin"
/usr/bin/install -c mtpfs '/usr/bin/bin'
make[1]: Nothing to be done for `install-data-am'.
make[1]: Leaving directory `/home/redcat/Downloads/mtpfs-1.1'
[root@localhost mtpfs-1.1]#
[redcat@localhost mtpfs-1.1]$ ./configure --prefix=/usr
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for FUSE... yes
checking for MTP... yes
checking for GLIB... yes
checking for MAD... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: executing depfiles commands
[redcat@localhost mtpfs-1.1]$ su
Password:
[root@localhost mtpfs-1.1]# make install
make[1]: Entering directory `/home/redcat/Downloads/mtpfs-1.1'
test -z "/usr/bin" || /usr/bin/mkdir -p "/usr/bin"
/usr/bin/install -c mtpfs '/usr/bin'
make[1]: Nothing to be done for `install-data-am'.
make[1]: Leaving directory `/home/redcat/Downloads/mtpfs-1.1'
Quote:
and things will install just fine
Something still is not going correctly....(I Think) because of the Nothing to be done for 'install-data-am' Am I wrong?
although "make install" can sometimes be used as a shortcut
it is not a good idea
"make" should be ran as a NORMAL user
as root clean the build folder
there a few ways
start over with a clean extract of the tarball
or run "AS ROOT for this seeing as you ran "make" as root last time
Code:
su
make distclean
then
as a normal non root user
Code:
./configure --prefix=/usr
make
su
--- root password when asked for ---
make install
[root@localhost mtpfs-1.1]# make distclean
test -z "mtpfs" || rm -f mtpfs
rm -f *.o
rm -f *.tab.c
test -z "" || rm -f
test . = "." || test -z "" || rm -f
rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
rm -f config.status config.cache config.log configure.lineno config.status.lineno
rm -rf ./.deps
rm -f Makefile
[root@localhost mtpfs-1.1]#
Trying again exactly in the order you told me.
1) ./configure --prefix=/usr
2)make
3)su
4)make install
Code:
[redcat@localhost mtpfs-1.1]$ ./configure --prefix=/usr
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for FUSE... yes
checking for MTP... yes
checking for GLIB... yes
checking for MAD... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: executing depfiles commands
[redcat@localhost mtpfs-1.1]$ make
make: Nothing to be done for `all'.
[redcat@localhost mtpfs-1.1]$ su
Password:
[root@localhost mtpfs-1.1]# make install
make[1]: Entering directory `/home/redcat/Downloads/mtpfs-1.1'
test -z "/usr/bin" || /usr/bin/mkdir -p "/usr/bin"
/usr/bin/install -c mtpfs '/usr/bin'
make[1]: Nothing to be done for `install-data-am'.
make[1]: Leaving directory `/home/redcat/Downloads/mtpfs-1.1'
[root@localhost mtpfs-1.1]#
yes, it only install the binary mtpfs in /usr/bin, as told by your configure parameters;
the string "nothing to be done..." is normal during make, as makefile contain a sequence of command to build the package and some of them exist, but have no relevant command, like pressing enter in a shell without entering a command, it does nothing but you have pressed enter
no, just use it (and i'm interested too), just a thing more, if you want to delete it, just do a "make uninstall", you can delete the source folder, and in the future just do "./configure --prefix=/usr" and "make uninstall", remember the prefix you used or the makefile won't find anything
EDIT: the end of the world, my phone as a usbdrive
Last edited by gengisdave; 01-25-2014 at 06:39 PM.
BTW I also installed 'simple-mtpfs' as Jeremy advised me.
I'm very sorry to say that installing 'mtpfs' & 'simple-mtpfs' has made no difference or at least; so far it hasn't.
You guys are the best!
Thank you allfor teaching me this compilation process!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
); compile was successful, but you tried to install into /usr/local/bin from user, not root, and have no permission to do that: "ls -l /usr/local/ | grep bin" show you "rwxr-xr-x root root", meaning only root can write in it, then?
