Skip Menu |
 

Date: Wed, 28 Apr 2010 10:44:18 -0400
From: Jeff Blaine <jblaine@kickflop.net>
To: krb5-bugs@mit.edu
Subject: 1.8 build failure only when CPPFLAGS=-DDEBUG
Download (untitled) / with headers
text/plain 1.3KiB
Builds fine without specifying CPPFLAGS.

RHELv5.5 x86 and gcc 4.1.2 as provided by OS.

./configure CPPFLAGS="-DDEBUG"
...
make
...
gcc -fPIC -DSHARED -I../../../include -I../../../include
-I../../../include/kadm5 -I../../../lib/gssapi/krb5
-I../../../lib/gssapi/generic -I../../../lib/gssapi/krb5
-I../../../lib/gssapi/generic -DKRB5_DEPRECATED=1 -DDEBUG -g -O2 -Wall
-Wcast-align -Wshadow -Wmissing-prototypes -Wno-format-zero-length
-Wmissing-format-attribute -Wmissing-prototypes -Wreturn-type
-Wmissing-braces -Wparentheses -Wswitch -Wunused-function -Wunused-label
-Wunused-variable -Wunused-value -Wunknown-pragmas -Wsign-compare
-Wdeclaration-after-statement -Wvariadic-macros -pthread -c server_acl.c
-o server_acl.so.o && mv -f server_acl.so.o server_acl.so
server_acl.c: In function âkadm5int_acl_get_lineâ:
server_acl.c:118: warning: comparison between signed and unsigned
server_acl.c: In function âkadm5int_acl_parse_lineâ:
server_acl.c:179: warning: implicit declaration of function âxprintfâ
server_acl.c: In function âkadm5int_acl_match_dataâ:
server_acl.c:572: error: âentryâ undeclared (first use in this function)
server_acl.c:572: error: (Each undeclared identifier is reported only once
server_acl.c:572: error: for each function it appears in.)
make[3]: *** [server_acl.so] Error 1
To: rt@krbdev.MIT.EDU
Subject: Re: [krbdev.mit.edu #6710] 1.8 build failure only when CPPFLAGS=-DDEBUG
From: Tom Yu <tlyu@MIT.EDU>
Date: Fri, 30 Apr 2010 14:23:14 -0400
RT-Send-Cc:
"Jeff Blaine via RT" <rt-comment@krbdev.mit.edu> writes:

Show quoted text
> Builds fine without specifying CPPFLAGS.
>
> RHELv5.5 x86 and gcc 4.1.2 as provided by OS.
>
> ./configure CPPFLAGS="-DDEBUG"

I think CPPFLAGS=-DDEBUG has never consistently worked from the top
level. I'll look to see if we document this anywhere.
Subject: Compilation fails with -DDEBUG
I needed to build the current tree with -DDEBUG to debug a PKINIT issue
and discovered when doing so that the kadmin code doesn't build with
-DDEBUG. It defines a debugging macro to xprintf, which is not defined
anywhere in the tree.
Date: Thu, 13 May 2010 14:08:15 -0400
From: Jeff Blaine <jblaine@kickflop.net>
To: rt-comment@krbdev.mit.edu
Subject: Re: [krbdev.mit.edu #6721] Compilation fails with -DDEBUG
RT-Send-Cc:
FWIW:

http://krbdev.mit.edu/rt/Ticket/Display.html?id=6710

On 5/13/2010 2:03 PM, Russ Allbery <rra@stanford.edu> via RT wrote:
Show quoted text
> I needed to build the current tree with -DDEBUG to debug a PKINIT issue
> and discovered when doing so that the kadmin code doesn't build with
> -DDEBUG. It defines a debugging macro to xprintf, which is not defined
> anywhere in the tree.
> _______________________________________________
> krb5-bugs mailing list
> krb5-bugs@mit.edu
> https://mailman.mit.edu/mailman/listinfo/krb5-bugs
>
Subject: merging into 6710
merging into 6710
To: rt@krbdev.MIT.EDU
Subject: Re: [krbdev.mit.edu #6721] Compilation fails with -DDEBUG
From: Tom Yu <tlyu@MIT.EDU>
Date: Thu, 13 May 2010 14:25:02 -0400
RT-Send-Cc:
"Russ Allbery <rra@stanford.edu> via RT" <rt-comment@krbdev.mit.edu>
writes:

Show quoted text
> I needed to build the current tree with -DDEBUG to debug a PKINIT issue
> and discovered when doing so that the kadmin code doesn't build with
> -DDEBUG. It defines a debugging macro to xprintf, which is not defined
> anywhere in the tree.

What's probably best is to run "make CPPFLAGS=-DDEBUG" in the
directory (pkinit?) where you want the debugging code turned on. I
think that's the general way that people operate when they're
debugging something they've added debugging code to. (and we should
document this better) Are there specific pieces of debugging code you
need working in kadmin?
From: Russ Allbery <rra@stanford.edu>
To: rt@krbdev.mit.edu
Subject: Re: [krbdev.mit.edu #6710] Re: [krbdev.mit.edu #6721] Compilation fails with -DDEBUG
Date: Thu, 13 May 2010 11:28:09 -0700
RT-Send-Cc:
"Tom Yu via RT" <rt-comment@krbdev.mit.edu> writes:

Show quoted text
> What's probably best is to run "make CPPFLAGS=-DDEBUG" in the directory
> (pkinit?) where you want the debugging code turned on. I think that's
> the general way that people operate when they're debugging something
> they've added debugging code to. (and we should document this better)

Yeah, that's what I fell back on doing.

Show quoted text
> Are there specific pieces of debugging code you need working in kadmin?

No, I was just building the whole tree with debugging enabled since it
seemed simplest.

--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>