On Sun, Feb 02, 2014 at 04:23:22AM +0100, Juan Francisco Cantero Hurtado wrote:
> On Sat, Feb 01, 2014 at 07:11:25PM -0500, Adam Jensen wrote:
> > On Sat, 1 Feb 2014 00:52:31 +0000 (UTC)
> > na...@mips.inka.de (Christian Weisgerber) wrote:
> >
> > > FreeBSD is more playful: It has ${ARCH}-portbld-freebsd
> > > ${OSREL} in its ports tree and ...
> > >
> >
> > I wonder how the FreeBSD guys changed it "without breaking every
> > gnu-configure script in existence".
>
> You just need to create a few tens of thousands of patches to fix the
> mess and send everything to upstream.
Actually, we have our own config.guess so getting configured as something
else is already patched for.
But there are things that actually use the "unknown". Most notorious being
gcc.
So far, I don't see anyone jumping up and down to fix gcc to use something
sane.
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.
naddy ? brad ?
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 ?
