Date: Mon, 07 Jul 2003 09:23:24 +0900 From: Jun Kuriyama <kuriyama@imgsrc.co.jp> To: naddy@mips.inka.de (Christian Weisgerber) Cc: freebsd-ports@freebsd.org Subject: Re: config.guess (was: Re: cvs commit: ports/audio/libmikmod/files patch-config.sub) Message-ID: <7mwuev9ocj.wl@black.imgsrc.co.jp> In-Reply-To: <bdajjd$2gjo$1@kemoauc.mips.inka.de> References: <200306190941.h5J9fIYL073911@repoman.freebsd.org> <20030620165635.GA53379@rot13.obsecurity.org> <bd076g$1nul$1@kemoauc.mips.inka.de> <7misqx7ftv.wl@black.imgsrc.co.jp> <bdajjd$2gjo$1@kemoauc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
At Tue, 24 Jun 2003 23:30:42 +0000 (UTC),
Christian Weisgerber wrote:
> > I'm not sure whether we should import GNU stuff in ports tree or not.
> > I'm building amd64 packages with my local $CONFIG_SUB_OVERRIDE patch.
> > This is inspired from NetBSD's $CONFIG_SUB_OVERRIDE. [...]
>
> Well, this is very similar to the CONFIG_GUESS_DIRS approach I
> copied from OpenBSD. From the porter's perspective, the only
> difference is the name of the variable.
>
> > As we provide correct (hopefully :-)) $CPU-$VENDOR-$OS string in ports
> > infrastracture, I'm using extremely simplified config.sub script.
>
> Yes, it may very well be possible to replace config.guess/config.sub
> by extremely simplified scriptlets.
I don't care what variable name is used. :-)
Only I worry is whether we should import GPL'ed stuff in ports tree.
> > o Error logs which I cannot build with this patch:
>
> But none of these are due to config.* problems, are they?
Yes, there are many ports which should be patched for amd64 other than
config.* stuff.
--
Jun Kuriyama <kuriyama@imgsrc.co.jp> // IMG SRC, Inc.
<kuriyama@FreeBSD.org> // FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7mwuev9ocj.wl>