OK folks, here's the problem.

I just installed a source package but accidentally deleted the source!
I've tried downloading the source again, but a simple 'make uninstall'
fails because uninstall isn't a target.

In order to make it a target, I have to run 'configure', which will
fail because the package is already installed.

The package isn't small enough to manually remove, and I don't know
other way to remove it.

Is there an obvious trick I'm missing here?

Thanks in advance for any ideas.

"colin353" <colin353@gmail.com> wrote in
news:1154828263.697777.17180@m79g2000cwm.googlegro ups.com:

> OK folks, here's the problem.
>
> I just installed a source package but accidentally deleted the source!
> I've tried downloading the source again, but a simple 'make uninstall'
> fails because uninstall isn't a target.
>
> In order to make it a target, I have to run 'configure', which will
> fail because the package is already installed.
>
> The package isn't small enough to manually remove, and I don't know
> other way to remove it.
>
> Is there an obvious trick I'm missing here?
>
> Thanks in advance for any ideas.
>
>

Do another ./configure make and make install *exactly* as you did before
and with the make install instead do make install&>install.out. and when
it's done read through install.out and remove the files where it says it
put them - that's what the output is. On a general note I think that
anyone who writes such a package - and there are more than there were 5
years ago, should be sent back to highschool to learn quickbasic as
punishment.

--
(setq (chuck nil) car(chuck) )

colin353 wrote:
> OK folks, here's the problem.

> I just installed a source package but accidentally deleted the source!
> I've tried downloading the source again, but a simple 'make uninstall'
> fails because uninstall isn't a target.

> In order to make it a target, I have to run 'configure', which will
> fail because the package is already installed.

Change the name of the executable then run configure. Change the name back and
make uninstall.

> The package isn't small enough to manually remove, and I don't know
> other way to remove it.

But once configured you will see every place it is installed so it may take
some time but you shouldn't miss anything.

> Is there an obvious trick I'm missing here?

--
Sturgeon's Law: 90% of everything is crap.
Giwer's Law: Sturgeon was an optimist.
-- The Iron Webmaster, 3674
nizkor http://www.giwersworld.org/nizkook/nizkook.phtml
flying saucers http://www.giwersworld.org/flyingsa.html a2

Matt Giwer <jull43@tampabay.REMover.rr.com> writes:

>colin353 wrote:
>> OK folks, here's the problem.

>> I just installed a source package but accidentally deleted the source!

What package? How did you install it? Was it via tarball or via a package
manager (eg rpm)?

>> I've tried downloading the source again, but a simple 'make uninstall'
>> fails because uninstall isn't a target.

So the makers of the program have not given you a way of uninstalling the
program. The only way then is to uninstall it by hand.


>> In order to make it a target, I have to run 'configure', which will
>> fail because the package is already installed.

No idea why configure will fail. Most tarballs do not care if the program
is already installed. What program do you have? Have you tried it, or is
this all based on some weird theory of how programs work that you have
invented?


> Change the name of the executable then run configure. Change the name back and
>make uninstall.

??? What executable?


>> The package isn't small enough to manually remove, and I don't know
>> other way to remove it.

> But once configured you will see every place it is installed so it may take
>some time but you shouldn't miss anything.

>> Is there an obvious trick I'm missing here?

Yes, use the package manager for your distribution rather than using the
tarball.

Alright guys, thanks for the help.

I've solved the problem by finding the exact source package and
reconfiguring, then using a simple
'make uninstall' to remove the package.

That's all I had to do.

> What package? How did you install it? Was it via tarball or via a package
> manager (eg rpm)?

The package was a tarball of GTK+-2.8.16. Of course, had I used rpm or
dpkg for installing, it would have been easy.

> Yes, use the package manager for your distribution rather than using the
> tarball.

Slackware 10.2 has an RPM system, but I much prefer installing things
from source, if not for the configuration options, then for
dependencies issues I had with RPM.

Anyway, that seems to be the way to do it. I tried routing the output
of 'make install' to a text file and then manually deleting the files,
as chuckcar suggested, but it was full of lots of useless information
and it didn't work so well.

> No idea why configure will fail.

Actually, I was confused by dependency problems. Foolishly, I
uninstalled another package that GTK was dependent on in the hopes of
crippling GTK. Don't ask me what I was thinking.

Later on, I tried reinstalling another version of the removed package
to restore GTK to working order so that I could remove it using 'make
uninstall'. Needless to say, it caused GTK to fail because two
conflicting versions of the same software were installed.

Anyway, it's all sorted out. Most of the complications were my own
fault. I guess it's all part of learning, eh?

Anyway, the solution is to find the exact same source tarball and
configure it, then do 'make install'.

