id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
5153	Behavior difference of 32-bit and 64-bit libraries	lcarreon@…	Beman Dawes	"Hi,

I have built the 32-bit and 64-bit versions of the Boost libraries on Solaris 10 x86.  I specified the following options when I built the libraries:

	runtime-link=shared

	link=shared

Now, I'm trying to experiment with the libraries and I'm observing some inconsistency.

I wrote the program test_space.cpp to display the space information about the current filesystem using version 3 of the Boost filesystem library.

When I run the 32-bit version of test_space.cpp, I get the following results:

  capacity  =        33666173952

  free      =                  0

  available =        33410671616


When I run the 64-bit version of test_space.cpp, I get the following results:

  capacity  =        33666173952

  free      =        33410000896

  available =        33073339392

Based on the above results, it seems that the 32-bit version is not behaving correctly.  Am I missing something here?

Here's another observation I have.  I wrote another program test_direntry.cpp to display the file type of three paths again using version 3 of the Boost filesystem library.

When I run the 32-bit version of test_direntry.cpp, I get the following results:

  An unknown path:

    dummy status is file not found

  A file path:

    bin-soli32/test_direntry status is type unknown

  A directory path:

    /home/Leo/Devel/projects/compiler_tests/test_direntry status is type unknown

When I run the 64-bit version of test_direntry.cpp, I get the following results:

  An unknown path:

    dummy status is file not found

  A file path:

    bin-soli64/test_direntry status is regular file

  A directory path:

    /home/Leo/Devel/projects/compiler_tests/test_direntry status is directory file

It appears from the above results that the 32-bit version of test_direntry.cpp isn't behaving correctly.  Do you have an idea what I could have done wrong or is this a bug in the library?

Regards,
Leo
"	Bugs	closed	To Be Determined	filesystem	Boost 1.45.0	Problem	fixed