From owner-freebsd-questions@FreeBSD.ORG Mon Mar 24 18:36:04 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4B6AD26E for ; Mon, 24 Mar 2014 18:36:04 +0000 (UTC) Received: from ptolemy.wi.mit.edu (ptolemy.wi.mit.edu [18.4.1.120]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C23F8A5A for ; Mon, 24 Mar 2014 18:36:03 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.97,722,1389762000"; d="scan'208";a="6928890" Received: from unknown (HELO mars.wi.mit.edu) ([10.9.4.20]) by ptolemy.wi.mit.edu with ESMTP; 24 Mar 2014 14:35:55 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by mars.wi.mit.edu (Postfix) with ESMTP id BF66131E120 for ; Mon, 24 Mar 2014 14:35:55 -0400 (EDT) X-Virus-Scanned: amavisd-new at mars.wi.mit.edu Received: from mars.wi.mit.edu ([127.0.0.1]) by localhost (mars.wi.mit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c2EHtJOqXZ-v for ; Mon, 24 Mar 2014 14:35:55 -0400 (EDT) Received: from [10.9.40.29] (disco.wi.mit.edu [10.9.40.29]) by mars.wi.mit.edu (Postfix) with ESMTPSA id 5173131E115 for ; Mon, 24 Mar 2014 14:35:55 -0400 (EDT) Message-ID: <53307B1E.4080704@wi.mit.edu> Date: Mon, 24 Mar 2014 14:36:14 -0400 From: Assaf Gordon User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: 'make' behavior in FreeBSD-10 ? References: <532F1A58.30702@wi.mit.edu> <44siq7wjwi.fsf@be-well.ilk.org> In-Reply-To: <44siq7wjwi.fsf@be-well.ilk.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Mar 2014 18:36:04 -0000 Hello, On 03/24/2014 02:06 PM, Lowell Gilbert wrote: > >> I'm trying to track down an issue in compiling 'autotools' packages that appears in FreeBSD-10 . >> (I'm not a frequent FreeBSD user, so it's possible I'm missing something - any help would be appreciated). > > Is automake specifically what you're trying to build, or are the other > questions relevant as well? > > This is relevant because it sounds as though you are not trying to use > the FreeBSD ports (or pkg; they're really the same thing in terms of > what gets installed) system. That's the usual way such a thing would be > done, and the exceptions are almost entirely people who would be able to > answer such questions for themselves. I'm trying to build a package that uses autotools+automake, and should be built with "./confgure && make". These issues were detected in an package of mine, and were reproducible with the canonical "GNU-Hello" project ( https://www.gnu.org/software/hello/ ) . I'd assume that almost any project that uses "automake" would faces these issues. I am not using "pkg" - under the (wrong?) assumption that a portable package written in C and uses "autotools" should be portable enough to be compiled on many different OSes. > >> It is my understanding the FreeBSD-10 switched to a different 'make' (bmake?), which could be the reason for these differences - but I do not know how to fix them. > > Gnu Make has never been standard on BSD. Most variations of make > programs understand slightly different makefile syntax, so they > generally don't run each other's makefiles. I understand that there are inherent differences. To rephrase my previous question, to a very narrow technical issue: Is there a way to make such a "makefile" complete successfully on FreeBSD: === all: non_existing_command ; true === Or will this construct never work on FreeBSD, and must be changed in order to be portable ? Because as a whole, it is a valid shell command, which should succeed (return exit code 0), according to POSIX (if I understand correctly). Thank you, -gordon