i am getting the follwoing error while install the packages

hi linux guru's

i have installed .tar.gz type file

for example anjuta-1.1.97.tar.gz

i copied this file to /opt then i unziped that file and extracted
that file using the following comands

gz -d anjuta-1.1.97.tar.gz
tar -xvf anjuta-1.1.97 tar
then i chenaged the directory to /opt/anjuta-1.1.97

from here i have run ./configure but i am not able to install i
got the following errror

checking wheather build envrionment ........ yes
checking wheather sane......... yes
checking wheather make set $[MAKE]..... yes
checking for aclocal1-1.4..... missing
checkig for autoconfig........missing
checking for automake-1.4 .....missing
checking for makeinfo.........missing

checking for /usr/bin/perl
checking for gcc ...... no
checking for cc ...... no
cheking for cl..... no
configure error: no accptance for C compiler found in $ PATH

what does it mean how to install and confiugre

pls guide me

one more quesiotn

i have installed mozill rpm that also i am not able to run the
application

i have installed yahoomessenger rpm . but i dont know how to run the
messenger

is ther any configure have to be done
pls guide me

ravi

In comp.os.linux.networking (E-Mail Removed) <(E-Mail Removed)>:
> hi linux guru's

First of all, your questions doesn't seem to be related to Linux
+ networking. Another ng like comp.os.linux.misc or
comp.os.linux.setup would have been better suited.

> i have installed .tar.gz type file

> for example anjuta-1.1.97.tar.gz

> i copied this file to /opt then i unziped that file and extracted
> that file using the following comands

Don't put source there, use your own $HOME or /usr/local/src or
alike.

> gz -d anjuta-1.1.97.tar.gz
> tar -xvf anjuta-1.1.97 tar

'tar' has a switch "z" allowing it to gunzip in one go.

> then i chenaged the directory to /opt/anjuta-1.1.97

> from here i have run ./configure but i am not able to install i
> got the following errror

> checking wheather build envrionment ........ yes
> checking wheather sane......... yes
> checking wheather make set $[MAKE]..... yes
> checking for aclocal1-1.4..... missing

Missing package aclocal1

> checkig for autoconfig........missing
Missing package autoconfig
> checking for automake-1.4 .....missing
Missing package automake
> checking for makeinfo.........missing
Missing package makeinfo

And so on...

> checking for /usr/bin/perl
> checking for gcc ...... no
> checking for cc ...... no
> cheking for cl..... no
> configure error: no accptance for C compiler found in $ PATH

> what does it mean how to install and confiugre

Just what it says, configure is trying to build a Makefile
suitable for your system and can't find quite some thing needed
to compile that app. Install the missing packages and retry.

It is quite often easier to find a ready to go package suited for
your distro. Use your distro provided tools yum/urpmi or whatever
your distro provides, you don't mention.

> pls guide me

> one more quesiotn

> i have installed mozill rpm that also i am not able to run the
> application

Try 'rpm -ql mozilla' to see where it was installed, presuming
you can't run it as you do not know where the executable is?

If you don't know the exact package name:

rpm -qa | grep -i mozilla

Or alike

If you do have a file but don't know which package installed it:

rpm -qf /path/to/somefile

Try 'man rpm' there are quite some other useful switches you want
to explore.

> i have installed yahoomessenger rpm . but i dont know how to run the
> messenger

Same here, use your package manager to check where it has
installed things.

rpm -ql <package_name>

Replace <package_name> with the actual name.

To query a package not installed you can use this:

rpm -qlip /path/to/package.rpm

Good luck

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 129: The ring needs another token

Michael Heiming wrote:

>> i copied this file to /opt then i unziped that file and extracted
>> that file using the following comands
>
> Don't put source there, use your own $HOME or /usr/local/src or
> alike.

Why not /opt , as a matter of interest?
What exactly is /opt for?
[I might say I would have saved it in /usr/local , as you suggest.]

--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

On Tue, 06 Mar 2007, in the Usenet newsgroup comp.os.linux.networking, in
article <VneHh.18428$(E-Mail Removed)>, Timothy Murphy wrote:

>Michael Heiming wrote:

>>> i copied this file to /opt then i unziped that file and extracted
>>> that file using the following comands
>>
>> Don't put source there, use your own $HOME or /usr/local/src or
>> alike.
>
>Why not /opt , as a matter of interest?
>What exactly is /opt for?

http://www.pathname.com/fhs/

---------
/opt : Add-on application software packages

Purpose

/opt is reserved for the installation of add-on application software packages.

A package to be installed in /opt must locate its static files in a separate
/opt/<package> or /opt/<provider> directory tree, where <package> is a name
that describes the software package and <provider> is the provider's LANANA
registered name.
---------

>[I might say I would have saved it in /usr/local , as you suggest.]

Interestingly, the FHS doesn't require/recommend a /usr/local/src/ but
it has been installed by many distributions I've used over the years, and
I would have created such hierarchy on any install lacking it.

[compton ~]$ grep builder /etc/passwd
builder:x:65523:65523:Software Building account:/usr/local/src:/bin/bash
[compton ~]$ grep builder /etc/group
builder:*:65523:builder

Those are not distribution or UNIX standard accounts. They are on our systems
because a software auditor from corporate recommended them. Neither user or
group accounts own ANY other files/directories. The user has permissions of
'others' which is to say they can write to /tmp/ and /usr/tmp (other than
their home directory) and that is all.

Tarballs are unpacked in /usr/local/src/ then audited and built there. If the
software does not _require_ root permission to _run_ (for example, it's not
opening a network socket), then the software is test run from the source
directory by the 'builder' user, so that if something goes horribly wrong,
'builder' is the only user effected. Only when things are correct is root
needed to _install_ the software so that regular users can then run it.

We've been using this method WITHOUT PROBLEMS for over twenty years - yes,
that predates Linux.

Old guy