[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: READ ME: updating mpc, mpfr, and eventually gmp
mueller6724%bellsouth.net@localhost ("Thomas Mueller") writes:
>from Paul Goyette:
>> I've had intermittent similar problems with NetBSD for at least three
>> years now. I have no idea what the problem is, though. I've
>> suspected some sort of memory corruption, but was never able to make
>> any progress in tracking it down.
>It could be a corruption or bug in NetBSD. I've come to expect these
>things with NetBSD.
>This is in particular a sudden inability to build NetBSD-current from source.
Those happen, and are usually fixed by reading UPDATING and doing what it
recommends (or in the case of obvious breaks, waiting a day, updating and
running the build again).
-current is built by umpteen people (like eg me), and on current and
releases and .. my Azubi even managed to build release on Linux with very
little coaching, it's not hard, usually.
If you can't get it built using build.sh with fairly simple mk.conf -ever-
(and not just "this one checkout"), there's something wrong with your
machine or installation.
>Until I see information about an update of base gcc, I don't plan to try
>any more using base gcc. I could try to build gcc-aux or gcc48 from pkgsrc
>and use that, if build is successful. I think I could set HOST_CC and
>HOST_CXX to tell the build to use that in place of base gcc.
That is IMO asking for interesting times.
Main Index |
Thread Index |