From owner-freebsd-hackers Mon Mar 30 13:09:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22529 for freebsd-hackers-outgoing; Mon, 30 Mar 1998 13:09:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22499 for ; Mon, 30 Mar 1998 13:08:38 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id QAA13473; Mon, 30 Mar 1998 16:07:53 -0500 (EST) Date: Mon, 30 Mar 1998 16:07:53 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: Brian Cully cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Objective C rules for /usr/share/mk In-Reply-To: <19980330154514.35130@kublai.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 30 Mar 1998, Brian Cully wrote: > On Mon, Mar 30, 1998 at 03:06:51PM -0500, Chuck Robey wrote: > > Brian, you might not be aware that the make utility has compiled into it > > to read the startup file /usr/share/mk/sys.mk, but you're really not > > supposed to modify that. sys.mk sources in /etc/make.conf, and that's > > (/etc/make.conf) where local user modifications are expected to go. > > That explains a lot of the behaviour I was seeing (I suppose I should > have completely read the make man page before diving in). Thanks. > > > That's probably the source of some of the things you mentioned, that you > > supposed were compiled in. Take a look at /etc/make.conf, and customize > > to your hearts' content, but please leave sys.mk entirely alone > > (especially if you ever intend to compile the FreeBSD source tree). > > I'm aware of the problems with modifying stuff in /usr/share/mk. What > I'd like to see is having Objective C progs be compilable without > /etc/make.conf mucking (as C++ does). > > Assuming I send-pr a good set of patches (the ones I've sent don't cut > it), would they be commited, or should I not bother? Well, seeing as it really affects a smallish number of hackers, and makes modifications that some might object to .... I dunno, I think I would just make the changes locally. I'm putting out an opinion here, not a fact, so if you disagree, go ahead and send-pr it. It's likely to sit forever in the database, tho. It's just not something that's black and white correct, if you see what I mean. > > -bjc > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message