Re: Log for attempted build of k3d_0.8.0.6-5 on m68k (dist=unstable)

[Thorsten Glaser <tg@mirbsd.de>]

>fail
>
>virtual memory exhausted: Cannot allocate memory

I should probably give-back it, but packages failing when the
buildd has “only” 768 MiB RAM are a problem. (Yes, I know, I
can set ARAnyM to give it more nowadays, but the host doesn’t
have more either.)

We probably should tackle this somewhere. Perhaps at the
dpkg-buildflags level? Some people fix it by using -gstabs
instead of -g on several architectures. (Maybe this could
be discussed on the d-ports level?)

I don’t know enough about this to comment further.

bye,
//mirabilos, who saw several instances of that recently
-- 
(gnutls can also be used, but if you are compiling lynx for your own use,
there is no reason to consider using that package)
	-- Thomas E. Dickey on the Lynx mailing list, about OpenSSL