>>>>> "CY" == C Y <smustudent1@yahoo.com> writes:
CY> --- Raymond Toy <toy@rtp.ericsson.se> wrote:
>> Isn't this normally done as follows:
>>
>> mkdir maxima-on-gcl
>> cd maxima-on-gcl
>> ../configure --use-gcl
>> ...
>> cd ..
>> mkdir maxima-on-cmucl
>> cd maxima-on-cmucl
>> ../configure --use-cmucl
>> ...
CY> No reason to make the user do all the mkdir stuff and whatnot
CY> by hand - that's what configure is all about. The compile for
CY> each may proceed in it's own directory, but unless he/she
CY> wishes to there should be no reason to know those details of
CY> the process. Usually what happens when I compile stuff on
CY> Linux is that different parts get built in different
CY> directories, so what you are suggesting above is what
CY> configure does, but the user only ever supplies three commands
CY> - configure with options, make, and make install. (OK,
CY> occasionally make test too.) Configure is typically very smart
CY> (or rather the person who has set it up is) so it handles all
CY> that automatically.
Your example is a bit different because you don't normally build some
package "foo" so that it can use some other package "bar" and "baz"
and "quux" all at the same time.
Having said that, yes, you can probably make configure do this.
Ray