Uses/compiler.mk does not trigger under RBPi

Michelle Sullivan michelle at sorbs.net
Sat Oct 3 10:15:10 UTC 2015


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 at raspberry-pi:~ % cat Makefile
>>> all:
>>>         @${ECHO_CMD} ${LOCALBASE}
>>>         @${ECHO_CMD} ${COMPILER_TYPE}
>>> .include <bsd.port.mk>
>>> me at raspberry-pi:~ % make
>>> /usr/local
>>>
>>> me at raspberry-pi:~ %
>>>
>>> As a result building ports is a nightmare.
>>>
>>> Note how in AMD64 it works:
>>> me at amd64:~ % make
>>> /usr/local
>>> clang
>>> me at 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 at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"


-- 
Michelle Sullivan
http://www.mhix.org/



More information about the freebsd-arm mailing list