Milter-greylist

jimklimov@... wrote:
 > When a new version arrives, at least one with interesting features,
 > time comes to rebuild the whole milter-related stack or at least
 > some parts of it (like this project alone). Often some minor things
 > have to be tweaked which causes several rebuilds across a number
 > of systems of different age (including x86 and sparc solaris 8 and
 > above) using same source shared over nfs, and placing resulting
 > objects, binaries and libraries into per-arch folders there. That's
 > the way things were done here and there's little incentive to change
 > and break stuff.

Does that mean you have a system of Makefiles that builds
a large amount of software packages, one of them being
milter-greylist?

In that case the easiest solution would probably be to call
milter-greylist's Makefile with the line 'MAKEFLAGS="" make'
so the -j flag isn't propagated to the child make.
Basically that's also what FreeBSD's ports collection does
when building ports that are marked as "MAKE_JOBS_UNSAFE"
(such as milter-greylist).

Best regards
   Oliver


-- 
Oliver Fromme,  secnetix GmbH & Co. KG,  Marktplatz 29, 85567 Grafing
Handelsregister:  Amtsgericht Muenchen, HRA 74606, Gesch\ufffdftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsreg.: Amtsgericht M\ufffdnchen,
HRB 125758, Gesch\ufffdftsf\ufffdhrer:  Maik Bachmann,  Olaf Erb,  Ralf Gebhart

FreeBSD-Dienstleistungen/-Produkte + mehr: http://www.secnetix.de/bsd

"Documentation is like sex; when it's good, it's very, very good,
and when it's bad, it's better than nothing."
        -- Dick Brandon