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

On Fri, May 12, 2006 at 10:41:39AM -0300, Paulo Aukar wrote:
> On Fri, 12 May 2006 14:20:58 +0200
> Quentin Garnier <cube@cubidou.net> wrote:
>=20
> > You mean a 2.0.3 kernel?  Because the thread is about a change in
> > -current...
>=20
> Yes. 2.0.3 kernel. In fact the whole system compiled from source. I think=
=20
> you are right. After pkg_adding gkrellm compiled some time ago=20
> under 3.99.9 everything is working fine. But shouldn't -current kernel=20
> have all the necessary resources to run NetBSD 2.* binaries?

I have a hard time following you.  What is at stake here is very simple:
-current was changed and that breaks gkrellm *compilation*.  The change
took place as new version 3.99.18.

What I want to know is whether a gkrellm binary compiled for 3.99.17
works on 3.99.18.  Anything else is outside the scope of that thread,
and if there are bugs, they need their own thread/PR.

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.

--GLp9dJVi+aaipsRk
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (NetBSD)

iQEVAwUBRGSULdgoQloHrPnoAQJMnwgAv7tuoAe3XPcsfyk2H5w1pLiyOQJnElo4
nB/bW4k3ZyO57QdlDq3LvvkuUNaREejufy+Y1m9tC2ZnVPmxkpyJcoxQUFaSjr5Z
f8MhvEVOauyS5UNc7qmD2GkmeDPKZ8VZD6jvHDepvJRv+0NAcXG89ktV8VdtVk+B
w6V9Zcl/ftreirG8Hc3jelSZ+53bQEIqQ8JD+g00mgtuJ7fyBns0RiIa1EybNVl8
WOA3CHvXE5sTcWtoj5C4WouPiyXMuZAz3Wl3CIQY7aiq66r9t1xGGLziXEadf3j3
sss/sgyWDgtZUWYTvWs0i+7TBxSxKm0byHeHblsabKN08L18R4We6g==
=60hJ
-----END PGP SIGNATURE-----

--GLp9dJVi+aaipsRk--