jbk: it seems to be supported (and working) on ESXi, but not working (while still being advertised) on desktop products (i checked vmware workstation)

I've been finding to do anything useful in bldenv lately I always have to include -S when trying to do any dev work. Is it just me?

(Remembering it for dmake -m serial is the most painful)

rmustacc I'm use make for serial and dmake for parallel build:D

I use*

tsoome_: I don't think it really changes the problem of needing to just use -S.

When there's only one or two source files, it's easy to ignore, but trying to do anything in unix/genunix say.

I assume this is due to -k in MAKEFLAGS in the env actually making its way into the bldenv environment.

Yes.

I am trying to retrain, but just trying to see if others are in a same boat or if it's a just me thing.

Maybe we should fix nightly to always pass -k on the command line and take it out of the env file.

Dunno, I want be mindful if it's just me having an issue and if everyone else likes the new behavior.

tsoome_: I've seen cases where it gratuitously rebuilds when you switch between make and dmake, likely due to some .KEEP_STATE subtlety.

yes, keep state is doing evil things:)

Nice things are often evil to someone else.

it's a saftey vs speed tradeoff

ofc it is mostly good, but there are some bugs apparently, where you run make and then next make will still [re]build things.

If it's just me, I'll keep struggling for a while and hopefully I'll change. Though I still type the old manual section numbers, haha.

It's not just you but it's not something that really bugs me. It goes against decades of experience in which -k is never the default .. if it's still an irritant in a month or two, speak up..

in other news, my work-in-progress locale-in-ulwp_t patches (a) booted cleanly in a VM, and (b) appear to speed up towupper/towlower by up to 8x in an admittedly rigged test...

but they need a bunch more testing of course.

rmustacc - I just ended up taking MAKEFLAGS out of my .env files completely

I generally want things to fail fast, even nightly

(or at least, I can accept that trade off)

I have multiple ways of operating. one is often to use -k first to build everything that can build, then go back and do a serial build w/o -k to fix things one at a time. Another is to just use emacs's compile mode and walk through every error until I've changed enough things that doing anther build seems worthwhile (and in the latter style, shadow compilers are annoying because you see every error at least twice)