problem when dealing with tar.gz files on ubuntu

mbg_gayed · 08-11-2009, 04:33 PM

after extracting .tar.gz file and execute the following commands according to README instructions file :
./configure
make
make install

./configure command goes very fine ,but when i tried to execute both make & make install commands ,this msgs appear :
1-for make command:
make: *** No targets specified and no makefile found. Stop.
2-for make install command:
make: *** No rule to make target `install'. Stop.

what should i do ? any help !!

mark_alfred · 08-12-2009, 08:49 AM

For make and make install commands, root privileges are needed. Did you run it as root (or with sudo)?

weibullguy · 08-12-2009, 09:03 AM

Quote:

Originally Posted by mbg_gayed

1-for make command:
make: *** No targets specified and no makefile found. Stop.

Then configure didn't go well after all. Rerun the configure script and pay close attention to the output. Obviously if there is no Makefile, make install won't work either.

You do NOT have to be root to execute make or even make install. In fact, there should be no reason to execute make as root; its a bad habit to get into so I recommend you not start. You only need to be root to install system-wide. You can also install in your $HOME which would not require root privileges.

mbg_gayed · 08-12-2009, 11:43 AM

make file doesn't exist ,while make install file is already exist ,and I'm still can't execute make command !!

AlucardZero · 08-12-2009, 11:46 AM

Then configure didn't go well after all. Rerun the configure script and pay close attention to the output.

jdkaye · 08-12-2009, 11:53 AM

Quote:

Originally Posted by mbg_gayed

make file doesn't exist ,while make install file is already exist ,and I'm still can't execute make command !!

Sorry but what you say doesn't make any sense. Is there a file called "Makefile"? If it doesn't exist then you cannot run

Code:

make

and if you cannot run make, then you cannot run

Code:

# make install

Weibullguy is correct that you don't (need to) run make as root. Normally what you compile gets put in /usr/local (though you can specify otherwise) and so normally you do need to run make install as root.
cheers,
jdk

weibullguy · 08-12-2009, 12:34 PM

What package are you trying to build? Did you check the md5sum after you downloaded the tarball?

If a Makefile doesn't exist, then configure didn't work or the file is corrupt and not working the way it should. That's, fundamentally, what the configure script is for...to create a Makefile from Makefile.in. You likely are seeing a script named install-sh. This is a script used to install the package components on systems that don't have the install command.

So, rerun the configure script and pay close attention to the output. If you don't see anything obvious, post the last 20-30 lines of output from the configure script.

mbg_gayed · 08-12-2009, 03:29 PM

here's the output :

Quote:

mbg@MBG:~/Desktop/liferea-1.6.0$ ./configure
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
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 dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for shl_load... no
checking for shl_load in -ldld... no
checking for dlopen... no
checking for dlopen in -ldl... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking whether NLS is requested... yes
checking for intltool >= 0.35.0... ./configure: line 11237: intltool-update: command not found
found
configure: error: Your intltool is too old. You need intltool 0.35.0 or later.

weibullguy · 08-12-2009, 04:26 PM

Code:

checking for intltool >= 0.35.0... ./configure: line 11237: intltool-update: command not found
found
configure: error: Your intltool is too old. You need intltool 0.35.0 or later.

Update or install intltool, then re-execute configure. Better yet, use your package manager to install Liferea. It's a common package and I'm sure its available.

mark_alfred · 08-14-2009, 11:13 PM

Quote:

Originally Posted by weibullguy

You do NOT have to be root to execute make or even make install.

I rarely install source packages, and instead rely almost exclusively on pre-compiled deb packages for my distro. When I have installed source packages in the past, I've needed to be root for the "make install" command. However, your post inspired me to look a bit further into this, and I discovered that if I added my user to the group "staff", that my user then became able to run the "make install" command when installing to the /usr/local directory.

Learn something new every day. This, in fact, will make me less hesitant in the future to install source packages. In fact, I installed my favourite file manager, emelfm, just now (emelfm was in Etch, but not Lenny, for some reason -- but it's now in my desktop thanks to your post).

AlucardZero · 08-15-2009, 06:45 AM

Or, if you use ./configure's --prefix flag, you can install to anywhere, for example your home directory.