long(!) Re: need help on CFLAGS in /etc/make.conf please

2004-02-19 Thread Paul Seniura
Hi Chuck, me again I'll study the pointers you mentioned, and merely reply what I can for now. Thank you very much for spending time on this. >> The delay in my response here was due to pest control in our building >> and the three-day weekend (I have no li'l-endians at home ;) . > > No problem

Re: need help on CFLAGS in /etc/make.conf please

2004-02-17 Thread Chuck Swiger
Paul Seniura wrote: Hi Chuck, Hi, Paul-- The delay in my response here was due to pest control in our building and the three-day weekend (I have no li'l-endians at home ;) . No problem...and a good job of solving the endian-debate. :-) Paul Seniura wrote: My question for this discussion is speci

Re: need help on CFLAGS in /etc/make.conf please

2004-02-17 Thread Paul Seniura
Hi Chuck, The delay in my response here was due to pest control in our building and the three-day weekend (I have no li'l-endians at home ;) . Chuck Swiger wrote: > Hi, Paul-- > > There is little point to crossposting between -questions and -hackers; > dropping the latter. Actually, <[EMAIL PRO

Re: need help on CFLAGS in /etc/make.conf please

2004-02-16 Thread Lowell Gilbert
Richard Coleman <[EMAIL PROTECTED]> writes: > Unless there is evidence of more recent gcc bugs, that part of the > handbook should really be removed. There's plenty of such evidence. In fact, reports of FreeBSD bugs should be pretty much ignored unless they can be reproduced with -O.

Re: need help on CFLAGS in /etc/make.conf please

2004-02-13 Thread Richard Coleman
Paul Seniura wrote: Chapter 2 of "FreeBSD Developers' Handbook": | 2.4 Compiling with cc | | -O |Create an optimized version of the executable. The compiler |performs various clever tricks to try and produce an executable |that runs faster than normal. You can add a number after the

Re: need help on CFLAGS in /etc/make.conf please

2004-02-13 Thread Chuck Swiger
Hi, Paul-- There is little point to crossposting between -questions and -hackers; dropping the latter. Actually, <[EMAIL PROTECTED]> is probably the most appropriate place... Paul Seniura wrote: My question for this discussion is specifically how to prevent overriding a port's own setting for

Re: need help on CFLAGS in /etc/make.conf please

2004-02-13 Thread Paul Seniura
> On Thu, Feb 12, 2004 at 09:56:08PM -0600, Paul Seniura wrote: > > > > Hi Kris, > > > > > On Thu, Feb 12, 2004 at 06:17:03PM -0600, Paul Seniura wrote: > > > > > > > > Hi y'all, > > > > > > > > I'm trying to find a way to do a CFLAGS+='-O' if and only if such a > > > > parm was not already provid

Re: need help on CFLAGS in /etc/make.conf please

2004-02-12 Thread Kris Kennaway
On Thu, Feb 12, 2004 at 09:56:08PM -0600, Paul Seniura wrote: > > Hi Kris, > > > On Thu, Feb 12, 2004 at 06:17:03PM -0600, Paul Seniura wrote: > > > > > > Hi y'all, > > > > > > I'm trying to find a way to do a CFLAGS+='-O' if and only if such a > > > parm was not already provided before 'make'

Re: need help on CFLAGS in /etc/make.conf please

2004-02-12 Thread Paul Seniura
Hi Kris, > On Thu, Feb 12, 2004 at 06:17:03PM -0600, Paul Seniura wrote: > > > > Hi y'all, > > > > I'm trying to find a way to do a CFLAGS+='-O' if and only if such a > > parm was not already provided before 'make' actually runs. > > > > I had this coded with the single = sign, i.e. without ?=

Re: need help on CFLAGS in /etc/make.conf please

2004-02-12 Thread Kris Kennaway
On Thu, Feb 12, 2004 at 06:17:03PM -0600, Paul Seniura wrote: > > Hi y'all, > > I'm trying to find a way to do a CFLAGS+='-O' if and only if such a > parm was not already provided before 'make' actually runs. > > I had this coded with the single = sign, i.e. without ?= or +=, but > the process s

need help on CFLAGS in /etc/make.conf please

2004-02-12 Thread Paul Seniura
Hi y'all, I'm trying to find a way to do a CFLAGS+='-O' if and only if such a parm was not already provided before 'make' actually runs. I had this coded with the single = sign, i.e. without ?= or +=, but the process still acts as if += was coded anyway, thus tacking on my -O *after* the port's