On 4 Nov 99, at 10:15, Mason Ip wrote:
../configure --enable-languages=pascal make bootstrap make install
Be careful, you might screw up the original gcc binary. The gcc-2.95.x/install/* did mention that if you use the "--enable-languages=" option, "make bootstrap" won't work. So, in the above case, "make bootstrap" will generate a copy of "gcc" which would be different from the case when you "make bootstrap" without the "--enable-languages=" option.
Before a fixed (and well tested) gpc INSTALL doc is released, I use the following work around.
- build GCC without "--enable-languages" option. And make install. This
does not build GPC. 2. backup the install-dir to a tar ball 3. build GPC with "--enable-languages=pascal" option. And make install. This build GPC with a "defective" GCC as by-product. Make Install. 4. restore the tar ball from step 2 back to the install-dir. This will over-write the "defective" GCC with the original good copy.
I tried this procedure with Cygwin. 'make bootstrap' produced both a GPC and a GCC compiler (taking 2 hours and eating 100mb of my hard disk in the process). Is this how it is supposed to behave?
Best regards, The Chief -------- Dr. Abimbola A. Olowofoyeku (The African Chief) Email: laa12@keele.ac.uk Homepage: http://ourworld.compuserve.com/homepages/African_Chief/ Author of: Chief's Installer Pro v5.20a for Win32 ftp://ftp.demon.co.uk/pub/ibmpc/win95/apps/chief32/chief52a.zip