From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on ip-172-31-74-118.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Received: by 2002:ac8:23e3:: with SMTP id r32mr54161025qtr.268.1594109594421; Tue, 07 Jul 2020 01:13:14 -0700 (PDT) X-Received: by 2002:a05:6820:172:: with SMTP id k18mr37333779ood.69.1594109594200; Tue, 07 Jul 2020 01:13:14 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 7 Jul 2020 01:13:13 -0700 (PDT) In-Reply-To: <53e66aa5-c298-4b27-8718-386e7a624141o@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: google-groups.googlegroups.com; posting-host=79.46.127.221; posting-account=JRF_-woAAABYlsAtkCl_CUxBuQy2SsaQ NNTP-Posting-Host: 79.46.127.221 References: <242465de-0171-44b1-9618-752b22c3604co@googlegroups.com> <11c21c57-69de-4fcb-9193-71a98ca93ecao@googlegroups.com> <126727e4-3108-46cd-acc6-e42dbdb9dd6bo@googlegroups.com> <011aef92-84e3-47e5-a558-a8c2c6504161o@googlegroups.com> <8959b86d-ec38-4e0b-a272-384751914732o@googlegroups.com> <16b49b03-8657-425d-bad5-67cc5fe725d2o@googlegroups.com> <891fe070-40a4-4ba2-a7be-a7e9c4c036a4o@googlegroups.com> <04195e55-a82f-4035-a05d-5078ea2e6259o@googlegroups.com> <2790711b-d169-4a19-b666-5853eb0f5268o@googlegroups.com> <7052e60c-33ad-4961-9a2c-76014bd6c516o@googlegroups.com> <6efbebf3-8dd2-4909-ab48-d57ba39dc309o@googlegroups.com> <7e2ea50e-412b-421a-b842-e97014043e37o@googlegroups.com> <24f16e6b-e885-4dc5-8519-05c6a786f4dfo@googlegroups.com> <53e66aa5-c298-4b27-8718-386e7a624141o@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <43a34342-88a2-4af3-b146-817192dab5b7o@googlegroups.com> Subject: Re: SweetAda 0.1 released From: gabriele.galeotti.xyz@gmail.com Injection-Date: Tue, 07 Jul 2020 08:13:14 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader01.eternal-september.org comp.lang.ada:59375 List-Id: On Tuesday, July 7, 2020 at 9:20:34 AM UTC+2, Roger wrote: > Although /opt/sweetada/bin/make run produced IOEMU and QEMU windows neith= er of those or the menu bar was responsive. > The terminal window associated with one of them did respond with XYZ. >=20 > When I get the QEMU window to go full-screen it contains the message: > Guest has not initialized the display (yet) >=20 > I also tried running toolchain tools directly, such as qemu-img, but they= failed with=20 > dyld: Library not loaded: /usr/x86_64-apple-darwin15/darwin/usr/local/lib= /libgthread-2.0.0.dylib > Referenced from: /opt/sweetada/bin/qemu-img > Reason: image not found >=20 > Also: > /opt/sweetada/bin/x86_64-sweetada-elf-gnatmake =20 > fatal error, run-time library not installed correctly > cannot locate file system.ads > raised TYPES.UNRECOVERABLE_ERROR : targparm.adb:183 >=20 > x86_64-sweetada-elf-gnatmake: INTERNAL ERROR. Please report. >=20 > Hoping this helps > Roger If you see the XYZ characters on a terminal, then QEMU is running fine, and= you are seeing CPU sending characters through a serial port. You don't see= other things because there is nothing else on the terminal, as I said Swee= tAda is essentially a framework and the code does very little. The main win= dow of QEMU does display the VGA screen of the emulated platform, which is = not used. IOEMU should display a pulsing 8-bit register (the CPU is in a lo= op counting forever), but if it didn't maybe there are some GUI problems ye= t to solve. If you want to execute the toolchain directly, then you have to know exactl= y what you want. You can call GNATMAKE, but then you have to supply the RTS= location, compiler switches and the source files of your project. If you a= ren't an embedded Ada developer, then there is no point in doing that. My feeling is that, after many test (sorry), you could have a corrupted env= ironment, since does sound strange to me that you have errors in running th= e new QEMU executable and the new libioemu library. Being said that, try to annotate your work and wait for me to collect furth= er info from other OSX users, so we can understand better where potential Q= EMU problems could arise. I appreciate your interest.