Compile question...

**vwgtiturbo** · 02-02-2004, 03:14 AM

This in reference to my question about compiling from source...
I decided to read the Slack FAQ (real genius, eh?) and found this...
To create a Slack package, you will need to "Compile per program author instructions..."

Now, does this mean that I need to 'configure/make' and not install, or do I need to also make install? Seems kind of pointless to make install, then just delete it so you can install with pkgtool... Maybe I am missing something here...

**trommaster** · 02-02-2004, 03:15 AM

'conpile'
i would assume you just need to
./configure
make

**gaxprels** · 02-02-2004, 04:08 AM

http://www.talug.org/howto/Steps_to_...k_package.html

If you read that link, it will tell you exactly how to make your own slackware package from a source tarball

**vwgtiturbo** · 02-02-2004, 06:06 AM

Sweet.. Thanks. It doesn't make sense why you need to install it first though... kind of defeats the purpose... Oh well, I guess it makes sense that way if you want it to be ready to install in the future...

**gaxprels** · 02-02-2004, 12:30 PM

The whole purpose behind the Slackware package tarball is to install a binary... basically by installing to a directory where you don't install anything else, it can just open the tarball and copy the contents to the appropriate directories

Making your own package is usually to make it easier for others to install the same software on THEIR slackware systems (or to make it easier to install on multiple slackware installations you own.) Given that, it makes perfect sense

**vwgtiturbo** · 02-02-2004, 06:11 PM

When you compile something, does it 'detect' what architecture you are running on, and optimize the code for it, or do you need to specify with --march flags?

**paradox** · 02-02-2004, 06:51 PM

Generally as far as I know it compiles it for your general architecture ie 686, 386, 586, blah blah blah. You would want to optimize it if you want the most speed out of it.

Aragorn

**gaxprels** · 02-02-2004, 07:04 PM

Generally, when you do "./configure && make && make install" what happens is this:

configure determines your system type, compiler version, libraries available, etc... it also checks that all dependancies are available so the program will compile. The configure process produces a custom Makefile for your computer and then make uses that to compile the source and install it.

In short... if you read the first couple of lines produced by "./configure" you'll see what architecture it recognizes your system as.