[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gcl-devel] Re: possible GCL/Windows compiler bug

From: Matt Kaufmann
Subject: Re: [Gcl-devel] Re: possible GCL/Windows compiler bug
Date: Sat, 23 Oct 2004 12:03:13 -0500

Hi --

OK, I downloaded/installed
and then I rebuilt ACL2 2.9 on top of it.  Then I did the usual experiment to
try to cause the Windows/GCL bug I'd been seeing:

(f-put-global 'safe-mode t state)
(ACL2_*1*_ACL2::MATCH-CLAUSE 'DCL '(& . &) '(T))

These commands completed without error.  So perhaps there was just a quirk in
the GCL build on Jared Davis's machine.

On the other hand, I repeatedly got this compiler error when I tried to certify

cc1.exe: unrecognized option `-fno-zero-initialized-in-bss'

Perhaps it's because I forgot to do this, or because I needed to point to the
new mingw somehow:

export PATH=/c/Progra~1/GCL-2.6.5-CLtL1/bin:${PATH}

(Instead, I specified the new gcl explicitly in the make command I used for
building ACL2.)

But anyhow, I only use Windows to help with testing, and the error went away,
so as far as I'm concerned, the case is closed.  Let me know if you need
anything further.

-- Matt
   From: "Mike Thomas" <address@hidden>
   Date: Tue, 19 Oct 2004 14:19:50 +1000
   Content-Type: text/plain;
   X-Priority: 3 (Normal)
   X-MSMail-Priority: Normal
   X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
   Importance: Normal
   X-SpamAssassin-Status: No, hits=-2.6 required=5.0
   X-UTCS-Spam-Status: No, hits=-272 required=180

   Hi Matt.

   | I have very little experience with this sort of stuff.  Is it
   | sufficient for me
   | to go to http://ftp.gnu.org/gnu/gcl/binaries/stable/ and fetch
   | gcl_2.6.5.mingw32_cltl1_japi_20040818.exe in Windows, then double-click or
   | such,

   Yes - double click, and follow the default choices.

   | and then build ACL2 with the installed gcl

   Yes.  You would need to add the GCL bin directory to the MSYS shell PATH as

      export PATH=/c/Progra~1/GCL-2.6.5-CLtL1/bin:${PATH}

   | and reproduce the error?



   Mike Thomas

reply via email to

[Prev in Thread] Current Thread [Next in Thread]