From: "Luke A. Guest" <laguest@archeia.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Adding Ada support
Date: Sat, 9 Dec 2023 15:24:28 +0000 [thread overview]
Message-ID: <fbca9c17-a76e-43f9-9c6b-e768669eb006@archeia.com> (raw)
In-Reply-To: <87msujtnkq.fsf@gentoo.org>
On 09/12/2023 15:12, Sam James wrote:
>
> "Luke A. Guest" <laguest@archeia.com> writes:
>
>> Hi,
>>
>> Can we add the following patch to the toolchain.eclass? I want to stop
>> having to mess with this overlay. The diff can be generated by
>> grabbing the repo https://github.com/Lucretia/ada-overlay and running
>> ./scripts/diff_eclass.sh.
>
> It'd be useful to send the whole lot with `git send-email` as proper
> patches which could be `git am`'d.
Can't really do that as you'd get a lot of stuff that's not required for
portage.
>>
>> The only thing I'm not sure about is the BDEPEND stuff.
>
> It looks OK from a glance.
>
>>
>> The reason for doing this is because gnat-gpl is dead, more info can
>> be found here https://www.adacore.com/community.
>>
>> The
>> https://github.com/Lucretia/ada-overlay/tree/master/dev-lang/ada-bootstrap
>> ebuilds provide bootstrap compilers, the archives are hosted on
>> dropbox, from 9.5.0 -> 14.
>>
>
> What is going to be a problem is using these. We'll need to build our
> own.
You can use those to build your own then as you need a bootstrap to
start with.
>> The scripts/build-bootstrap.sh script will build a bootstrap for a
>> particular version based on an env var.
>>
>
> But if this works, I guess that's fine. It would be nice if there were
> some we could use from elsewhere somewhat-official that other distros
> are using, but if they don't exist, I guess we have to live with it.
>
> We need to do the same for D.
As I said, these are built and packaged as tars, you could change the
script to add in d as well if you wanted. It's not a complex script, it
builds what is needed and dumps it to /tmp/opt/ and then installs it to
/opt with the ebuild.
>> As for anything in dev-ada/* well, the ada guy would need to work on
>> that really, I'm not really experienced enough to handle it properly.
>>
>
> Kind of curious as to your interest in Ada if you're not experienced
> enough - not intended derogatorily, just know you've been interested
> in Ada for a while so I wonder if dev-ada/* is somehow that different
> or what..
I'm not experienced enough with ebuilds.
>
> I also wouldn't want to merge something if it's then going to conflict
> with anything in dev-ada/*, so at least some coordination is required.
>
> (To that end, cc'd toolchain@ and ada@.)
Yes, as I state in the README, I disable all the ::gentoo ada stuff with
another script.
>> Given GCC is masked up to :10 now, the gnat gpr tools / libs might be
>> easier to get going with single versions covering numerous toolchain
>> versions.
>>
>> Alire would need to be added at some point, http://alire.ada.dev/ to
>> provide an easier way to get packages going.
>>
>> I originally envisioned gnatmake, gprbuild eclasses to cover building
>> simple projects with one entry point (gnatmake) and projects
>> (gprbuild). I think an alire based eclass would need to be added as
>> well.
>>
>> Thanks,
>> Luke.
>>
>> [2. text/x-patch; gentoo-diff.patch]...
>
>
next prev parent reply other threads:[~2023-12-09 15:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 15:04 [gentoo-dev] Adding Ada support Luke A. Guest
2023-12-09 15:12 ` Sam James
2023-12-09 15:24 ` Luke A. Guest [this message]
2023-12-09 15:30 ` Luke A. Guest
2023-12-09 15:37 ` Luke A. Guest
2023-12-09 15:51 ` Luke A. Guest
2023-12-09 23:40 ` Eli Schwartz
2023-12-09 17:55 ` Luke A. Guest
2023-12-09 18:08 ` Luke A. Guest
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fbca9c17-a76e-43f9-9c6b-e768669eb006@archeia.com \
--to=laguest@archeia.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox