tech-toolchain archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: final steps for reproduceable builds.
christos%zoulas.com@localhost (Christos Zoulas) writes:
> | Fine, but we need something for each component too, and we need a name
> | for that specifically here -- something that reflects that what we're
> | dealing with is very specifically the "D" flag to ar on bsd.lib.mk
> | built libraries.
> |
> | Any ideas on a name for *that*? I've been unable to think of a good one.
>
> MKARZERO? But I don't know about making too many tunables available to the
> user, they make things hard to test and maintain.
In this case I want to make it possible for non-NetBSD code to use
bsd.lib.mk and turn on and off the D flag, which means it needs to be
independently tunable.
If you prefer MKARZERO, I'll use that.
Perry
--
Perry E. Metzger perry%piermont.com@localhost
Home |
Main Index |
Thread Index |
Old Index