Hmm...I only have one 'bmake':

jaj@dhcp12-79[~]$ which bmake
/Volumes/NetBSD/pkg/bin/bmake
jaj@dhcp12-79[~]$ ls -l /usr/bin/bmake
ls: /usr/bin/bmake: No such file or directory

And I definitely can compile other programs.  This is an issue tied to 
pkgsrc.

Thanks!

Chuck Yerkes wrote:

>I wonder about "which bmake" ....
>
>With 10.3 (panther), Apple changed vi from nvi to vim.  Annoying.
>They also made "make" be gmake.  "bmake" is the lovely berkeley make
>we know and love.
>
>You might be hitting the "wrong" bmake.
>
>You might try (temporarily) running "gzip /usr/bin/bmake"
>to get it out of the way.
>
>OTOH, it may not be this at all.
>
>You *can* compile a helloworld.c program, right?
>
>
>Quoting David Hopper (DHOP@gesi.net):
>  
>
>>Hi all.  Something is broken on this OS X pkgsrc installation, such that for
>>certain packages (most of them, unless they are terribly simple) configure
>>fails when run from pkgsrc (via bmake in, say, devel/gettext-lib), but
>>completes when run explicitly within the working directory.
>>
>>I get the following broken config.log:
>>
>>---
>>configure:1817: checking for C compiler default output
>>configure:1820: gcc -O2 -I/Volumes/NetBSD/pkg/include
>>-D_INTL_REDIRECT_MACROS=1 -DSTATIC=static -no-cpp-precomp
>>-I/Volumes/NetBSD/pkg/include  -Wl,-L/usr/lib -liconv
>>-L/Volumes/NetBSD/pkg/lib conftest.c  >&5
>>ld: can't open:  (No such file or directory, errno = 2)
>>configure:1823: $? = 1
>>configure: failed program was:
>>#line 1801 "configure"
>>#include "confdefs.h"
>>    
>>