From owner-freebsd-ports@freebsd.org Sat Oct 3 04:09:29 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 C9AC9A0F467; Sat, 3 Oct 2015 04:09:29 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (kientzle.com [142.254.26.11]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E0B971016; Sat, 3 Oct 2015 04:09:28 +0000 (UTC) (envelope-from tim@kientzle.com) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id t933t1El038632; Sat, 3 Oct 2015 03:55:01 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.109] (192.168.1.101 [192.168.1.101]) by kientzle.com with SMTP id ze7f9npc4f7qvkhuvn25d6t2sw; Sat, 03 Oct 2015 03:55:01 +0000 (UTC) (envelope-from tim@kientzle.com) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: Uses/compiler.mk does not trigger under RBPi From: Tim Kientzle In-Reply-To: Date: Fri, 2 Oct 2015 20:54:48 -0700 Cc: Michelle Sullivan , freebsd-arm@freebsd.org, freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <560DCFD7.30509@sorbs.net> To: =?utf-8?Q?Jos=C3=A9_P=C3=A9rez?= X-Mailer: Apple Mail (2.2104) 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 04:09:29 -0000 What specific ports are you having trouble with? Tim > On Oct 2, 2015, at 2:56 PM, Jos=C3=A9 P=C3=A9rez wrote: >=20 > Hi Michelle, > thank you for your suggestion. Is this another workaround? >=20 > 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. >=20 > 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? >=20 > Thank you. >=20 > Regards, >=20 >=20 > --- > Jos=C3=A9 P=C3=A9rez >=20 > El 2015-10-02 02:29, Michelle Sullivan escribi=C3=B3: >> Jos=C3=A9 P=C3=A9rez 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=3Dclang 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+=3D compiler >> to the makefile first... >> (and it still has some issues but that should solve the first) > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"