Phil Endecott wrote:
Beman Dawes wrote:
I should have asked not just for trouble reports, but success reports too.
I have successfully built rc2 on my Debian Linux box with gcc 4.1.3 - though I have probably not exercised it enough to detect any problems.
A few notes, which are not things that need to be fixed for the release:
- The top-level directory after untaring was called boost-posix-2008-03-21; I was expecting something more like boost-1.35.0-rc2; is this going to change for the final version?
Yep. I picked that up too on a Windows install. I've added it to the issues list and will fix for RC3, which I hope is the final RC.
- It's nice that the build process uses "./configure; make; make install" but it would be even nicer if there was a file called INSTALL that explained, in a couple of lines, that that was the way to build it. This would make it even more like other open-source packages.
Would you like to volunteer to draft INSTALL? It should have two sections, one for POSIX-like systems, and one for Windows, and should also include a pointer to the full install docs. (Added to issues list, but not considered a showstopper.)
- It looks as if configure checks for some dependencies (ICU?), but it didn't check whether I had the necessary python or bzip2 headers installed; it would be great if it could do this automatically.
Doug, is this something you could look at? (Added to issues list, but not considered a showstopper.) Thanks for the report, Phil! --Beman