[Buildroot] [PATCH 1/2] ngrep: bump to version 1.47

Peter Korsgaard peter at korsgaard.com
Tue Nov 6 11:18:56 UTC 2018


>>>>> "Arnout" == Arnout Vandecappelle <arnout at mind.be> writes:

Hi,

 >> > then package{A,B,C} would be built with the system-provided make, and
 >> > then package{D,E,F} would be built with host-make ? Is this really a
 >> > desirable situation ?
 >> 
 >> Well, it sounds better than the breakage we have today.

 >  At first sight, I don't see why it should be a problem to use a different make
 > for different packages. A bit weird, but it really shouldn't affect
 > reproducibility or anything.

Well, it could in case a package behaved differently depending on the
make version (E.G. newer make versions have broken older Makefiles), so
enabling a package X that pulls in host-make suddenly changes something
for the build of package Y - Or the other way around, E.G. package Y
depends on package X which pulls in host-make so we never notice that
package Y needs a newer make version, and then a version bump of Y makes
X optional, ..

But I agree that it is quite unlikely to cause any real issues.


 >> In general, mixing make versions in recursive invocations seems a bit
 >> icky. I guess we could end up with issues if/when we do toplevel
 >> parallel builds as well if the job control tracking differs between
 >> versions.

 >  Ooh, yes, top-level parallel build might break dramatically in such a situation...

 >  Well, let's fix that problem when we get there, right?

Agreed!

-- 
Bye, Peter Korsgaard


More information about the buildroot mailing list