Date: Fri, 02 Oct 2015 23:56:24 +0200 From: =?UTF-8?Q?Jos=C3=A9_P=C3=A9rez?= <fbl@aoek.com> To: Michelle Sullivan <michelle@sorbs.net> Cc: freebsd-ports@freebsd.org, freebsd-arm@freebsd.org Subject: Re: Uses/compiler.mk does not trigger under RBPi Message-ID: <c5f4ab0adc751410b8205e6f3aedda57@mail.yourbox.net> In-Reply-To: <560DCFD7.30509@sorbs.net> References: <bfe1c24f878ca90245680b2cfae1f6d2@mail.yourbox.net> <560DCFD7.30509@sorbs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Michelle,
thank you for your suggestion. Is this another workaround?
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.
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?
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 <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,
>>
> Try adding:
>
> USES+= compiler
>
> to the makefile first...
>
> (and it still has some issues but that should solve the first)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c5f4ab0adc751410b8205e6f3aedda57>