Marc Espie <es...@nerim.net> wrote:
> But there are things that actually use the "unknown". Most notorious being
> gcc.
Hmm... no?
I'm too lazy to compile a gcc port on FreeBSD now, but as far as I can
tell, it just uses...
.if ${ARCH} == "amd64"
CONFIGURE_TARGET= x86_64-portbld-${OPSYS:L}${OSREL}
.else
CONFIGURE_TARGET= ${ARCH}-portbld-${OPSYS:L}${OSREL}
.endif
... and that's it.
> Even though it's one of those annoying ports that you have to bump every
> release because the directory name changes for no reason relevant to how
> we do things.
That's the OSREV part of the operating system. Different issue.
> if that's so simple, how about a patch so we get something sane ? like
> amd64-openbsd, the way the perl does, instead of the obnoxious
> amd64-unknown-openbsd5.5 that we hate ?
I doubt that you can just _drop_ the middle part. We can replace
"unknown" with something else.
"dummy"? No, Adam will think we're stupid.
"generic"? No, Adam will think we're cheap.
Maybe we can just leave it.
--
Christian "naddy" Weisgerber na...@mips.inka.de
