From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on ip-172-31-65-14.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00,FREEMAIL_FROM, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Received: by 2002:a37:5886:0:b0:763:a2ec:27e7 with SMTP id m128-20020a375886000000b00763a2ec27e7mr2388851qkb.7.1687805809985; Mon, 26 Jun 2023 11:56:49 -0700 (PDT) X-Received: by 2002:a81:a703:0:b0:576:6e4e:b87f with SMTP id e3-20020a81a703000000b005766e4eb87fmr4712940ywh.10.1687805809839; Mon, 26 Jun 2023 11:56:49 -0700 (PDT) Path: eternal-september.org!news.eternal-september.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 26 Jun 2023 11:56:49 -0700 (PDT) In-Reply-To: <87v8fb1acr.fsf@nosuchdomain.example.com> Injection-Info: google-groups.googlegroups.com; posting-host=72.86.43.83; posting-account=QF6XPQoAAABce2NyPxxDAaKdAkN6RgAf NNTP-Posting-Host: 72.86.43.83 References: <266fe78e-5e0e-4b2e-afc2-b1bf6771b082n@googlegroups.com> <87v8fb1acr.fsf@nosuchdomain.example.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <1f88aebf-f1f2-46fa-b66a-4e605d7ff202n@googlegroups.com> Subject: Re: I have gnat 13.1.0 on my M1 Mac; I'd like to have my own Ada+GNAT *.ad[sb] library files, where are they? From: Jere Injection-Date: Mon, 26 Jun 2023 18:56:49 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Received-Bytes: 3001 Xref: news.eternal-september.org comp.lang.ada:65350 List-Id: On Sunday, June 25, 2023 at 5:49:11=E2=80=AFPM UTC-4, Keith Thompson wrote: > Simon Wright writes:=20 > [...] > > But you say you know that. I wonder whether it's the crunched filenames= =20 > > that are confusing? (a legacy of the days when DOS 8.3 filenames were= =20 > > required for a large part of GNAT's target audience). You can find the= =20 > > crunched filename for a package using gnatkr (gnat krunch):=20 > > > > $ gnatkr ada.sequential_io.ads=20 > [fixed typo] > > a-sequio.ads=20 > >=20 > > (you don't actually need whatever's after the final period to be the=20 > > actual file extension: you could use '.open' or just '.'). > Which raises a question: Why does GNAT still use crunched filenames? It= =20 > probably makes sense to continue to support them (does anyone use GNAT=20 > on MS-DOS?), but I wouldn't think it would be difficult to use full file= =20 > names on the vast majority of systems that support them. It's not a=20 > huge deal, but using full file names where possible would be less=20 > annoying.=20 Unless they changed how the GNAT compiler works in the last few years, then= my guess is inertia to do that. Right before the pandemic hit, I had the neat idea of doing m= y own bare metal=20 runtime and to use normal uncrunched names. The RTS compiled just fine doi= ng that. However, when I tried to use the RTS to build a full fledged program, it failed to f= ind the package in the RTS. I don't recall if it failed at compile time or link time, but crunching the= names and recompiling the RTS fixed the issue. So something in their compiler requires the crunched = names, or if they have since changed that, used to require it.