Everyone, So I figured out the culprit (and what made this bug so hard.) I was trying to build out of an NFS share. Now, some NFS shares work ok, some don't. On that solaris machine, my home directory is on one NFS share (from a linux server), while the source was on a different one that was shared by my Mac. (We are a Mac/Solaris/Windows shop.) I could build locally on the solaris box our out of my home NFS share, but not out of the NFS shared by my mac. Still working on that, don't know why it doens't like NFS or how to reconfigure. I'll post more to this thread when I find out. So this is just an FYI to everyone. -Andrew On 11/15/05 10:29 AM, "Andrew Mellinger" <amelling@nasmedical.com> wrote:
Everyone,
I apologize if this isn't the right forum for bjam issues, but I can't find a group specifically for bjam. If someone knows of one, please direct me that way.
I have tried searching google, but haven't identified anything relevant.
I am trying to build bjam on SunOS 5.8 using gcc 3.1 with the posix thread model. When I do a gcc-v I also get:
Configured with: ../configure --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --disable-nls
I don't know if any of that is relevant. When I run ./build.sh from the jam_src directory (either in boost source tree or a download of 3.1.11) I get the following output.