Re: documentation build issue with e.g. -j3

Andreas Metzler <[email protected]>
Newsgroups gmane.comp.web.lynx.devel
Message-ID <[email protected]>
On 2021-02-28 Thomas Dickey <[email protected]> wrote:
> On Sun, Feb 28, 2021 at 01:59:02PM -0500, Thomas Dickey wrote:
[...] 
> > Actually, I've not found a way to reproduce problems with parallel make
> > using GNU make.

Hello Thomas,

Comparing 

(sid)ametzler@argenau:/tmp/LYNX/lynx-snapshots$ { autoreconf-dickey --verbose -f -i && ./configure --enable-htmlized-cfg CFLAGS=-DNO_BUILDSTAMP && make -j3 && mkdir INST && make -j3 install-full DESTDIR=/tmp/LYNX/lynx-snapshots/INST ; } 2>&1 | tee buildlog

with

(sid)ametzler@argenau:/tmp/LYNX/lynx-snapshots$ { autoreconf-dickey --verbose -f -i && ./configure --enable-htmlized-cfg CFLAGS=-DNO_BUILDSTAMP && make -j1 && m
kdir INST && make -j1 install-full DESTDIR=/tmp/LYNX/lynx-snapshots/INST ; } 2>&
1 | tee buildlog

both on a clean git checkout will show the "Support for this setting was
disabled at compile-time." issue in body.html. The error happens on
install-full.

> > However, it's fairly simple to reproduce similar problems
> > using BSD make (I could digress).  So I had that on a to-do list, anyway.
> > At the moment I'm testing a more involved change which fixes this issue
> > as reproduced in pmake (along with other fixes), and once done with testing
> > that set of changes, will make an update in my git snapshots.

> https://github.com/ThomasDickey/lynx-snapshots/commit/f100e91840bc2ef2cecf3d0975b734e53637fa55

This fixes my reproducer too. (Errors show up on
372d64a9e3f0d1fa9b53c5bc494f61263b19f0ff and are gone
f100e91840bc2ef2cecf3d0975b734e53637fa55.

Thank you.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

_______________________________________________
Lynx-dev mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lynx-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.