You are not logged in.

#1 2009-05-14 07:22:28

Davey
Member
Registered: 2009-02-13
Posts: 4

What does configure/make/make install leave behind?

Hello everyone,

When I compile something from source with configure/make/make install, what does it leave behind (installfiles, tempfiles etc.)?

Thanks! roll

Offline

#2 2009-05-14 10:50:12

tomk
Forum Fellow
From: Ireland
Registered: 2004-07-21
Posts: 9,839

Re: What does configure/make/make install leave behind?

Everything in the build dir i.e. the dir you ran those commands in.

FYI, as you are using a package-managed distro, it's recommended that you create an Arch package, instead of installing directly into your system as you describe.

Offline

#3 2009-05-14 15:45:28

Davey
Member
Registered: 2009-02-13
Posts: 4

Re: What does configure/make/make install leave behind?

Thanks for the explanation.
I always use pacman, but pidgin kept crashing. So I tried to install from source (didn't work, didn't know where to get libgtk2.0-dev) but I ran some commands like libtoolize, autoconf, automake, but wasn't sure where it puts it's files.
(Pidgin is working better now btw, got it from other pacserver)

Offline

#4 2009-05-14 16:42:55

EVRAMP
Member
From: Czech Republic
Registered: 2008-10-03
Posts: 173
Website

Re: What does configure/make/make install leave behind?

I think what tomk suggested is to use ABS or PKGBUILD to create your own version if you need.
Writing own PKGBUILD is not hard at all and you will get as clean package as from repos + you learn something new.
There are no -dev packages in Archlinux. They are in Debian however, Archlinux includes header files directly in a package. Debian spreads them into -dev packages.

Last edited by EVRAMP (2009-05-14 16:44:12)

Offline

Board footer

Powered by FluxBB