From owner-freebsd-ports@freebsd.org Sat Oct 3 10:15:10 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 166A8A0FEB3; Sat, 3 Oct 2015 10:15:10 +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 F39521B0D; Sat, 3 Oct 2015 10:15:09 +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 <0NVN00G9T3FLDC00@hades.sorbs.net>; Sat, 03 Oct 2015 03:21:23 -0700 (PDT) Message-id: <560FAAA4.6080800@sorbs.net> Date: Sat, 03 Oct 2015 12:15:00 +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> In-reply-to: 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: Sat, 03 Oct 2015 10:15:10 -0000 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+? Regards, Michelle > > Thank you. > > Regards, > > > --- > José Pérez > > El 2015-10-02 02:29, Michelle Sullivan escribió: >> José Pérez wrote: >>> Hi, >>> I've notice that Uses/compiler.mk is not triggered and as a >>> consequence does to set COMPILER_TYPE. >>> >>> me@raspberry-pi:~ % cat Makefile >>> all: >>> @${ECHO_CMD} ${LOCALBASE} >>> @${ECHO_CMD} ${COMPILER_TYPE} >>> .include >>> me@raspberry-pi:~ % make >>> /usr/local >>> >>> me@raspberry-pi:~ % >>> >>> As a result building ports is a nightmare. >>> >>> Note how in AMD64 it works: >>> me@amd64:~ % make >>> /usr/local >>> clang >>> me@amd64:~ % >>> >>> As a workaround I set COMPILER_TYPE=clang in /etc/make.conf but this >>> is just an ugly hack. >>> >>> Can some expert trow a little light on this? Thank you. >>> >>> Regards, >>> >> Try adding: >> >> USES+= compiler >> >> to the makefile first... >> >> (and it still has some issues but that should solve the first) > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" -- Michelle Sullivan http://www.mhix.org/