Date: Sat, 21 Aug 2010 17:01:54 -0500 From: Nathan Whitehorn <nwhitehorn@freebsd.org> To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= <des@des.no> Cc: powerpc@freebsd.org, FreeBSD Tinderbox <tinderbox@freebsd.org>, current@freebsd.org Subject: Re: [head tinderbox] failure on powerpc64/powerpc Message-ID: <4C704CD2.9040604@freebsd.org> In-Reply-To: <86aaofpr7j.fsf@ds4.des.no> References: <201008190304.o7J34Wa4089466@freebsd-current.sentex.ca> <86occzdmhg.fsf@ds4.des.no> <4C6D557E.6080406@freebsd.org> <86sk29ws6u.fsf@ds4.des.no> <4C6E825C.5060509@freebsd.org> <86fwy9f5vj.fsf@ds4.des.no> <4C6F0813.9030007@freebsd.org> <86aaofpr7j.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/21/10 16:54, Dag-Erling Smørgrav wrote: > Nathan Whitehorn<nwhitehorn@freebsd.org> writes: > >> I'm the first to admit that many of the config tricks involved in this >> port, and GENERIC64, are ugly hacks, largely because config(8) was not >> designed with such things in mind. >> > It's not just "config tricks and ugly hacks", it also violates the > assumption that target names are unique. > This was discussed on arch several months ago. Breaking that assumption seems much better, in the long term, than any of the alternatives in order to accomodate mips[64][el|eb], arm[eb], powerpc[64], and any other similar situations we may run into in the future. Sharing an include/machine directory, which is a side effect, also means that things like cc -m32 work out of the box. >> To address the immediate problem, I think the best solution is to use >> the -m option to config to reject kernel configs for different >> architectures, >> > I'm not sure I understand what you mean (or rather, how it would help > the tinderbox). What *would* help would be an easy way to determine, > *before* trying to build it, whether a specific kernel config is > appropriate for a specific target. Can you think of an easier way to do > this than to scan the config for the "machine" line? > That's exactly what I proposed. You use config, before trying the build, to look up the machine specification for the config file. I sent you a 5 line patch to tinderbox.pl that does this by private email. Other alternatives would be having sys/$MACHINE/conf.$MACHINE_ARCH directories or something, but that invites far more breakage. -Nathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C704CD2.9040604>