Damn Small Linux (DSL) Forums
Welcome, Guest. Please login or register.
Did you miss your activation email?
September 18, 2014, 01:46:06 PM

Login with username, password and session length
News
The new DSL forums are now open.
Stats
297728 Posts in 294151 Topics by 231 Members
Latest Member: JGreenwoo
Search:     Advanced search
* Home Help Search Login Register
Get The Official Damn Small Linux Book. Great VPS hosting provided by Tektonic

+  Damn Small Linux (DSL) Forums
|-+  Damn Small Linux
| |-+  Other Help Topics
| | |-+  configuring packages
« previous next »
Pages: [1] Print
Author Topic: configuring packages  (Read 1263 times)
carlo
Newbie
*
Posts: 12


View Profile
« on: April 19, 2013, 09:04:54 AM »

Hello

To install packages of sourceforge (for instance), I need to configure them first. Meanwhile I know it is possible to do "make" and "make install" with gcc, but how will I be able to do "./configure"? Is there a package in Debian I can install for it? Or what?
I have to mention that I have a full hd installation.

Thanks
« Last Edit: April 19, 2013, 12:12:49 PM by carlo » Logged
CNK
Full Member
***
Posts: 148


View Profile
« Reply #1 on: April 19, 2013, 10:28:29 PM »

"./configure" is a script included with most source code packages for Linux. Unlike the other commands, it exists in the directory of the program you want to compile (hence why you type "./" before it). You don't download it separately.

Often simply typing "./configure" will set things up automatically as required for your system. However you can type "./configure --help", or to scroll through the text, "./configure --help | less", to see a list of options that may be added to the "./configure" line in order to make specific choices about the compillation.

Also, just a note that gcc doesn't actually control the "make" command, there is a specific program called "make" for that, but gcc is used by it to compile the package.
Logged
carlo
Newbie
*
Posts: 12


View Profile
« Reply #2 on: April 21, 2013, 06:59:49 AM »

Thanks,

that explains a lot.
"Sourcecode package" does that mean, from "Sourceforge", or is that from Debian in our (DSL) case?
What I allso wanted to know is: When I want to start an installed package and the output is: errot while loading shared libraries (eg) 'gimpprint.so.1' no such file or directory, and I can't find gimpprint.so.1, why should this than work with gimpprint.dev?

Thanks again
Logged
CNK
Full Member
***
Posts: 148


View Profile
« Reply #3 on: April 22, 2013, 07:35:35 AM »

Source Code is the common way to distribute programs for Linux so that they can be used with a range of different distributions. If a project on Sourceforge offers a Linux version, it probably has the source package available, but many linux programs from elsewhere on the net will have them too. They usually have the "tar.gz" extension (or tar.xz, tar.bz2). Note though that the ".tar.gz" packages in the MyDSL repository are not Source Code packages.

For your second problem, if you downloaded a package for the program you're using, it might be looking for GIMP-print when it isn't installed on your computer. If you compiled it, you should check for a "./configure" option to disable GIMP-print. If the program can't run without GIMP-print for some reason, you might need to install it, though I'm not sure if it is compatible with DSL.
Logged
carlo
Newbie
*
Posts: 12


View Profile
« Reply #4 on: April 22, 2013, 01:32:27 PM »

Thanks
Logged
Pages: [1] Print 
« previous next »
Jump to:  

Powered by SMF 1.1.19 | SMF © 2013, Simple Machines
Mercury design by Bloc