Opened 17 years ago

Closed 16 years ago

#404 closed Support Requests (Out of Date)

Building errors on windows with vc71stlport

Reported by: nobody Owned by: az_sw_dude
Milestone: Component: None
Version: None Severity:
Keywords: Cc:

Description

Hi,

I'm trying to install Boost on windows xp with stlport
and Visual Studio .Net 2003.  When building it with
"bjam "-sTOOLS=vc-7_1-stlport" install" I'm obtaining
errors that seems like:

c-C++
bin\boost\libs\date_time\build\boost_date_time.dll\vc-7_1-stlport\debug\threading-multi\greg_month.obj
greg_month.cpp
C:\Documents and
Settings\BOUJAC00\Bureau\boost_1_32_0\boost\lexical_cast.hpp(150)
: error C2679: binary '>>' : no operator found which
takes a right-hand operand of type
'boost::date_time::date_names_put<Config,charT,OutputIterator>::string_type'
(or there is no acceptable conversion)
        with
        [
            Config=boost::gregorian::greg_facet_config,
            charT=wchar_t,
           
OutputIterator=std::ostreambuf_iterator<wchar_t,std::char_traits<wchar_t>>
        ]


The log of the build is include in log2.txt.  Somebody
have an idea of what I'm doing wrong?

Thanks in advance
JA
jacques-andre.boulay@polymtl.ca

Change History (2)

comment:1 by az_sw_dude, 17 years ago

Logged In: YES 
user_id=579686

Stlport was not built with wchar_t support (this is the
default).

You have two choices to work around this issue.

You can rebuild stlport with wchar_t support by adding
/Zc:wchar_t to the
makefile and then build date_time with:
(from $boost_root)
bjam -a  "-sTOOLS=vc-7_1-stlport"  "-sSTLPORT_PATH=..."
     "-sBUILD=<native-wchar_t>on"
     --stagedir=... --with-date_time stage Or, you can build
date_time w/o
wstrings:bjam -a  "-sTOOLS=vc-7_1-stlport"  "-sSTLPORT_PATH=..."
     "-sBUILD=<define>BOOST_NO_STD_WSTRING"
     --stagedir=... --with-date_time stage(adjust the elipses
accordingly)

--as posted on list by Bart

Jeff

comment:2 by az_sw_dude, 16 years ago

Status: assignedclosed
Logged In: YES 
user_id=579686

Closing this old request out.  AFAIK the suggested
workaround was successful. 

Jeff
Note: See TracTickets for help on using tickets.