Nathan Whitehorn <nwhitehorn_at_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. > 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? DES -- Dag-Erling Smørgrav - des_at_des.noReceived on Sat Aug 21 2010 - 19:54:11 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:06 UTC