[Iostreams] Fails to build on Windows
At the time of writing, Iostreams from CVS head still does not build on Windows XP, due to missing header files. The build starts with these comments: ****************************************************** Building Boost.Iostreams with bzip2 support disabled. HINT: define the environment variable BZIP2_SOURCE to point to the root directy of your bzip2 installation if you have one. For more options, consult the Boost.Iostreams documentation ****************************************************** ****************************************************** Building Boost.Iostreams with zlib and gzip support disabled. HINT: define the environment variable BZIP2_SOURCE to point to the root directy of your zlib installation if you have one. For more options, consult the Boost.Iostreams documentation ****************************************************** Presumably "BZIP2_SOURCE" should not effect both types of compression, and "directy" is a typo. Anyway, the following errors are then reported 8 times each: bzip2.cpp(14) : fatal error C1083: Cannot open include file: 'bzlib.h': No such file or directory zlib.cpp(14) : fatal error C1083: Cannot open include file: 'zlib.h': No such file or directory The command line I used for the build was: bjam -sTOOLS=vc-8_0 -sICU_PATH=F:\Dev\icu-3.2 -sPYTHON_ROOT=C:\Apps\Python24 -sPYTHON_VERSION=2.4
Keith MacDonald wrote:
At the time of writing, Iostreams from CVS head still does not build on Windows XP, due to missing header files. The build starts with these comments:
Presumably "BZIP2_SOURCE" should not effect both types of compression, and "directy" is a typo.
BZIP2_SOURCE is a typo, too. Thanks.
Anyway, the following errors are then reported 8 times each:
I figured out what's going wrong, but don't know how to fix it, because of my limited understanding of the Jam language. I'll post to the build list to find out. Thanks for reporting the problem. Jonathan
Keith MacDonald wrote:
At the time of writing, Iostreams from CVS head still does not build on Windows XP, due to missing header files. The build starts with
Okay, I've tried to fix the problem. (I've learned not to say it's fixed, since I don't fully understand the build system). Would you try to build again and see what happens? Jonathan
Have you checked in the changed files, because the build still has the same problems? Incidentally, as this is mainly an issue for Windows users, I suggest you use the term "folder" in the hint, instead of "directory". - Keith "Jonathan Turkanis" <technews@kangaroologic.com> wrote in message news:d7tci2$psq$1@sea.gmane.org...
Okay, I've tried to fix the problem. (I've learned not to say it's fixed, since I don't fully understand the build system).
Would you try to build again and see what happens?
Jonathan
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Keith MacDonald wrote:
Have you checked in the changed files, because the build still has the same problems?
The changes are apparently not yet available via anonymous CVS.
Incidentally, as this is mainly an issue for Windows users, I suggest you use the term "folder" in the hint, instead of "directory".
Good point, but I stole the language from John Maddock's regex warning: ****************************************************** Building Boost.Regex with Unicode/ICU support disabled. HINT: define the environment variable ICU_PATH to point to the root directy of your ICU installation if you have one. Couldn't find utypes.h in ****************************************************** Apparently I stole the typo, too ;-) I'd like to keep the bjam warnings consitent, if possible. Do you really think some windows developers won't know what a directory is? At any rate, I'd appreciate it if you'd try building Iostreams again when the changes show up in CVS. Jonathan
I wouldn't like to assume any level of knowledge about the file system by the average Windows user, but would doubt that such person had the competence to use Boost, if they didn't know what a directory is ;-) The hints now look correct, but the build with MSVC 8.0 fails with this error: F:\CVS\boost\tools/build/v1\boost-base.jam:1966: in subvariant-target *** argument error * rule library-file ( target : sources + ) * called with: ( <@boost!libs!iostreams!build\libboost_iostreams.lib\vc-8_0\debug\runtime-link-static>libboost_iostreams-vc80-sgd-1_33.lib : ) * missing argument sources F:\CVS\boost\tools/build/v1\boost-base.jam:119:see definition of rule 'library-file' being called F:\CVS\boost\tools/build/v1\boost-base.jam:2403: in stage Jamfile:195: in load-jamfiles F:\CVS\boost\tools\build\v1\bootstrap.jam:21: in boost-build F:\CVS\boost\boost-build.jam:16: in module scope I'm afraid it makes me none the wiser! - Keith "Jonathan Turkanis" <technews@kangaroologic.com> wrote in message news:d7u6t7$8gi$1@sea.gmane.org...
Keith MacDonald wrote:
Have you checked in the changed files, because the build still has the same problems?
The changes are apparently not yet available via anonymous CVS.
Incidentally, as this is mainly an issue for Windows users, I suggest you use the term "folder" in the hint, instead of "directory".
Good point, but I stole the language from John Maddock's regex warning:
******************************************************
Building Boost.Regex with Unicode/ICU support disabled. HINT: define the environment variable ICU_PATH to point to the root directy of your ICU installation if you have one. Couldn't find utypes.h in
******************************************************
Apparently I stole the typo, too ;-)
I'd like to keep the bjam warnings consitent, if possible. Do you really think some windows developers won't know what a directory is?
At any rate, I'd appreciate it if you'd try building Iostreams again when the changes show up in CVS.
Jonathan
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Building with missing header files for compression now works, thanks. However, there remains a problem when building boost_iostreams.dll, resulting in these warnings: iostreams/device/file_descriptor.hpp(96) : warning C4251: 'boost::iostreams::file_descriptor::pimpl_' : class 'boost::shared_ptr<T>' needs to have dll-interface to be used by clients of class 'boost::iostreams::file_descriptor' iostreams/device/mapped_file.hpp(135) : warning C4251: 'boost::iostreams::mapped_file_source::pimpl_' : class 'boost::shared_ptr<T>' needs to have dll-interface to be used by clients of class 'boost::iostreams::mapped_file_source' A similar warning occurs in filesystem/exception.hpp(97) for boost_filesystem.dll, so the problem may not be in your code. - Keith MacDonald "Jonathan Turkanis" <technews@kangaroologic.com> wrote in message news:d7u6t7$8gi$1@sea.gmane.org...
At any rate, I'd appreciate it if you'd try building Iostreams again when the changes show up in CVS.
Jonathan
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Keith MacDonald wrote:
Building with missing header files for compression now works, thanks.
Great! I was running out of ideas.
However, there remains a problem when building boost_iostreams.dll, resulting in these warnings:
iostreams/device/file_descriptor.hpp(96) : warning C4251: 'boost::iostreams::file_descriptor::pimpl_' : class 'boost::shared_ptr<T>' needs to have dll-interface to be used by clients of class 'boost::iostreams::file_descriptor' iostreams/device/mapped_file.hpp(135) : warning C4251: 'boost::iostreams::mapped_file_source::pimpl_' : class 'boost::shared_ptr<T>' needs to have dll-interface to be used by clients of class 'boost::iostreams::mapped_file_source'
A similar warning occurs in filesystem/exception.hpp(97) for boost_filesystem.dll, so the problem may not be in your code.
These warnings can be safely ignored, I think.
- Keith MacDonald
Jonathan
At 23:17 2005-06-04, Keith MacDonald wrote:
Have you checked in the changed files, because the build still has the same problems?
Incidentally, as this is mainly an issue for Windows users, I suggest you use the term "folder" in the hint, instead of "directory".
1) in the command shell the command is dir, not win to list the contents 2) you haven't said what you're building with 3) iostreams is buliding just fin on XP pro SP2 on both vc7.1 and vc8.0 on my machine
- Keith
"Jonathan Turkanis" <technews@kangaroologic.com> wrote in message news:d7tci2$psq$1@sea.gmane.org...
Okay, I've tried to fix the problem. (I've learned not to say it's fixed, since I don't fully understand the build system).
Would you try to build again and see what happens?
Jonathan
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"
participants (4)
-
Jonathan Turkanis -
Keith MacDonald -
Victor A. Wagner Jr.