LinuxQuestions.org - [SOLVED] Installing mtpfs 1.1.tar gz for Fedora 19

- Fedora (https://www.linuxquestions.org/questions/fedora-35/)

- - Installing mtpfs 1.1.tar gz for Fedora 19 (https://www.linuxquestions.org/questions/fedora-35/installing-mtpfs-1-1-tar-gz-for-fedora-19-a-4175492097/)

Installing mtpfs 1.1.tar gz for Fedora 19

Hi:

I am trying to install mtpfs-1.1.tar gz in order for my Android tablet to be recognized. libmtp btw is installed
I am not good with installing these types of tarballs and struggle.
I don't understand why "make" is not working-

Code:

[redcat@localhost mtpfs-1.1]$ ./configure

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... no

checking for cc... no

checking for cl.exe... no

configure: error: in `/home/redcat/Downloads/mtpfs-1.1':

configure: error: no acceptable C compiler found in $PATH

See `config.log' for more details

[redcat@localhost mtpfs-1.1]$ make

make: *** No targets specified and no makefile found.  Stop.

Do I not have a compiler? Like gcc?

Here is the portion of the "Install" File instruction that I am trying to follow.

Code:

 The simplest way to compile this package is:



  1. `cd' to the directory containing the package's source code and type

    `./configure' to configure the package for your system.



    Running `configure' might take a while.  While running, it prints

    some messages telling which features it is checking for.



  2. Type `make' to compile the package.



  3. Optionally, type `make check' to run any self-tests that come with

    the package, generally using the just-built uninstalled binaries.



  4. Type `make install' to install the programs and any data files and

    documentation.  When installing into a prefix owned by root, it is

    recommended that the package be configured and built as a regular

    user, and only the `make install' phase executed with root

    privileges.



  5. Optionally, type `make installcheck' to repeat any self-tests, but

    this time using the binaries in their final installed location.

    This target does not install anything.  Running this target as a

    regular user, particularly if the prior `make install' required

    root privileges, verifies that the installation completed

    correctly.



  6. You can remove the program binaries and object files from the

    source code directory by typing `make clean'.  To also remove the

    files that `configure' created (so you can compile the package for

    a different kind of computer), type `make distclean'.  There is

    also a `make maintainer-clean' target, but that is intended mainly

    for the package's developers.  If you use it, you may have to get

    all sorts of other programs in order to regenerate files that came

    with the distribution.

Thanks in advance-;)

Quote:

Originally Posted by Ztcoracat (Post 5102641)

Code:

[redcat@localhost mtpfs-1.1]$ ./configure

checking for gcc... no

checking for cc... no

checking for cl.exe... no

configure: error: in `/home/redcat/Downloads/mtpfs-1.1':

configure: error: no acceptable C compiler found in $PATH

yes, you don't have gcc or a similar compiler

Installing a working / usable gcc :

# yum install gcc-c++

Quote:

Originally Posted by knudfl (Post 5102794)

Installing a working / usable gcc :

# yum install gcc-c++

Installed gcc-c++ like you advised:-

Code:

Running transaction

  Installing : libmpc-1.0.1-1.fc19.x86_64                                  1/8 

  Installing : cpp-4.8.2-7.fc19.x86_64                                      2/8 

  Installing : kernel-headers-3.12.8-200.fc19.x86_64                        3/8 

  Installing : glibc-headers-2.17-20.fc19.x86_64                            4/8 

  Installing : glibc-devel-2.17-20.fc19.x86_64                              5/8 

  Installing : gcc-4.8.2-7.fc19.x86_64                                      6/8 

  Installing : libstdc++-devel-4.8.2-7.fc19.x86_64                          7/8 

  Installing : gcc-c++-4.8.2-7.fc19.x86_64                                  8/8 

  Verifying  : cpp-4.8.2-7.fc19.x86_64                                      1/8 

  Verifying  : gcc-c++-4.8.2-7.fc19.x86_64                                  2/8 

  Verifying  : gcc-4.8.2-7.fc19.x86_64                                      3/8 

  Verifying  : glibc-devel-2.17-20.fc19.x86_64                              4/8 

  Verifying  : glibc-headers-2.17-20.fc19.x86_64                            5/8 

  Verifying  : libstdc++-devel-4.8.2-7.fc19.x86_64                          6/8 

  Verifying  : kernel-headers-3.12.8-200.fc19.x86_64                        7/8 

  Verifying  : libmpc-1.0.1-1.fc19.x86_64

I'll try it again to install "mtpfs-1.1" : hope it works.

Code:

[redcat@localhost mtpfs-1.1]$ ./configure

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... no

configure: error: Package requirements (fuse >= 2.2) were not met:



No package 'fuse' found



Consider adjusting the PKG_CONFIG_PATH environment variable if you

installed software in a non-standard prefix.



Alternatively, you may set the environment variables FUSE_CFLAGS

and FUSE_LIBS to avoid the need to call pkg-config.

See the pkg-config man page for more details.

[redcat@localhost mtpfs-1.1]$ make

make: *** No targets specified and no makefile found.  Stop.

[redcat@localhost mtpfs-1.1]$

I do not understand how to adjust the PKG_CONFIG PATH-
Do I need to install fuse 2.2 with yum? Is fuse a module? (new to me)

# 5 .

Quote:

No package 'fuse' found

Means : No "package config file" by name 'fuse.pc' found.

`fuse.pc' is provided by 'fuse-devel' : # yum install fuse-devel
.. Providing /usr/lib64/pkgconfig/fuse.pc , etc. etc. development files,
.. <headers>.h , usr/lib64/libfuse.so → → Total = 13 files.

-

yes, install fuse (let's say it's a link between filesystems and kernel and don't require root privileges)

Installed fuse-devel--

Code:

================================================================================

 Package            Arch          Version                Repository      Size

================================================================================

Installing:

 fuse-devel        x86_64        2.9.3-1.fc19          updates          36 k



Transaction Summary

================================================================================

Install  1 Package



Total download size: 36 k

Installed size: 123 k

Is this ok [y/d/N]: y

Downloading packages:

fuse-devel-2.9.3-1.fc19.x86_64.rpm                        |  36 kB  00:02    

Running transaction check

Running transaction test

Transaction test succeeded

Running transaction

  Installing : fuse-devel-2.9.3-1.fc19.x86_64                              1/1 

  Verifying  : fuse-devel-2.9.3-1.fc19.x86_64                              1/1 



Installed:

  fuse-devel.x86_64 0:2.9.3-1.fc19                                              



Complete!

So, fuse is kindof like a library that communicates sort of like the way firmware is an aid to hardware?
Trying to understand so I know what to look for in the future and have my fedora on straight-

configure handling is normal in a slacker's life :) fuse handles more fs than kernel does, plus you can mount on-the-fly from a normal user (given enough privileges)

Quote:

Originally Posted by gengisdave (Post 5103252)

configure handling is normal in a slacker's life :) fuse handles more fs than kernel does, plus you can mount on-the-fly from a normal user (given enough privileges)

I see-
I'm thinking perhaps it would be a wise practice than to make this privileage (administrative)"root"?
I'm not sure, in truth--

knudfl:-:)

Should I now proceed with the terminal: ./configure, make and make install or do you foresee another dependency or a conflict or variation that may prevent this install of mtpfs 1.1?

Trying to stay focused when life is a tad hectic:-

configure scripts are basically all the same, every package has many dependencies, some are critically needed, others are optional and you can disable configure checking with parameters;

"./configure --help" shows all you can do

Quote:

Originally Posted by gengisdave (Post 5103268)

Didn't know some where optional. Perhaps that takes time to know that.
I'll proceed with the terminal....

Code:

configure: error: Package requirements (libmtp >= 1.1.0) were not met:



No package 'libmtp' found

Correct me if I am wrong (this is new to me) but as long as configure has a complaint and shows me that there is an error and a pkg requirement or some other dependency I will need to continue to install pkg's that are needed. Until than "make" will not be successful? Right?
(trying to understand)

yes, it's recursive, and when configure success, you can finally make and install; there are millions of trouble that can happen, missing dependencies are the lesser part, sometimes there's problem with version packages (you have it installed but it's older - or newer), missing compiler or linker flags etc etc

working on LFS helps a lot in all these

Quote:

Originally Posted by gengisdave (Post 5103290)

Now I get what recursive really means! Thanks!
I'm thinking LFS as in Large File System?

Code:

[redcat@localhost mtpfs-1.1]$ su

Password: 

[root@localhost mtpfs-1.1]# yum install libmtp

Loaded plugins: langpacks

Package libmtp-1.1.6-0.fc19.x86_64 already installed and latest version

Nothing to do

[root@localhost mtpfs-1.1]# make

make: *** No targets specified and no makefile found.  Stop.

[root@localhost mtpfs-1.1]#

Why is it that "no makefile found"?