Re: [SPAM UNSURE] gnatfind is missing from GCC v11 and newer

[Simon Wright]

I’m very sorry; they ARE there in the ELPA package (also in 1.0.4).

Stephe, are you running a system where e.g. cd ignores any argument that isn’t 
a directory?

> On 25 Oct 2023, at 20:47, Simon Wright <simon.j.wright@mac.com> wrote:
> 
> No, it wasn’t. Perhaps Stephe posted it a a patch?
> 
> I don’t know where emacs_gpr_query_config_devel.gpr etc come from, they 
> aren’t there in the elpa package either!
> 
>> On 25 Oct 2023, at 18:12, Left Right <olegsivokon@gmail.com> wrote:
>> 
>> Sorry, I realized now I botched the message with a bunch of
>> copy-paste.  The "find -type d" is something I added to fix the
>> problem. It wasn't there before.
>> 
>> On Wed, Oct 25, 2023 at 6:56 PM Simon Wright <simon.j.wright@mac.com> wrote:
>>> 
>>> On 25 Oct 2023, at 17:19, Left Right <olegsivokon@gmail.com> wrote:
>>>> 
>>>> When trying to run build.sh in gpr_query I ran into a problem with the 
>>>> line:
>>>> 
>>>> I altered it like this to overcome the problem:
>>>> 
>>>> ./build.sh: line 15: cd: too many arguments
>>>> 
>>>> if type alr; then
>>>>  # alr can be installed from https://alire.ada.dev/
>>>>  echo "building gpr_query via Alire; compiler:"
>>>>  alr toolchain
>>>>  alr get emacs_gpr_query~1.0.1
>>>>  cd $(find . -type d -name 'emacs_gpr_query_*') ; alr build --release
>>>> 
>>>> to my understanding, the problem was that it was finding another file
>>>> in this directory that also starts with emacs_gpr_query_, namely:
>>>> emacs_gpr_query_config_devel.gpr or
>>>> emacs_gpr_query_config_release.gpr. This behavior may be contingent on
>>>> what /bin/sh is on any given system.
>>> 
>>> It’s finding another *directory* (the "find -type d") . I’m guessing that a 
>>> previous build downloaded version 1.0.1 to emacs_gpr_query_1.0.1_ad2db6d2/, 
>>> but since there’s now a version 1.0.2 there’d be a new directory 
>>> emacs_gpr_query_1.0.2_????????/, making 2 directories, hence the problem. 
>>> You could delete the existing directory and try again?
>>> 
>>> I can’t replicate, because I can’t get 1.0.2; will post a separate message.
> 
>