ALR unable to get many packages

[Kenneth Wolcott]

Hi;

I am on a Mac Mini with an M1 chip and I have GNAT Ada 13.1 (thanks Simon!)

ALR does not work very well for me. I am unable to "alr get" many packages (see below for an example).

Updating the index does not help in most of these cases.

Is ALR incompatible with an external GNAT compiler?

What am I doing wrong here?

Thanks,
Ken Wolcott

alr --no-color get aws
Warning:
Warning: New solution is incomplete.
Warning: +i gnat 13.1.0 (new,installed,gnat_external)
Warning: + gnatcoll 23.0.0 (new)
Warning: + libgpr 23.0.0 (new,indirect)
Warning: + make 3.81.0 (new)
Warning: +~ openssl * (new,external)
Warning: + xmlada 23.0.0 (new)
Warning:
Warning: Could not find a complete solution for aws=23.0.0
Build will fail unless externals are made available, do you want to continue?
[Y] Yes [N] No (default is No) n
ERROR: Crate retrieval abandoned.

[Simon Wright]

Kenneth Wolcott <kenneth...@gmail.com> writes:

> I am on a Mac Mini with an M1 chip and I have GNAT Ada 13.1 (thanks Simon!)

I take it you're using the aarch64 (Apple silicon) version?

> ALR does not work very well for me. I am unable to "alr get" many
> packages (see below for an example).

Please let me know which (external) packages you're having trouble with.

> Updating the index does not help in most of these cases.
>
> Is ALR incompatible with an external GNAT compiler?

No.

Which version of alr are you using? If it's 2.0-dev (from my build, see
below, for Apple silicon) then it understands Homebrew.

https://github.com/simonjwright/alire-index.mac/releases/tag/alr_binary_aarch64-1.0.0

Not all index entries for external packages have been updated to include
Homebrew links (this includes openssl), but you should still be able to
say "brew install <whatever>" and have it work.

At present, you need to have something like this in your startup
scripts: working on it!

eval $(/opt/homebrew/bin/brew shellenv)
export C_INCLUDE_PATH=$HOMEBREW_PREFIX/include
export LIBRARY_PATH=$HOMEBREW_PREFIX/lib

> What am I doing wrong here?

