From owner-cvs-all Wed Oct 14 18:24:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05298 for cvs-all-outgoing; Wed, 14 Oct 1998 18:24:21 -0700 (PDT) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05176 for ; Wed, 14 Oct 1998 18:24:11 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.0/8.9.0) with SMTP id UAA18589 for ; Wed, 14 Oct 1998 20:23:54 -0500 (CDT) Date: Wed, 14 Oct 1998 20:23:54 -0500 (CDT) From: Steve Price To: committers@FreeBSD.ORG Subject: annoying make(1) behavior Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk Hi All, No offense to the John B. who committed revision 1.7 of src/usr.bin/make/config.h, but this has made -current's make take on a very annoying behavior. In an ELF world despite the fact that a library doesn't even exist make(1) says it is up-to-date and the build fails. A good example of what I'm talking about is the yale-tftpd port. I have fixed several ports by just using 'USE_GMAKE=yes', just to get them fixed before we go to release, but "this ain't right" especially for this port since it uses a bmake'd Makefile. Bruce will probably have a quick answer for why this is the correct behavior, but it seems severely broken to me. I have taken a look at it and developed a couple of hacks, none of which I think are appropriate for inclusion in the pending release, so if anyone has some time and knows their way around make(1) it would be great if this could be fixed before the release. And yes, just reverting revision 1.7 does work, but this isn't the right solution either or John wouldn't have made the commit to begin with. Thanks, Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message