What specific ports are you having trouble with?
Tim
> On Oct 2, 2015, at 2:56 PM, José Pérez <f...@aoek.com> wrote:
>
> 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)
> _______________________________________________
> freebsd-...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org"
_______________________________________________
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
