--RnlQjJ0d97Da+TV1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, May 28, 2002 at 03:01:15PM +0200, Klaus Heinz wrote:
> Bernd Ernesti wrote:
>=20
> > Please ask Ignatios about this part.
> >=20
> > I can't find a mail now which describes why we have to use the gspa 'co=
mpiler'
> > and can't add a generated c file.
>=20
> I would also be interested in why the build broke in the first place.
>=20
> When I looked at this on sunday evening I could find no reason for the br=
oken
> build mechanism on Amiga. My only guess, from the logfile on the releng
> machine:=20
>=20
>   gspa: not found
>   *** Error code 127
>=20
> gspa somehow disappeared from /usr/sbin/ on the build machine.

errr no... Michael Hitch reported the same, and as far as he analyzed, the
PATH for building was changed to exclude it.

Which is very reasonable for a building machine.

In this special case, gspa would be machine independent, but not OS
independent; we can't rely on it being available, so it would have to be
a host tool. It's certainly more reasonable to carry around the created
microcode.

Regards,
	-is
--=20
seal your e-mail: http://www.gnupg.org/

--RnlQjJ0d97Da+TV1
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (NetBSD)
Comment: For info see http://www.gnupg.org

iD8DBQE888YiPCRcZ/VMtk4RAtMyAJ9Xemf7iNiclD8y+S+xACJbljGFKwCfc/xi
AMQnGO8TolAlKeU9yiNdLMY=
=6CcJ
-----END PGP SIGNATURE-----

--RnlQjJ0d97Da+TV1--