Date: Fri, 5 May 1995 09:04:14 -0700 (PDT) From: Steven G Kargl <kargl@troutmask.apl.washington.edu> To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Cc: freebsd-ports@FreeBSD.org Subject: Re: make.conf and bsd.ports.mk Message-ID: <199505051604.JAA27016@troutmask.apl.washington.edu> In-Reply-To: <199505050220.TAA08380@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 4, 95 07:20:34 pm
next in thread | previous in thread | raw e-mail | index | archive | help
According to Rodney W. Grimes: > > > > > Satoshi, Jordan, whomever, > > > > Is there an obvious reason (that I am missing) why bsd.port.mk does > > not scan make.conf for CFLAGS? The only place I can find that uses > > make.conf is sys.mk, but this isn't used for ports. > > If you type ``make'' sys.mk is read, you have to do a ``make -r'' to > stop make from reading /usr/share/mk/sys.mk. > > The problem you are most likely seeing is that most Makefile's in > the ports have there own .c.o rules that overrides the one in sys.mk :-(. > I knew the answer was probably simply, but I'm not too familiar with how the *.mk files interact. I played around with the port of top-3.3, and found that if I changed the Makefile in top/work from CDEF = -O CFLAGS = -DHAVE_GETOPT $(CDEF) to #CDEF = -O CFLAGS += -DHAVE_GETOPT $(CDEF) The build does the Right Thing. Should this type of change be added to the GUIDELINES for porting to FreeBSD? I admit I like the convenience of the ports, but I don't want to edit the Makefile(s) in every port to include CFLAGS = -O2 -m486 -pipe (e.g., consider the fun of editing the Makefiles in XFree86). Rod, do you have a separate business related email address? -- Steven G. Kargl | Phone: 206-685-4677 | Applied Physics Lab | Fax: 206-543-6785 | Univ. of Washington |---------------------| 1013 NE 40th St | FreeBSD 2.1-current | Seattle, WA 98105 |---------------------|
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505051604.JAA27016>