On 2019-Nov-19, at 19:58, Mark Linimon <[email protected]> wrote:
>> devel/freebsd-gcc6
>> devel/freebsd-gcc6@aarch64
>
> These two ports are exactly equivalent.
>
> I did not have enough time before the commit to puzzle out a way to
> work around that. I have limited understanding of flavors.
>
> The way it *should* work IMHO is for the former to refuse to build
> with a message like "is a meta port -- nothing to build." This is
> used in several other existing masterports.
>
Ahh. That helps explain the use of "native" in devel/binutils and
why it is listed first and that there is a matching default, from
looking . . .
FLAVORS= native aarch64 aarch64_none_elf amd64 arm_gnueabi arm_none_eabi
\
avr i386 mingw32 mips mips64 powerpc64 riscv64 s390x sparc64
FLAVOR?= native
Looks like that makes testing for the default (or literal native here) testable:
.if ${FLAVOR} != native
So adding an extra flavor as a default could allow for generating an error?
Thanks for the note. It helped me understand what to expect and what to watch
out for.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "[email protected]"
