| To: | "Ross A. Towle" <rat@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Configure |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Sat, 13 Jan 2001 16:56:57 +0100 |
| Cc: | pro64-support@xxxxxxxxxxx |
| In-reply-to: | <10101121310.ZM46924@xxxxxxxxxxxxxxxxxxx>; from rat@xxxxxxxxxxxxxxxxxxx on Fri, Jan 12, 2001 at 01:10:32PM -0800 |
| References: | <OF89ED4C76.F22F1800-ON882569D2.00720C14@xxxxxxxxxxxx> <10101121310.ZM46924@xxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-pro64-support@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Fri, Jan 12, 2001 at 01:10:32PM -0800, Ross A. Towle wrote: > The answer is no, we are not switching to Configure. > Right now, it is just as simple. Just gmake in the targ* > directories (depending upon your target). We need the > capability of building multiple targets from the same > sources without one build messing up another build (which is > a side effect of Configure). GNU autoconf supports building in separate directories without touching the original source tree. I do this all the time when building gcc. -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Header files for building libgcc, James Kingdon |
|---|---|
| Next by Date: | followup on inliner bug, David Goodwin |
| Previous by Thread: | Re: Configure, James Kingdon |
| Next by Thread: | sgif90 -cpp errors, Wayne Vieira |
| Indexes: | [Date] [Thread] [Top] [All Lists] |