pro64-support
[Top] [All Lists]

Re: Configure

To: pro64-support@xxxxxxxxxxx
Subject: Re: Configure
From: James Kingdon <jkingdon@xxxxxxxxxxxxxxxxxxx>
Date: Fri, 12 Jan 2001 18:55:01 -0800
Cc: jkingdon@xxxxxxxxxxxxxxxxxxxx
References: <OF89ED4C76.F22F1800-ON882569D2.00720C14@conexant.com> <10101121310.ZM46924@cchkms.engr.sgi.com>
Sender: owner-pro64-support@xxxxxxxxxxx
"Ross A. Towle" wrote:
> 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 configure handles this with the --srcdir argument to configure
(which is the default if you specify a configure script in another
directory other than where you are running configure from).

For example, here's how you can build both a ia32 native GCC
compiler and a ia32 x ia64 compiler from the same source tree
(I think I even did it with the source tree being read-only
although there are a few minor annoyances related to yacc and
makeinfo and such, which generate non-platform-specific generated
files):

  On an ia32 system, go to OBJDIR32 and issue the following commands: 

    SRC/gcc/configure --enable-languages=c++ --disable-nls
    make bootstrap

  On an ia32 system, go to OBJDIR64 and issue the following commands: 

    SRC/gcc/configure --enable-languages=c++ --target=ia64-unknown-linux
--disable-nls
    make

(for those within SGI, this is an excerpt from
http://sahara/ia64/merge.html
although it could go on a public site if anyone actually cares).

Having said all that, I'm not sure I see a lot of reasons to
autoconfiscate
Pro64.  But it does have this particular feature.  (There's also the
"hmm,
interesting idea, you feel like working up some patches to see what
would
be involved in autoconfiscating it?" response.... :-)).

<Prev in Thread] Current Thread [Next in Thread>