Re: [chrony-dev] GNU make requirement |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] GNU make requirement
- From: Richard Curnow <rc@xxxxxxxxxx>
- Date: Thu, 10 Dec 2009 09:46:57 +0000
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=dadd2wb/x5irVxqztTyxqIxlnWdD92gqaulntqzSTdE=; b=QNrwPbpGihhfPK0yP4b1AQ1cEGYRX53IFItZmi/DqDU0RsEqVlKzCZHyHKwiZ/5M4o eXrWh4opP537FJvxbHOuuk0kJlI4lJR4XCS/VCXeXZ0jTHdz5WNrCQPBqVyGolPvHgxb J5xgAmUXC2UyhdTeF+PZVNij8tL3Z16aZP+DI=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=Vu92ChGMPx69XTe5qUwsYf59Z3PeKjIbebnJ9ZGIVne8MtbZR6O9LTWMspFtPwgppI tG2UH/xt0YJNzevGn4nLp1miR0/WL6LSnKnVrFS6S25BITN29GYfBzkLtUGcN+prEsrV Kbc7yVb6zhfN8Qq596IQuL13gZzE/tSdzS2ys=
2009/12/7 Miroslav Lichvar <mlichvar@xxxxxxxxxx>:
> I couldn't find it in the docs, is GNU make required to compile chrony?
It was never intentionally like that, but I doubt I ever personally
built it with anything else. However, configure still claims that we
support BSD, FreeBSD, NetBSD - I wonder how recently they have been
tried and whether make has broken on them.
>
> It seems that (at least) BSD make doesn't support pattern rules which
> are used in the Makefile. They can be replaced with more portable
> suffix rules.
>
> Or, if we support only GNU make, I'd like to add an -include .depend,
> so I don't need to spend time chasing weird bugs after changing one of the
> headers and not recompiling all depending objects :).
Does anything like
..%.d : %.c
gcc -MM $< -o $@
include $(addprefix .,$(OBJ:.o=.d))
work for other makes?
---
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.