From owner-freebsd-arm@freebsd.org  Thu Oct  1 23:39:13 2015
Return-Path: <owner-freebsd-arm@freebsd.org>
Delivered-To: freebsd-arm@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 8888FA0D048;
 Thu,  1 Oct 2015 23:39:13 +0000 (UTC) (envelope-from fbl@aoek.com)
Received: from srv56-45.cdn.bestreaming.com (ns330343.ip-37-187-119.eu
 [37.187.119.94])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id E14D81279;
 Thu,  1 Oct 2015 23:39:11 +0000 (UTC) (envelope-from fbl@aoek.com)
Received: from mail.yourbox.net (localhost [127.0.0.1])
 by srv56-45.cdn.bestreaming.com (8.14.7/8.14.7) with ESMTP id t91Nd7aI058214; 
 Fri, 2 Oct 2015 01:39:07 +0200 (CEST) (envelope-from fbl@aoek.com)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
Date: Fri, 02 Oct 2015 01:39:07 +0200
From: =?UTF-8?Q?Jos=C3=A9_P=C3=A9rez?= <fbl@aoek.com>
To: freebsd-ports@freebsd.org, freebsd-arm@freebsd.org
Subject: Uses/compiler.mk does not trigger under RBPi
Message-ID: <bfe1c24f878ca90245680b2cfae1f6d2@mail.yourbox.net>
X-Sender: fbl@aoek.com
User-Agent: Roundcube Webmail/1.0.3
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Oct 2015 23:39:13 -0000

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 <bsd.port.mk>
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,

-- 
José Pérez