www.delorie.com/archives/browse.cgi | search |
Date: | Sun, 17 Dec 2000 19:17:30 +0200 (WET) |
From: | Andris Pavenis <pavenis AT lanet DOT lv> |
To: | Laurynas Biveinis <lauras AT softhome DOT net> |
Cc: | DJGPP Workers <djgpp-workers AT delorie DOT com> |
Subject: | Re: gcc-2.95.* for DJGPP |
In-Reply-To: | <3A3CE9F9.FA946CCB@softhome.net> |
Message-ID: | <Pine.A41.4.05.10012171914330.66800-100000@ieva06.lanet.lv> |
MIME-Version: | 1.0 |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
On Sun, 17 Dec 2000, Laurynas Biveinis wrote: > Andris Pavenis wrote: > > So either gcc_2_95 branch is broken (it's so with libio, but maybe also > > with objc) or there is something weird with that PIII box ... > > GCC 2.95 does not have any real PIII support, AFAICT. So I could try > bootstrapping it with my PII, this should make no difference and indicate > is it a GCC bug or faulty hardware. Did you use any configure/make options? > Initially not: simply '../gcc/configure; make bootstrap;' (under Linux). For DJGPP I used the same way I used for gcc-2.95.2 I bootstrapped it here for DJGPP on Celeron 366 without problems (other than libio ones) Andris
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |