Date: Thu, 18 Apr 2002 13:23:18 +0200 (CEST) From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> To: FreeBSD-gnats-submit@FreeBSD.org Subject: bin/37224: make: $< only set for implicit rules Message-ID: <200204181123.g3IBNIV28960@naos.dbai.tuwien.ac.at>
next in thread | raw e-mail | index | archive | help
>Number: 37224 >Category: bin >Synopsis: make: $< only set for implicit rules >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Apr 18 04:30:05 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Gerald Pfeifer >Release: FreeBSD 4.5-RELEASE i386 >Organization: >Environment: System: FreeBSD naos.dbai.tuwien.ac.at 4.5-RELEASE FreeBSD 4.5-RELEASE #0: Fri Feb 15 09:48:40 CET 2002 root@naos.dbai.tuwien.ac.at:/usr/src/sys/compile/DBAI i386 The same happens on -CURRENT as well. >Description: The following Makefile demonstrates a make(1) bug handling $< in explicit rules (assume that bar.c resides in the current directory): .c.o: echo $< foo: bar.c echo $< Specifically, 'make bar.o' prints bar.c, as expected, while 'make foo' prints the empty string (as $< has not been set). GNU make prints bar.c in both cases, and also my reading of IEEE Std 1003.1-2001 indicates that make(1) is incorrect here. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200204181123.g3IBNIV28960>