Re: 2025Q1 lang/rust build failure on illumos (ENOMEM)

[Hans Rosenfeld <hans%netbsd.org@localhost>]

On Wed, Apr 16, 2025 at 10:34:42PM +0100, Jonathan Perkin wrote:
> * On 2025-04-16 at 15:32 BST, Hans Rosenfeld wrote:
> 
> > I ran 'ulimit -s 131072' in the shell I'm using for building, and
> > devel/cargo-c built successfully.
> > 
> > I presume that means it needs UNLIMIT_RESOURCES? Is that perhaps the
> > case for all rust-based packages?
> 
> What's your default stacksize?  On SmartOS it's 10MB and I didn't have any
> problems building cargo-c.  At what threshold does it start working for you?

It did work with 131072, while it did not when it was unlimited.

I didn't check any other values. I figure it's the same problem that I
saw building lang/rust, and I would conclude that rustc (?) just doesn't
like running with unlimited stack size in general, for the reasons given
previously (https://github.com/NetBSD/pkgsrc/commit/a7aeedc3).

I do however wonder whether it is stack_getbounds(3c) that is wrong, or
whether rust is wrong not handling this case properly. It seems counter-
intuitive to have UNLIMIT_RESOURCES actually limit stack size to a
smaller value if it's already "unlimited".


Hans




-- 
%SYSTEM-F-ANARCHISM, The operating system has been overthrown