From owner-freebsd-ports@freebsd.org Sun Oct 4 10:56:39 2015 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A61EA104BA; Sun, 4 Oct 2015 10:56:39 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (mail.sorbs.net [67.231.146.200]) by mx1.freebsd.org (Postfix) with ESMTP id EF78C1EA5; Sun, 4 Oct 2015 10:56:38 +0000 (UTC) (envelope-from michelle@sorbs.net) MIME-version: 1.0 Content-transfer-encoding: 8BIT Content-type: text/plain; charset=UTF-8 Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0NVP00J7I00QYS00@hades.sorbs.net>; Sun, 04 Oct 2015 04:02:51 -0700 (PDT) Message-id: <561105DD.1030903@sorbs.net> Date: Sun, 04 Oct 2015 12:56:29 +0200 From: Michelle Sullivan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24) Gecko/20100301 SeaMonkey/1.1.19 To: =?UTF-8?B?Sm9zw6kgUMOpcmV6?= Cc: freebsd-arm@freebsd.org, freebsd-ports@freebsd.org Subject: Re: Uses/compiler.mk does not trigger under RBPi References: <560DCFD7.30509@sorbs.net> <560FAAA4.6080800@sorbs.net> In-reply-to: <560FAAA4.6080800@sorbs.net> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Oct 2015 10:56:39 -0000 Michelle Sullivan wrote: > José Pérez wrote: > >> Hi Michelle, >> thank you for your suggestion. Is this another workaround? >> > > As far as I was aware if you need Uses/compiler.mk it should be > specified (there are params if a particular compiler/feature set is > required) with USES+=compiler > > >> I mean: many port Makefiles are affected, in the sense that when built >> on Intel/AMD the ports just work because Uses/compiler.mk is sucked in >> automatically, but it is not on ARM. >> > > But do they need Uses/compiler.mk ? If so then it might be someone > screwed up, if they don't actually need it then that would be why it's > not specified. > > >> So, shall I report a bug on all the ports that use COMPILER_TYPE, or >> is there a way to have ARM trigger Uses/compiler.mk? >> > > If they use/require COMPILER_TYPE and don't specify USES+= compiler then > I would log a bug for each port and let the ports manager take care of > it as it's probably a change in default behavior that has caused the > mess... how many are we talking about? 10+, 100+, 1000+? > > Another (additional) thought is that if amd64/i386 is automatically pulling in Uses/compiler.mk when it is not explicitly requested, one could consider that in itself a (the) bug. -- Michelle Sullivan http://www.mhix.org/