This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: PR4114, 4113, 4082, 4078, (part of) 4096 plus other reports ingcc-bugs
- To: Phil Edwards <pedwards at disaster dot jaj dot com>
- Subject: Re: PR4114, 4113, 4082, 4078, (part of) 4096 plus other reports ingcc-bugs
- From: "Alan Piszcz 'peesh'" <apiszcz at mitre dot org>
- Date: Mon, 27 Aug 2001 14:36:07 -0400 (EDT)
- cc: Alexandre Oliva <aoliva at redhat dot com>, <rittle at labs dot mot dot com>, <libstdc++ at gcc dot gnu dot org>, <ungaro at pegasus dot fmrp dot usp dot br>, <partain at dcs dot gla dot ac dot uk>, <ajhood at fl dot net dot au>, <Hermann dot Rochholz at faidor dot de>, <gcc-bugs at gcc dot gnu dot org>, <karl at gnu dot org>, <bkoz at gcc dot gnu dot org>, <rkl at connect dot org dot uk>
i merely followed the instructions and am having no problems now...
we'll at least related to compiling.
FILE: configure-gcc
#!/bin/sh
echo "MUST BE in the top level source directory"
mkdir objdir
cd objdir
curDir=`pwd`
dirName=`dirname $curDir`
pkgName=`basename $dirName`
newDir="/app/$pkgName"
echo " pkgName: $pkgName"
echo " newDir: $newDir"
time ../configure \
--prefix=$newDir --enable-languages=c,c++,java,f77,objc
echo "to make 'cd objdir; time make'"
On Mon,
27 Aug 2001, Phil Edwards wrote:
> Date: Mon, 27 Aug 2001 13:02:51 -0400
> From: Phil Edwards <pedwards@disaster.jaj.com>
> To: Alexandre Oliva <aoliva@redhat.com>
> Cc: rittle@labs.mot.com, libstdc++@gcc.gnu.org, ungaro@pegasus.fmrp.usp.br,
> partain@dcs.gla.ac.uk, ajhood@fl.net.au, Hermann.Rochholz@faidor.de,
> gcc-bugs@gcc.gnu.org, karl@gnu.org, bkoz@gcc.gnu.org, rkl@connect.org.uk,
> apiszcz@mitre.org
> Subject: Re: PR4114, 4113, 4082, 4078,
> (part of) 4096 plus other reports in gcc-bugs
>
> On Sun, Aug 26, 2001 at 09:40:46AM -0300, Alexandre Oliva wrote:
> > <target>/[multilibdirs]libstdc++-v3/foo -> ../../[...]libstdc++-v3/foo
> >
> > You're probably wondering why. Think, for example, of libiberty: it's
> > built for the host in <toplevel_builddir>/libiberty and for the target
> > in <toplevel_builddir>/<target_alias>/[multilib]libiberty. When
> > srcdir=builddir, you'd get libiberty configured in the top-level
> > directory for the host build.
>
> That all makes sense. In my other message I was wondering why we do
> this all the time, and not (as the comments claim) only "if cross".
> For a native compile, shouldn't configuring for the host be the same as
> configuring for the target? I /know/ I'm missing somthing here.
>
>
> > As for clobbering the source tree in order to test this stuff, you may
> > use symlink-tree to create a mirror of the source tree and then build
> > in it, so it won't affect the actual source tree.
>
> I could have sworn that the Makefiles do this already. Isn't that why
> symlink-tree is in the source in the first place? (Beats me why it never
> gets called.)
>
>
> Phil
>
> --
> Would I had phrases that are not known, utterances that are strange, in
> new language that has not been used, free from repetition, not an utterance
> which has grown stale, which men of old have spoken.
> - anonymous Egyptian scribe, c.1700 BC
>
- ___________.___________________.________
- < Al Piszcz | apiszcz@mitre.org | MITRE >