Re: gmake-4.4.1 has a performance regression: at least the science/nwchem project now builds much slower

On Sat, 30 Mar 2024 06:13:17 +0900
Tatsuki Makino <tatsuki_makino@hotmail.com> wrote:

> Hello.
> 
> I don't think this is relevant at all, but gmake does seem to have a mechanism inside that stalls due to load average.
> It seems to be possible to set it with options -l and --load-average, but I don't think that matters, since if it is left at the default negative number, it doesn't seem to be working.
> 
> Regards.

Possibly I'm overlooking something in Porter's Handbook, but is there a
proper and generic way that builds/installs some build dependencies
under ${WRKDIR} and use it, without installing into the bare-metal
environment?

For examole, build gmake 4.3 under foo/bar/work/opttools/gmake43/ and
use built gmake in it for build.

If it is possible, you can temporarily build/install gmake 4.3 in
${WRKDIR} and use built gmake instead of bare-metal system's gmake.


Off topic:

This could be used for python2.7 deletion. Anything requires it only
for build can still depends on it with the cost of building python2.7
for every build/rebuilds.

Of course, depending upon maintained tauthon, which is a fork of
python2.7 isntead of genuine python2.7 would be an option, too.

-- 
Tomoaki AOKI    <junchoon@dec.sakura.ne.jp>