[ see parents for my build problems ]
On Thu, Sep 04, 2008 at 02:00:11PM -0700, Ian Lance Taylor wrote:
> These days autoconf likes to dump a whole bunch of cruft at the end of
> config.log. You have to look above all the cruft, which is usually
> most of the file, to find the actual failing test
Joe Buck <[EMAIL PROTECTED]> writes:
> But ia64-unknown-linux-gnu/libgcc/config.log doesn't have any useful
> details. It has
>
> CC='/remote/atg5/jbuck/gcc-4.3.2-ia64build/./gcc/xgcc
> -B/remote/atg5/jbuck/gcc-4.3.2-ia64build/./gcc/
> -B/u/jbuck/cvs.ia64/4.3.2/ia64-unknown-linux-gnu/bin/
> -B
On Thu, Sep 04, 2008 at 11:12:59AM -0700, Joe Buck wrote:
> > I also found an ia64 box running Red Hat Advanced Workstation 2.1.
> > Yes, I know, really old, but I can't change it. I tried a build...
> > but the bootstrap died.
On Thu, Sep 04, 2008 at 11:37:47AM -0700, Joe Buck wrote:
> I think
On Thu, Sep 04, 2008 at 11:12:59AM -0700, Joe Buck wrote:
> I also found an ia64 box running Red Hat Advanced Workstation 2.1.
> Yes, I know, really old, but I can't change it. I tried a build...
> but the bootstrap died.
I think the issue was that the --with-gmp and --with-mpfr directories
weren
I located a couple of old machines to try, so I have two more successful
build reports, and one failure (though don't worry about the failure yet).
First one (includes C, C++, ObjC, Fortran, and Java)
i686-pc-linux-gnu on a RHEL 3 system.
boot compiler: gcc 3.3.6 (FSF release)
kernel: 2.4.21-32.E
