include problem building BDB 4.6.21 w/ /usr/local

[Bayard Bell]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Did a bit more digging. The problem looks to be with Apple's build of  
make. Extracted from "make -dp" output:

# default
.INCLUDE_DIRS = /usr/include /usr/local/include /usr/include

Filing bug report now. Again dtruss gives me a clue to put it  
together. Looking at the top of the output, there's some other  
sloppiness in how Apple is maintaining their make port:

# GNU Make 3.81
# Copyright (C) 2006  Free Software Foundation, Inc.
# This is free software; see the source for copying conditions.
# There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
# PARTICULAR PURPOSE.

# This program built for powerpc-apple-darwin9.0

Pretty sure it wasn't built for PPC, at least not PPC alone:

precious:Downloads bayard$ file -L /usr/bin/make
/usr/bin/make: Mach-O universal binary with 2 architectures
/usr/bin/make (for architecture i386):  Mach-O executable i386
/usr/bin/make (for architecture ppc7400):       Mach-O executable ppc

Am 17 Oct 2009 um 10:19 schrieb Joshua Root:

> On 2009-10-17 11:57, Bayard Bell wrote:
>> I've been looking through tickets, trying to figure out what's going
>> wrong. There's an open ticket for this, 19918. As far as I can see,  
>> the
>> immediate problem occurs when you've got db.h in /usr/local/include.
>> Renaming the file certainly fixes the problem. (Three cheers to  
>> dtruss
>> for giving me a handle on this.)
>>
>> What doesn't really make sense to me is why or how this is found in  
>> the
>> first instance: I'd argue strongly that the pre-processor shouldn't  
>> be
>> looking there by default, and it's not much evident to me that  
>> CPPFLAGS
>> is being constructed to tell it to do so. Before digging around  
>> further,
>> I thought I'd ask if anyone knew why this might be.
>
> We're not telling it to look there, it just does. The only way to  
> avoid
> this would be to use -nostdinc, but then you have to somehow  
> reconstruct
> the other default search paths and tell it to look in them.
>
> So basically, there's not much we can do about it, and the place to
> report the issue is <http://bugreport.apple.com/> and/or
> <http://gcc.gnu.org/bugzilla/>. (Note that upstream changes to GCC at
> this point will likely never be distributed by Apple, since they are
> moving to LLVM.)
>
> - Josh

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (Darwin)

iEYEARECAAYFAkrg890ACgkQcZQHT1XL9xllHwCgspk79GtWAk9lWbA0betUE3bZ
a5gAoLnPUcOoq1dqiwnRshfFhNYX9Ne3
=+00p
-----END PGP SIGNATURE-----