Added to developer's FAQ:
src/Makefile.custom can be used to set environment variables,
like CUSTOM_COPT, that are used for every compile.
---
Magnus Hagander wrote:
> >> If we did what you suggest, then --enable-
Matthias Luedtke wrote:
> And while we are at it, how about some CFLAGS="-DOPTIMIZER_DEBUG"
> sweetness for the debugging section in the Dev FAQ?
Most of the debugging macros are not documented because their purpose
only arises out of the source code.
--
Peter Eisentraut
http://developer.postgr
Hi all,
Magnus Hagander wrote:
Personally, in my development tree I use a Makefile.custom containing
# back off optimization unless profiling
ifeq ($(PROFILE),)
CFLAGS:= $(patsubst -O2,-O1,$(CFLAGS))
endif
-O1 still generates "uninitialized variable" warnings but the code is a
lot saner to
>> If we did what you suggest, then --enable-debug would cause performance
>> degradation, which would cause people to not use it, which would result
>> in most binaries being completely undebuggable rather than only partially.
>> Doesn't sound like a good tradeoff to me.
>>
>> Personally, in my de
Tom Lane wrote:
> NikhilS <[EMAIL PROTECTED]> writes:
> > True, this is how I myself circumvent this problem too. But IMHO,
> > explicitly passing CFLAGS when we are invoking --enable-debug (which does
> > add -g, but leaves some optimization flag around which deters debugging)
> > does not seem co
NikhilS <[EMAIL PROTECTED]> writes:
> True, this is how I myself circumvent this problem too. But IMHO,
> explicitly passing CFLAGS when we are invoking --enable-debug (which does
> add -g, but leaves some optimization flag around which deters debugging)
> does not seem correct?
If we did what you
Hi,
On 2/2/07, Gavin Sherry <[EMAIL PROTECTED]> wrote:
On Fri, 2 Feb 2007, NikhilS wrote:
> Hi,
>
> Indeed it does, apologies for not doing the entire groundwork. But what
it
> also does is that it adds -O2 by default for gcc even when
--enable-debug is
> specified. gdb is not able to navigate
On Fri, 2 Feb 2007, NikhilS wrote:
> Hi,
>
> Indeed it does, apologies for not doing the entire groundwork. But what it
> also does is that it adds -O2 by default for gcc even when --enable-debug is
> specified. gdb is not able to navigate the stack traces properly with this
> optimization in plac
Hi,
Indeed it does, apologies for not doing the entire groundwork. But what it
also does is that it adds -O2 by default for gcc even when --enable-debug is
specified. gdb is not able to navigate the stack traces properly with this
optimization in place. Especially tracing of static functions beco
On Fri, 2 Feb 2007, NikhilS wrote:
> Hi,
>
> configure with --enable-debug does not seem to add "-g" to CFLAGS while
> compiling with gcc. Guess we will need to change configure.in as below:
Erm... works for me and everyone else... AFAIK.
Thanks,
Gavin
---(end of broadc
Hi,
configure with --enable-debug does not seem to add "-g" to CFLAGS while
compiling with gcc. Guess we will need to change configure.in as below:
***
# supply -g if --enable-debug
! if test "$enable_debug" = yes && test "$ac_cv_prog_cc_g" = yes; then
CFLAGS="$CFLAGS -g"
fi
--
11 matches
Mail list logo
