./configure question

Road · 04-04-2002, 10:58 PM

Exactly what is the proper way to use the configure command before you use make.

Is it

[promt]./configure --enable-option1 --enable-option2 --enable-option3

or is
[promt]./configure --enable-option1
[promt]./configure --enable-option2
[promt]./configure --enable-option3

Or neither.

If that makes no sense I am basically asking what is the proper format for ./configure with multiple options, is it one per configure command or all grouped?

trickykid · 04-04-2002, 11:30 PM

I would think its best to have all the options the first time. Then go on to make, that way you wouldn't have to do a ./configure 3 or 4 times.. then move on to make... then make install.. etc etc..

-trickykid

neo77777 · 04-04-2002, 11:30 PM

I believe putting the options in one line is a proper way, because if you will run ./configure as many times as you want to include different options it will overwrite the every configuration you want to set up

AutoBot · 04-05-2002, 02:29 AM

Example:

./configure --prefix=/usr && make
su
make install
make clean

Road · 04-05-2002, 01:45 PM

So if its supposed to be one line do I seperate it a comma or anything like that.

Example
./configure --enable-option1, --enable-option2, ect

Or just a space without the comma

Or is like this,

./configure --enable-option1-option2-option3-ect.

The reason why I am asking is because I am having trouble getting a POP3 to configure correctly and I want to make sure its not because of my compile.

Thanks again,

Road

acid_kewpie · 04-05-2002, 01:49 PM

it's the same as giving command line options to any program.

programname --option1 --option2

jrmann1999 · 04-05-2002, 03:16 PM

a real easy way is to put a \ at the end of each option, like:

# ./configure --enable-option-1 \
> --enable-option-2 \
> --enable-option-3

this translates itself to:
# ./configure --enable-option-1 --enable-option-2 --enable-option-3

J

Road · 04-05-2002, 03:23 PM

Thanks that completly clears it up.

THanks for everybodies help.