Running past the wavefront :-(

> alr --no-color get aws

It took me a while to work out that I needed to use
--no-color. Investigating what's going wrong.

> Warning:
> Warning: New solution is incomplete.
> Warning: +i gnat 13.1.0 (new,installed,gnat_external)
> Warning: + gnatcoll 23.0.0 (new)
> Warning: + libgpr 23.0.0 (new,indirect)
> Warning: + make 3.81.0 (new)
> Warning: +~ openssl * (new,external)
> Warning: + xmlada 23.0.0 (new)
> Warning:
> Warning: Could not find a complete solution for aws=23.0.0
> Build will fail unless externals are made available, do you want to continue?
> [Y] Yes [N] No (default is No) n
> ERROR: Crate retrieval abandoned.

If you "brew install openssl" you should be able to say "Y" here.

I found there was an extra setting required:

alr build -- -XTARGET=aarch64-apple-darwin21

(find the correct setting by "gcc -v" and looking at the "Target:" line).

[Kenneth Wolcott]

On Saturday, August 5, 2023 at 12:28:59 AM UTC-7, Simon Wright wrote:

Hi Simon;

So I guess it is fair to say that ALR depends on homebrew and ALR will not work at all if there is a dependency on some C headers or libraries that can only be provided by homebrew?

Thanks,
Ken

[Kenneth Wolcott]

BTW, Simon, I am NOW using your ALR package. I am using the following build

alr --no-color build -- -XTARGET=arm64-apple-darwin22.6.0

I was able to "alr get" and successfully build only eight of the alr packages that I was interested in.

ansiada_1.0.0_dc770a5a
apdf_6.0.0_7c3ce4e9
aunit_23.0.0_84ce7d0b
euler_tools_1.1.1_cf37e6f9
gnatcoll_23.0.0_29478a20
parse_args_0.9.0_635f9e4f
stephes_ada_library_3.7.2_2b6a88f9
xmlada_23.0.0_70494123

Either the get failed or the compile failed. I'll assume that virtually all of those "get" failures are due to lack of a homebrew installation.

I have MANY MacPorts port packages installed which I like very much.

It seems clear that MacPorts and homebrew are not compatible (especially if building packages using either or both of them).

BTW: mathpaqs failed to build due to "digits value out of range, maximum is 15".

Thanks,
Ken

[Simon Wright]

Kenneth Wolcott <kenneth...@gmail.com> writes:

> So I guess it is fair to say that ALR depends on homebrew and ALR
> will not work at all if there is a dependency on some C headers or
> libraries that can only be provided by homebrew?

Sorry, but I've no idea how you got there from what I said!

[Kenneth Wolcott]

On Saturday, August 5, 2023 at 3:12:48 PM UTC-7, Simon Wright wrote:

> Kenneth Wolcott writes:
>
> > So I guess it is fair to say that ALR depends on homebrew and ALR
> > will not work at all if there is a dependency on some C headers or
> > libraries that can only be provided by homebrew?
> Sorry, but I've no idea how you got there from what I said!

Ok, perhaps that was a wee-bit severe, but it sure does look like that is the case.

What else am I to do?

If I don't install homebrew then what is it that I need to do to achieve the objective? I'd like to use ALR, but it looks like it only works for packages that are pure Ada (I'm not 100% sure of that, but it seems to be the case).

So please show me what to do that will result in further progress with ALR and an M1 chip without using homebrew...

Also, I'm still learning how to use gprbuild, so I really don't understand how to proceed with the hand-patching of the sdlada porting to MacPorts issue (different thread).

Thanks,
Ken

[Simon Wright]

Kenneth Wolcott <kenneth...@gmail.com> writes:

[About 70 lines of quoted comment. It'd help if you could leave in only
the relevant parts of the message you're replying to.]

> BTW, Simon, I am NOW using your ALR package. I am using the following
> build

I'm going to have to consider making releases in a way that makes it
easier for me to identify which release you're using.

> alr --no-color build -- -XTARGET=arm64-apple-darwin22.6.0

If this is when building aws, where there is an issue with TARGET, I'd
recommend setting TARGET to what you get by executing "gcc -dumpmachine",
which I believe should be "aarch64-apple-darwin21". The problem is that
aws's alire.toml sets TARGET to a value different from that needed by
the actual code.

> I was able to "alr get" and successfully build only eight of the alr
> packages that I was interested in.

Sorry, what I'm interested in at the meoment is the ones that *didn't*
work because they tried to use an external that isn't set up yet;
something like

$ alr with libreadline
ⓘ Synchronizing workspace...
Nothing to update.

Requested changes:

✓ libreadline * (add)

Changes to dependency solution:

New solution is incomplete.
+🔎 libreadline * (new,external) <============

Do you want to proceed?

[Y] Yes [N] No (default is No)

> It seems clear that MacPorts and homebrew are not compatible
> (especially if building packages using either or both of them).

I think you could probably install both for getting tools (eg graphviz),
but to install libraries for building software against you have to
decide which one to go for. My latest version of alr (not yet released,
issue with Github CI) checks whether "brew" or "port" are on the PATH;
if it finds both, it chooses Homebrew.

> BTW: mathpaqs failed to build due to "digits value out of range,
> maximum is 15".

This is because GNAT on x86_64 implements Long_Long_Float as 128 bits,
'digits 18', whereas GNAT on aarch64 only goes up to 64 bits, 'digits
15'.

[Simon Wright]

Kenneth Wolcott <kenneth...@gmail.com> writes:

> If I don't install homebrew then what is it that I need to do to
> achieve the objective? I'd like to use ALR, but it looks like it only
> works for packages that are pure Ada (I'm not 100% sure of that, but
> it seems to be the case).
>
> So please show me what to do that will result in further progress with
> ALR and an M1 chip without using homebrew...

No guarantees here, but ..

If alr says that a particular external package isn't available, then

* instead of saying N say Y and install the requested package using port

* set these environment variables:
export C_INCLUDE_PATH=/opt/local/include
export CPLUS_INCLUDE_PATH=/opt/local/include
export LIBRARY_PATH=/opt/local/lib

[Kenneth Wolcott]

On Sunday, August 6, 2023 at 4:30:16 AM UTC-7, Simon Wright wrote:
> Kenneth Wolcott writes:

> > So please show me what to do that will result in further progress with
> > ALR and an M1 chip without using homebrew...
> No guarantees here, but ..

Again, sorry I was lazy and did not trim details not relevant to the current response in the thread...

You asked which version of alr I was using:
alr --version
alr 2.0-dev

> If alr says that a particular external package isn't available, then
>
> * instead of saying N say Y and install the requested package using port
>
> * set these environment variables:
> export C_INCLUDE_PATH=/opt/local/include
> export CPLUS_INCLUDE_PATH=/opt/local/include
> export LIBRARY_PATH=/opt/local/lib

Ok, I set those environment variables and now I will try "get"ing a package, responding "Y" if the package is incomplete and if there does seem to be a corresponding MacPorts port which I have not installed, will install it.

Again, referring to your prior response:
gcc -dumpmachine
arm64-apple-darwin22.6.0

Thanks,
Ken

[Kenneth Wolcott]

Hi Simon;

An attempt to "get" aws follows along with all of my openssl installed packages from MacPorts.

alr --no-color get aws

Warning:
Warning: New solution is incomplete.
Warning: +i gnat 13.1.0 (new,installed,gnat_external)
Warning: + gnatcoll 23.0.0 (new)
Warning: + libgpr 23.0.0 (new,indirect)
Warning: + make 3.81.0 (new)
Warning: +~ openssl * (new,external)
Warning: + xmlada 23.0.0 (new)
Warning:
Warning: Could not find a complete solution for aws=23.0.0
Build will fail unless externals are made available, do you want to continue?

[Y] Yes [N] No (default is No) y
Note: Deploying aws=23.0.0...
########################################################################################################################### 100.0%
warn: Generating possibly incomplete environment because of missing dependencies
Note: Deploying make=3.81.0...
Note: Deploying xmlada=23.0.0...
-=O#- # # #
Note: Running post_fetch actions for xmlada=23.0.0...
checking build system type... aarch64-apple-darwin22.6.0
checking host system type... aarch64-apple-darwin22.6.0
checking target system type... aarch64-apple-darwin22.6.0
checking whether gnat can build shared libs... yes
checking for a BSD-compatible install... /opt/local/bin/ginstall -c
checking whether ln -s works... yes
configure: creating ./config.status
config.status: creating xmlada_shared.gpr
config.status: creating Makefile
config.status: creating tests/dom/default.gpr
Note: Deploying libgpr=23.0.0...
-=O#- # # #
Note: Deploying gnatcoll=23.0.0...
-=#=- # # #
Note: Running post_fetch actions for aws=23.0.0...
sed: illegal option -- s
usage: sed script [-Ealnru] [-i extension] [file ...]
sed [-Ealnu] [-i extension] [-e script] ... [-f script_file] ... [file ...]
sed: illegal option -- s
usage: sed script [-Ealnru] [-i extension] [file ...]
sed [-Ealnu] [-i extension] [-e script] ... [-f script_file] ... [file ...]
Bind
[gprbind] xoscons.bexch
[Ada] xoscons.ali
Link
[link] xoscons.adb
Setup OS specific definitions
aws-os_lib-tmplt.c:324:24: error: invalid operand for inline asm constraint 'i'
/*NOGEN*/ asm volatile("\n->CND:%0:" "SIN_FAMILY_OFFSET" ":%1:" "sin_family offset in record" : : "i" (324), "i" ((int) (uintptr_t)((uintptr_t)&sa.sin_family - (uintptr_t)&sa)));;
^
aws-os_lib-tmplt.c:343:24: error: invalid operand for inline asm constraint 'i'
/*NOGEN*/ asm volatile("\n->CND:%0:" "AI_FAMILY_OFFSET" ":%1:" "???" : : "i" (343), "i" ((int) (uintptr_t)((uintptr_t)&ai.ai_family - (uintptr_t)&ai)));;
^
aws-os_lib-tmplt.c:344:24: error: invalid operand for inline asm constraint 'i'
/*NOGEN*/ asm volatile("\n->CND:%0:" "AI_CANONNAME_OFFSET" ":%1:" "???" : : "i" (344), "i" ((int) (uintptr_t)((uintptr_t)&ai.ai_canonname - (uintptr_t)&ai)));;
^
aws-os_lib-tmplt.c:345:24: error: invalid operand for inline asm constraint 'i'
/*NOGEN*/ asm volatile("\n->CND:%0:" "AI_ADDR_OFFSET" ":%1:" "???" : : "i" (345), "i" ((int) (uintptr_t)((uintptr_t)&ai.ai_addr - (uintptr_t)&ai)));;
^
aws-os_lib-tmplt.c:233:17: error: unexpected token at start of statement
asm volatile("\n->TXT:%0:" "-- This is the version for " "arm64-apple-darwin22.6.0" : : "i" (233));
^
<inline asm>:2:1: note: instantiated into assembly here
->TXT:233:-- This is the version for arm64-apple-darwin22.6.0
^
aws-os_lib-tmplt.c:234:17: error: unexpected token at start of statement
asm volatile("\n->TXT:%0:" "" : : "i" (234));
^
<inline asm>:2:1: note: instantiated into assembly here
->TXT:234:
^
aws-os_lib-tmplt.c:240:17: error: unexpected token at start of statement
asm volatile("\n->TXT:%0:" "with Interfaces.C.Strings;" : : "i" (240));
^
<inline asm>:2:1: note: instantiated into assembly here
->TXT:240:with Interfaces.C.Strings;
^
aws-os_lib-tmplt.c:241:17: error: unexpected token at start of statement
asm volatile("\n->TXT:%0:" "with System;" : : "i" (241));
^
<inline asm>:2:1: note: instantiated into assembly here
->TXT:241:with System;
^
aws-os_lib-tmplt.c:243:17: error: unexpected token at start of statement
asm volatile("\n->TXT:%0:" "with GNAT.OS_Lib;" : : "i" (243));
^
<inline asm>:2:1: note: instantiated into assembly here
->TXT:243:with GNAT.OS_Lib;
^
aws-os_lib-tmplt.c:272:17: error: unexpected token at start of statement
asm volatile("\n->C:%0:" "Target_OS" ":" "OS_Type" ":" "Other_OS" ":" "" : : "i" (272));
^
<inline asm>:2:1: note: instantiated into assembly here
->C:272:Target_OS:OS_Type:Other_OS:
^
aws-os_lib-tmplt.c:281:17: error: unexpected token at start of statement
asm volatile("\n->C:%0:" "Target_Name" ":" "String" ":" "arm64-apple-darwin22.6.0" ":" "" : : "i" (281));
^
<inline asm>:2:1: note: instantiated into assembly here
->C:281:Target_Name:String:arm64-apple-darwin22.6.0:
^
aws-os_lib-tmplt.c:310:17: error: unexpected token at start of statement
asm volatile("\n->CND:%0:" "SIZEOF_unsigned_int" ":%1:" "Size of unsigned int" : : "i" (310), "i" ((int) sizeof (unsigned int)));
^
<inline asm>:2:1: note: instantiated into assembly here
->CND:310:SIZEOF_unsigned_int:4:Size of unsigned int
^
aws-os_lib-tmplt.c:313:17: error: unexpected token at start of statement
asm volatile("\n->CND:%0:" "SIZEOF_fd_set" ":%1:" "fd_set" : : "i" (313), "i" ((int) (sizeof (fd_set))));;
^
<inline asm>:2:1: note: instantiated into assembly here
->CND:313:SIZEOF_fd_set:128:fd_set
^
aws-os_lib-tmplt.c:314:17: error: unexpected token at start of statement
asm volatile("\n->CND:%0:" "FD_SETSIZE" ":%1:" "Max fd value" : : "i" (314), "i" ((int) 1024));;
^
<inline asm>:2:1: note: instantiated into assembly here
->CND:314:FD_SETSIZE:1024:Max fd value
^
aws-os_lib-tmplt.c:320:17: error: unexpected token at start of statement
asm volatile("\n->CND:%0:" "SIZEOF_sin_family" ":%1:" "Size of sa.sin_family" : : "i" (320), "i" ((int) sizeof (sa.sin_family) * 8));;
^
<inline asm>:2:1: note: instantiated into assembly here
->CND:320:SIZEOF_sin_family:8:Size of sa.sin_family
^
aws-os_lib-tmplt.c:353:17: error: unexpected token at start of statement
asm volatile("\n->CND:%0:" "SIZEOF_nfds_t" ":%1:" "Size of nfds_t" : : "i" (353), "i" ((int) sizeof (nfds_t) * 8));;
^
<inline asm>:2:1: note: instantiated into assembly here
->CND:353:SIZEOF_nfds_t:32:Size of nfds_t
^
aws-os_lib-tmplt.c:362:17: error: unexpected token at start of statement
asm volatile("\n->CND:%0:" "SIZEOF_pollfd_events" ":%1:" "Size of pollfd.events" : : "i" (362), "i" ((int) sizeof (v_pollfd.events) * 8));;
^
<inline asm>:2:1: note: instantiated into assembly here
->CND:362:SIZEOF_pollfd_events:16:Size of pollfd.events
^
aws-os_lib-tmplt.c:373:17: error: unexpected token at start of statement
asm volatile("\n->CND:%0:" "SIZEOF_fd_type" ":%1:" "Size of socket fd" : : "i" (373), "i" ((int) sizeof (v_pollfd.fd) * 8));;
^
<inline asm>:2:1: note: instantiated into assembly here
->CND:373:SIZEOF_fd_type:32:Size of socket fd
^
aws-os_lib-tmplt.c:381:17: error: unexpected token at start of statement
asm volatile("\n->CND:%0:" "SIZEOF_socklen_t" ":%1:" "Size of socklen_t" : : "i" (381), "i" ((int) sizeof (socklen_t) * 8));;
^
<inline asm>:2:1: note: instantiated into assembly here
->CND:381:SIZEOF_socklen_t:32:Size of socklen_t
^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
raised raised ADA.IO_EXCEPTIONS.NAME_ERROR : aws-os_lib-tmplt.s: No such file or directory

make[1]: *** [../.build/arm64-apple-darwin22.6.0/debug/../setup/src/aws-os_lib.ads] Error 1
make: *** [config_setup] Error 2
ERROR: A post-fetch action failed, re-run with -vv -d for details

-----------------------------------------------
port installed | grep openssl
openssl @3_8
openssl @3_9
openssl @3_9+universal
openssl @3_10+universal
openssl @3_10
openssl @3_11
openssl @3_12 (active)
openssl3 @3.0.7_0+legacy
openssl3 @3.0.7_2+legacy
openssl3 @3.0.8_1+legacy
openssl3 @3.0.8_1+legacy+universal
openssl3 @3.1.0_0+universal
openssl3 @3.1.0_1
openssl3 @3.1.0_1+universal
openssl3 @3.1.0_2+universal
openssl3 @3.1.0_3+universal
openssl3 @3.1.0_3
openssl3 @3.1.1_0
openssl3 @3.1.2_0 (active)
openssl10 @1.0.2u_4 (active)
openssl11 @1.1.1s_0
openssl11 @1.1.1t_0
openssl11 @1.1.1t_1
openssl11 @1.1.1u_1
openssl11 @1.1.1v_1 (active)
py310-openssl @21.0.0_0
py310-openssl @22.1.0_0
py310-openssl @23.0.0_0
py310-openssl @23.2.0_0 (active)
py311-openssl @23.0.0_0
py311-openssl @23.2.0_0 (active)
qt5-qtbase @5.15.6_1+openssl
qt5-qtbase @5.15.8_0+openssl
qt5-qtbase @5.15.8_1+openssl
qt5-qtbase @5.15.9_0+openssl
qt5-qtbase @5.15.10_0+openssl (active)
qt6-qtbase @6.4.3_1+openssl (active)
-----------------------------------------------

That reminds me, I need to uninstall those "universal" packages...

Thanks,
Ken

[Simon Wright]

Kenneth Wolcott <kenneth...@gmail.com> writes:

> make[1]: *** [../.build/arm64-apple-darwin22.6.0/debug/../setup/src/aws-os_lib.ads] Error 1
> make: *** [config_setup] Error 2

The reason, I think, is that you have /usr/bin in your PATH before
/opt/gcc-13.1.0-aarch64.

From the release notes at
https://github.com/simonjwright/distributing-gcc/releases/tag/gcc-13.1.0-aarch64-2,

Setting PATH

PATH needs to be set to include /opt/gcc-13.1.0-aarch64/bin at the front:

bash

Insert

export PATH=/opt/gcc-13.1.0-aarch64/bin:$PATH
in your ~/.bash_profile_common.

zsh

Likewise, but in ~/.zshrc.

/usr/bin/gcc is the exact same compiler as /usr/bin/clang (a hard link,
by the look of it).

$ /usr/bin/gcc -v
Apple clang version 14.0.3 (clang-1403.0.22.14.1)
Target: arm64-apple-darwin22.5.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

$ /opt/gcc-13.1.0-aarch64/bin/gcc -v
Using built-in specs.
COLLECT_GCC=/opt/gcc-13.1.0-aarch64/bin/gcc
COLLECT_LTO_WRAPPER=/opt/gcc-13.1.0-aarch64/libexec/gcc/aarch64-apple-darwin21/13.1.0/lto-wrapper
Target: aarch64-apple-darwin21
Configured with: [...]
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 13.1.0 (GCC)

I think you need to fix the PATH problem, then build with

$ alr build -- -XTARGET=aarch64-apple-darwin21

[Simon Wright]

Simon Wright <si...@pushface.org> writes:

> The reason, I think, is that you have /usr/bin in your PATH before
> /opt/gcc-13.1.0-aarch64.

/opt/gcc-13.1.0-aarch64/bin
^^^^

[Kenneth Wolcott]

Hi Simon;

Vast improvement after changing the PATH env var as you instructed!

I have an edited get+build log (hope it is not too long). Looks like there are still some sed issues and other things I'm not sure about.

I guess it is too long; well it is definitely too annoying to copy&paste a screenfull at a time...

What I saw:

ONE:
sed issues (three instances):

sed: illegal option -- s
usage: sed script [-Ealnru] [-i extension] [file ...]
sed [-Ealnu] [-i extension] [-e script] ... [-f script_file] ... [file ...]

TWO:
gnatcoll-refcount.ads:90:04: warning: in instantiation at gnatcoll-storage_pools-headers.adb:57 [enabled by default]
gnatcoll-refcount.ads:90:04: warning: possible aliasing problem for type "Header_Access" [enabled by default]
gnatcoll-refcount.ads:90:04: warning: use -fno-strict-aliasing switch for references [enabled by default]
gnatcoll-refcount.ads:90:04: warning: or use "pragma No_Strict_Aliasing (Header_Access);" [enabled by default]

Lots of "Exploring..." would there be something useful here as far as something not pertinent being examined or something that was NOT explored that should have been?

Lots of "Building"...If it doesn't complain then there's nothing missing and nothing wrong with the C and Ada sources?

The process generates at least three times a warning something like the following:

"Generating possibly incomplete environment because of missing dependencies"

What do I do now to ascertain the precise state of the alr aws package?

Thanks,
Ken

[Simon Wright]

Kenneth Wolcott <kenneth...@gmail.com> writes:

> ONE:
> sed issues (three instances):
>
> sed: illegal option -- s
> usage: sed script [-Ealnru] [-i extension] [file ...]
> sed [-Ealnu] [-i extension] [-e script] ... [-f script_file] ... [file ...]

This dosn't seem to do any harm.
See this PR: https://github.com/AdaCore/aws/pull/368

> TWO:
> gnatcoll-refcount.ads:90:04: warning: in instantiation at gnatcoll-storage_pools-headers.adb:57 [enabled by default]
> gnatcoll-refcount.ads:90:04: warning: possible aliasing problem for type "Header_Access" [enabled by default]
> gnatcoll-refcount.ads:90:04: warning: use -fno-strict-aliasing switch for references [enabled by default]
> gnatcoll-refcount.ads:90:04: warning: or use "pragma No_Strict_Aliasing (Header_Access);" [enabled by default]

This set of warnings has been there for quite a while. I've never had a
problem with it.

> Lots of "Exploring..." would there be something useful here as far as
> something not pertinent being examined or something that was NOT
> explored that should have been?

I don't recall those messages ... I probably wasn't looking, so if the
build didn't stop I wouldn't have noticed

> Lots of "Building"...If it doesn't complain then there's nothing
> missing and nothing wrong with the C and Ada sources?

I'd say Yes

> The process generates at least three times a warning something like
> the following: "Generating possibly incomplete environment because of
> missing dependencies"

That's because the alr you're using doesn't understand MacPorts. Watch
this space.

> What do I do now to ascertain the precise state of the alr aws package?

You could try

cd demos/hello_world
alr exec -- make TARGET=aarch64-apple-darwin21
./hello_world

and within 60 seconds open your browser on localhost:8080.

(the 'make' part rebuilds the whole of aws!!)

[Kenneth Wolcott]

Hi Simon;

> > sed: illegal option -- s
> > usage: sed script [-Ealnru] [-i extension] [file ...]
> > sed [-Ealnu] [-i extension] [-e script] ... [-f script_file] ... [file ...]
> This dosn't seem to do any harm.
> See this PR: https://github.com/AdaCore/aws/pull/368

Cool.

> > gnatcoll-refcount.ads:90:04: warnings

> This set of warnings has been there for quite a while. I've never had a
> problem with it.

Also cool.

> > Lots of "Exploring..."

> I don't recall those messages ... I probably wasn't looking, so if the
> build didn't stop I wouldn't have noticed

Very good, see no problem then there is no problem :-)

> > Lots of "Building"...

If it doesn't complain then there's nothing
> > missing and nothing wrong with the C and Ada sources?
> I'd say Yes

Very good, see no problem then there is no problem :-)

> > The process generates at least three times a warning something like
> > the following: "Generating possibly incomplete environment because of
> > missing dependencies"
> That's because the alr you're using doesn't understand MacPorts. Watch
> this space.

Looking forward to this! [GRIN*]

> > What do I do now to ascertain the precise state of the alr aws package?
> You could try
>
> cd demos/hello_world
> alr exec -- make TARGET=aarch64-apple-darwin21
> ./hello_world
>
> and within 60 seconds open your browser on localhost:8080.
>
> (the 'make' part rebuilds the whole of aws!!)

The test you suggested worked!

Thank you!

Ken