Re: When to set / keep MAKE_JOBS_UNSAFE?

2020-10-10 Thread Moritz Schmitt
Kurt Jaeger (Oct 10, 2020):
> > In its Makefile MAKE_JOBS_UNSAFE is set and I'm trying to figure out if
> > it's acutally needed or not.
> 
> If you build it on a box with more CPUs cores, will it fail or not ?
> 
> What number of CPUs cores did you try ?

I built it successfully on

FreeBSD freebsd.current 13.0-CURRENT FreeBSD 13.0-CURRENT #0 
3c514403bef-c253353(main): Thu Sep 24 06:45:17 UTC 2020 
r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64
hw.machine: amd64
hw.ncpu: 12

> I've just tried it without MAKE_JOBS_UNSAFE on a 32 and it built
> fine. So I guess you can remove it.

This would also be my guess.

Best,
Moritz
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: When to set / keep MAKE_JOBS_UNSAFE?

2020-10-10 Thread Kurt Jaeger
Hi!

> In its Makefile MAKE_JOBS_UNSAFE is set and I'm trying to figure out if
> it's acutally needed or not.

If you build it on a box with more CPUs cores, will it fail or not ?

What number of CPUs cores did you try ?

I've just tried it without MAKE_JOBS_UNSAFE on a 32 and it built
fine. So I guess you can remove it.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


When to set / keep MAKE_JOBS_UNSAFE?

2020-10-10 Thread Moritz Schmitt
Hi,

I recently took over maintainership of devel/gindent, and I'm in the
process of cleaning it up.

In its Makefile MAKE_JOBS_UNSAFE is set and I'm trying to figure out if
it's acutally needed or not. Subversion's log has the following entry:

r244490 | pav | 2009-11-20 00:41:55 +0100 (Fri, 20 Nov 2009) | 4 lines

- Mark MAKE_JOBS_UNSAFE

Reported by:pointyhat

This commit message is undoubtedly correct, but alas, not very
convincing. And unfortunately, I couldn't find the report by pointyhat.

If I remove MAKE_JOBS_UNSAFE, the port seems to build without any
problems at all. I also couldn't find any restrictions specified in the
source of GNU indent. However, from this we cannot deduce that it's safe
to build the port in parallel.

How do porters usually deal with such a situation?

Best,
Moritz
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"