Howard Chu
> > CTO, Symas Corp. http://www.symas.com
> > Director, Highland Sun http://highlandsun.com/hyc/
> > Chief Architect, OpenLDAP http://www.openldap.org/project/
> >
>
>
> --
> -- Howard Chu
> CTO, Symas C
Hi,
Have you considered using port 0 instead to tap into the ephemeral port
range and communicate that port somehow?
>From what I understand, you want to use the job id as an offset to a base
port to choose a port from a range, right? That sounds non-portable to me,
spelling all sorts of ports co
that
condition.
Rationale for b):
INCLUDE_DIRS+=${HOME}/.local/include has no effect and does not print any
error message, which is not friendly towards users of make.
Something should either work, or when it doesn't, it should print an error
message.
Best regards,
--
Christian Hujer
CEO/CTO
Nelkind
Follow-up Comment #5, bug #29074 (project make):
I agree with Hack Lee.
There was a bug before 3.81.
You wouldn't want make to fall over on an
-include $(sources:%.c=%.d)
in the Makefile because of a source error when you're actually running
make clean
The behavior of GNUmake 3.81 is correct.
