Uses/compiler.mk does not trigger under RBPi
michelle at sorbs.net
Sun Oct 4 10:56:39 UTC 2015
Michelle Sullivan wrote:
> 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+?
Another (additional) thought is that if amd64/i386 is automatically
pulling in Uses/compiler.mk when it is not explicitly requested, one
could consider that in itself a (the) bug.
More information about the freebsd-ports