Re: 2.7.1 on Mac x86

"Chun Tian (binghe)" <[email protected]> Sun, 4 May 2025 17:20:00 +1000
Newsgroups gmane.lisp.gcl.devel
Organization The Australian National University
Message-ID <[email protected]>
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--n8IgxnZe8EIQIBByJ0J0rLtcGYLNyeRJO
Content-Type: multipart/mixed; boundary="Mdx7Jnb6qr6vl6Ux01eiGvRsO5qRDJyGW";
 protected-headers="v1"
From: "Chun Tian (binghe)" <[email protected]>
To: Camm Maguire <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Subject: Re: 2.7.1 on Mac x86
References: <[email protected]>
 <[email protected]>
 <[email protected]>
 <[email protected]>
 <[email protected]>
 <[email protected]>
 <[email protected]>
 <[email protected]>
In-Reply-To: <[email protected]>

--Mdx7Jnb6qr6vl6Ux01eiGvRsO5qRDJyGW
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Greetings,

On 01/05/25 12:54, Chun Tian (binghe) wrote:
> Greetings,
>=20
> I found another (minor) issue when building GCL in macOS. The system co=
mmand
> "mktemp" of macOS doesn't support "-p" option (in "xbin/mktmp"). How to=
 rewrite
> this script by using, e.g., "-t" instead:
>=20
>       -p DIR, --tmpdir[=3DDIR]
>               interpret TEMPLATE relative to DIR; if DIR is not specifi=
ed,  use
>               $TMPDIR  if  set, else /tmp.  With this option, TEMPLATE =
must not
>               be an  absolute  name;  unlike  with  -t,  TEMPLATE  may =
 contain
>               slashes, but mktemp creates only the final component
>=20
>        -t     interpret TEMPLATE as a single file name component, relat=
ive to a
>               directory:  $TMPDIR, if set; else the directory specified=
 via -p;
>               else /tmp [deprecated]
>=20

I just figured out that I can install MacPorts' "coreutils" package, whic=
h
provides the GNU version of "mktemp".

Furthermore, by using MacPorts' "legacy-support" package, the missing
"readlinkat" system call will be provided. (I will need to learn how to u=
se this
package.)

Therefore no more blocking issues on supporting GCL 2.7 in earlier macOS
versions. You don't need to do anything here.

In general, I think it's totally reasonable for GCL to depend on some oth=
er GNU
tooling packages (on macOS), including GCC (if necessary).

--Chun


--Mdx7Jnb6qr6vl6Ux01eiGvRsO5qRDJyGW--

--n8IgxnZe8EIQIBByJ0J0rLtcGYLNyeRJO
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEES+aY+4laoC0TwmVKFUkg2jrYR8gFAmgXFSAACgkQFUkg2jrY
R8gKYQ/9GzKmV5OV/ji7PO1TzCqHgKiKe9f/dJJqHK+btbQMRrx/mVZCsDWZ/0Fi
6Zigy3InatwnHeJk9a0ocwlURhEmscP7SPimMaB+UvtgZl9S8tVJGd9cI+RsIRcl
srp0AskV0xSm9eCHprwHZJAJEdWdGbbETgL+flm7ZjMLwJIU7NYwsS7bwF3iAje1
PUZGD1+BpcQpMxSTFuX9az7iS2mCs8o9e2vPQqOINrSEkszb2t65f0UNR78SihiG
pJDpNaK57MKcxHFeMtdsvBgMYIejkewu+Q/SZC7JgfANG4t6Q6CH/HiWhJgiKTQx
LqykKp18cyeaQYxb6+gOLOSEH6WqIAZ4FEqanLvDdNrc+Y65ciRL2sJK06VoSPI7
y6eh8nXKAAk3TDKCFAgcbzP0F3c05EirDcQZJFR530FzGce89mZX8rtfKkYsNt1+
Ai4hVC8zVCtKpVxa7zDH7c2XB3S4GeLDsQdGIRZAkYko5eFDiM59BOa9uIO9tx2r
7ROXg1EaBpuMxfnuYAoQi9EQoQs/W2UpIbRuX2LMDhmy5xv//EXLncqrLriB7ziZ
QJAlDQNaJwHhkB+YTEsVlQO+nw8i+KfwZmda9V2il4h2qymqYTtnqejaZSvm4cyN
g/AgOqcLvwHP4roCpzATBPA0ZBiL3M4vjXGDYOUyGWSdEEl704k=
=2biJ
-----END PGP SIGNATURE-----

--n8IgxnZe8EIQIBByJ0J0rLtcGYLNyeRJO--