Unruh wrote:
> Matt Giwer <jull43@tampabay.REMover.rr.com> writes:
>
> >colin353 wrote:
> >> OK folks, here's the problem.
>
> >> I just installed a source package but accidentally deleted the source!
>
> What package? How did you install it? Was it via tarball or via a package
> manager (eg rpm)?
>
> >> I've tried downloading the source again, but a simple 'make uninstall'
> >> fails because uninstall isn't a target.
>
> So the makers of the program have not given you a way of uninstalling the
> program. The only way then is to uninstall it by hand.
>
>
> >> In order to make it a target, I have to run 'configure', which will
> >> fail because the package is already installed.
>
> No idea why configure will fail. Most tarballs do not care if the program
> is already installed. What program do you have? Have you tried it, or is
> this all based on some weird theory of how programs work that you have
> invented?
>
>
> > Change the name of the executable then run configure. Change the name back and
> >make uninstall.
>
> ??? What executable?
>
>
> >> The package isn't small enough to manually remove, and I don't know
> >> other way to remove it.
>
> > But once configured you will see every place it is installed so it may take
> >some time but you shouldn't miss anything.
>
> >> Is there an obvious trick I'm missing here?
>
> Yes, use the package manager for your distribution rather than using the
> tarball.

"colin353" <colin353@gmail.com> writes:

>Alright guys, thanks for the help.

>I've solved the problem by finding the exact source package and
>reconfiguring, then using a simple
>'make uninstall' to remove the package.

>That's all I had to do.

>> What package? How did you install it? Was it via tarball or via a package
>> manager (eg rpm)?

>The package was a tarball of GTK+-2.8.16. Of course, had I used rpm or
>dpkg for installing, it would have been easy.

>> Yes, use the package manager for your distribution rather than using the
>> tarball.

>Slackware 10.2 has an RPM system, but I much prefer installing things
>from source, if not for the configuration options, then for
>dependencies issues I had with RPM.

urpmi from Mandr{ake,iva} handles those with ease. I would suggest
installing it on your system and using it with the rpms.

Many tarballs do not have an uninstall option.

And dependencies are actually usefull, since if your system is compiled for
some library it will not run without that library.

>Anyway, that seems to be the way to do it. I tried routing the output
>of 'make install' to a text file and then manually deleting the files,
>as chuckcar suggested, but it was full of lots of useless information
>and it didn't work so well.

.....

"colin353" <colin353@gmail.com> wrote in
news:1154889213.949199.252480@i42g2000cwa.googlegr oups.com:

> Alright guys, thanks for the help.
>
> I've solved the problem by finding the exact source package and
> reconfiguring, then using a simple
> 'make uninstall' to remove the package.
>
> That's all I had to do.
>
>> What package? How did you install it? Was it via tarball or via a
>> package manager (eg rpm)?
>
> The package was a tarball of GTK+-2.8.16. Of course, had I used rpm or
> dpkg for installing, it would have been easy.
>
>> Yes, use the package manager for your distribution rather than using
>> the tarball.
>
> Slackware 10.2 has an RPM system, but I much prefer installing things
> from source, if not for the configuration options, then for
> dependencies issues I had with RPM.
>
> Anyway, that seems to be the way to do it. I tried routing the output
> of 'make install' to a text file and then manually deleting the files,
> as chuckcar suggested, but it was full of lots of useless information
> and it didn't work so well.
>
>> No idea why configure will fail.
>
> Actually, I was confused by dependency problems. Foolishly, I
> uninstalled another package that GTK was dependent on in the hopes of
> crippling GTK. Don't ask me what I was thinking.
>
> Later on, I tried reinstalling another version of the removed package
> to restore GTK to working order so that I could remove it using 'make
> uninstall'. Needless to say, it caused GTK to fail because two
> conflicting versions of the same software were installed.
>
> Anyway, it's all sorted out. Most of the complications were my own
> fault. I guess it's all part of learning, eh?
>
> Anyway, the solution is to find the exact same source tarball and
> configure it, then do 'make install'.
>
Glad to see you worked it out - without knowing the *exact*
circumstances - I assumed you just used a normal source tarball - we
really couldn't asnwer any more specifically. BTW the method I suggested
will *always* work if there is a make install - although as you said, it
does involve wading through some output - lots of what linux is about
anyways though ;-)


--
(setq (chuck nil) car(chuck) )

Unruh <unruh-spam@physics.ubc.ca> wrote in
news:eb5pqi$f7s$1@nntp.itservices.ubc.ca:

> "colin353" <colin353@gmail.com> writes:
>
>>Alright guys, thanks for the help.
>
>>I've solved the problem by finding the exact source package and
>>reconfiguring, then using a simple
>>'make uninstall' to remove the package.
>
>>That's all I had to do.
>
>>> What package? How did you install it? Was it via tarball or via a
>>> package manager (eg rpm)?
>
>>The package was a tarball of GTK+-2.8.16. Of course, had I used rpm or
>>dpkg for installing, it would have been easy.
>
>>> Yes, use the package manager for your distribution rather than using
>>> the tarball.
>
>>Slackware 10.2 has an RPM system, but I much prefer installing things
>>from source, if not for the configuration options, then for
>>dependencies issues I had with RPM.
>
> urpmi from Mandr{ake,iva} handles those with ease. I would suggest
> installing it on your system and using it with the rpms.
>
> Many tarballs do not have an uninstall option.
>
> And dependencies are actually usefull, since if your system is
> compiled for some library it will not run without that library.
>

And if you try to compile - it won't making install impossible anyways.

--
(setq (chuck nil) car(chuck) )