From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: =?UTF-8?B?QmrDtnJu?= Persson Newsgroups: comp.lang.ada Subject: Crash problem with GNAT in Fedora 18 (was: Introducing Comfignat) Date: Wed, 14 Aug 2013 15:13:55 +0200 Message-ID: <20130814151355.669a5e5d@hactar.xn--rombobjrn-67a.se> References: <1375896729.30906.2.camel@speedy.xn--rombobjrn-67a.se> <20130810175217.04eb4dc639e40f35e96be212@iki.fi> <1376298237.5037.16.camel@speedy.xn--rombobjrn-67a.se> <20130813172436.db43b249304b6d85edf123b7@iki.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: individual.net 1HgaT39OAi7sQ2+gRbE2XAEdPxAXka/z43BC99vXr3HlbijaHC Cancel-Lock: sha1:RoECK43dTQYkmqAH/LW3HV/SjTg= X-Newsreader: Claws Mail 3.9.0 (GTK+ 2.24.13; x86_64-redhat-linux-gnu) Xref: news.eternal-september.org comp.lang.ada:16853 Date: 2013-08-14T15:13:55+02:00 List-Id: Tero Koskinen wrote: > However, next problem seems to be that anything linked with Ahven > crashes if Ahven is compiled with base gcc/gnat on Fedora 18. > GNAT GPL 2012 works, so it is base gcc/gnat problem on Fedora. > (And I made sure that I have static libgnat installed, so the crash > isn't directly related to it.) That sounds like it might be the initialization bug in GPRbuild 2011: https://bugzilla.redhat.com/show_bug.cgi?id=3D853866 If so, you might want to upgrade to Fedora 19 which has GPRbuild 2012. As a quick test to see if the bug is in GPRbuild you can set GNAT_BUILDER=3Dgnatmake on the Make command line. > But that isn't a problem in comfignat itself, so I think I'll file a > bug to Fedora bug tracker (or just send email to you) once I sort the > problem out. I'm not a GCC or GPRbuild maintainer so I would be the wrong person to send email to. If it turns out to be a problem with how GCC is packaged in Fedora, then please report it in Red Hat Bugzilla. If the bug is present in upstream GCC, then it's probably better to report it in GCC Bugzilla. Bj=C3=B6rn Persson