On Mon, 2008-08-04 at 17:04 -0700, Raoul Duke wrote:
> 3. i installed boost via "sudo port install boost" and port says:
> Port boost 1.35.0_2 is installed as an image in:
> /opt/local/var/macports/software/boost/1.35.0_2

Okay. I suspect that this is the ultimate source of the problem. I'll
post a note to bitc-dev to ask people how they are dealing with this on
OS X. There are one or two other people attempting that build.

One way to determine if you have a 64-bit machine is to compile and run:

  #include <stdio.h>
  int main(int argc, const char *argv[]) {
    printf("void * is %d bytes\n", sizeof(void *));
  }

This is basically the check that is being done in the "check for native
64-bit build". Since that check is saying no, I think it is safe to
assume that you are running a 32-bit system.

Just so I am clear, is the configure output that you sent produced with
or without the --with-boost options to configure?

shap

> 
> this is the output from configure
> 
> checking build system type... i386-apple-darwin8.11.1
> checking host system type... i386-apple-darwin8.11.1
> checking target system type... i386-apple-darwin8.11.1
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /usr/bin/grep
> checking for egrep... /usr/bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for void *... yes
> checking size of void *... 4
> checking For 64-bit native build... no
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking for gcc... (cached) gcc
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ISO C89... (cached) none needed
> checking for gcc option to accept ISO C99... -std=gnu99
> checking for gcc -std=gnu99 option to accept ISO Standard C...
> (cached) -std=gnu99
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether make sets $(MAKE)... yes
> checking for ranlib... ranlib
> checking for ccache... no
> checking for makeinfo... yes
> checking for texi2dvi... yes
> checking for dvips... no
> checking for inline... inline
> checking for astmaker... no
> checking for a sed that does not truncate output... /usr/bin/sed
> checking for bison... bison
> checking for bison version...
> checking for gawk... no
> checking for mawk... no
> checking for nawk... no
> checking for awk... awk
> checking for /usr/share/osdoc... no
> checking for /usr/share/osdoc... (cached) no
> checking for stdint.h... (cached) yes
> checking for inttypes.h... (cached) yes
> checking unicode/uchar.h usability... no
> checking unicode/uchar.h presence... no
> checking for unicode/uchar.h... no
> checking for boostlib >= 1.33.1... yes
> checking whether the Boost::System library is available... yes
> checking whether the Boost::Filesystem library is available... yes
> _______________________________________________
> bitc-dev mailing list
> [email protected]
> http://www.coyotos.org/mailman/listinfo/bitc-dev

_______________________________________________
bitc-dev mailing list
[email protected]
http://www.coyotos.org/mailman/listinfo/bitc-dev

Reply via email to