Date: Thu, 7 Feb 2002 14:59:14 -0800 From: Joe Kelsey <joe@zircon.seattle.wa.us> To: Terry Lambert <tlambert2@mindspring.com> Cc: current@freebsd.org Subject: Re: gcc3.x issues Message-ID: <15459.1730.129764.975598@zircon.zircon.seattle.wa.us> In-Reply-To: <3C62FEF8.7F3F6FD3@mindspring.com> References: <20020206160611.B181@dragon.nuxi.com> <200202070053.g170rjQ19592@aldan.algebra.com> <20020206170904.C181@dragon.nuxi.com> <15457.55061.55399.596297@zircon.zircon.seattle.wa.us> <20020206172554.A1999@dragon.nuxi.com> <15457.56475.172650.789685@zircon.zircon.seattle.wa.us> <20020206190852.A2932@dragon.nuxi.com> <15458.48143.28786.385095@zircon.zircon.seattle.wa.us> <20020207095912.I3623@elvis.mu.org> <3C62FEF8.7F3F6FD3@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Terry Lambert writes: > I don't think Joe is debating; I think he wants to have a > meta-discussion about what the problem space looks like, > before submitting patches that light up his little corner, > and dark up everything else. Thank you, Terry. Maybe I need to bring up the issue on -arch? Where is it possible to have design discussions without getting slapped down with the "submit a patch or shut up" attitude? I personally work by doing design first, or at least getting to the point where I understand the problem before tackling it in an incremental design/build cycle. Maybe someone can point out the design documentation for the whole complex mk hierarchy and/or for the design behind the importation of gcc and other GNU stuff into the source tree. Or maybe the design is the code... I appreciate your offer of assistance, Terry. I will take your last pointer into the make files and see what I can deduce on my own. /Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15459.1730.129764.975598>