See attached build log. (Please do not complain about the need for looking at the build log until you can provide an easy way to open bugs with the correct data picked out of a tinderbox log. Thanks.)
Created attachment 245676 [details] Build log
Created attachment 245717 [details, diff] add LDFLAGS and CPPFLAGS to LOCALFLAGS rhapsody's buildsystem doesn't distinguish between different sorts of compiler flags, so a ``correct'' fix is to add LDFLAGS to the LOCALFLAGS variable.
Why are you using CPPFLAGS on LOCALFLAGS? Where does this variable come from and why do you need it?
(In reply to comment #3) > Why are you using CPPFLAGS on LOCALFLAGS? Where does this variable come from > and why do you need it? CPPFLAGS is just another *FLAGS variable in the list of conventions all Makefiles should support. Or at least that's my understanding ;-). If you think it shouldn't be there and want me to roll another patch I can.
tinderbox has reproduced this issue with version 0.28b - Updating summary.
