Re: [Boost-users] Boost 1.34 and VC++ 64

From: Larry (lknain_at_[hidden])
Date: 2007-06-14 09:59:48

Your input for this problem helped my situation. I have MSVC 7.1 and 8 on my 
system and I tried to build with 7.1 (the only one in the path etc) but the 
libs got built and named as if they were built with 8. I was looking for an 
explanation but using your clue of msvc-7.1 for the toolset solved my 
problem. I did not see that particular item in the doc although it used to 
be that way in earlier Boost versions. Thanks.

Larry

"Christopher Lux" <christopherlux_at_[hidden]> wrote in message 
news:op.ttuowwb8o36c01_at_soddebecken.mshome.net...
> On Wed, 13 Jun 2007 06:03:42 +0200, Yutaka Leon Suematsu <yutaka_at_[hidden]> 
> wrote:
>
>> Hi boost users,
>>
>> I am trying to install Boost 1.34 in a Vista x64 (Core-duo) & VC++ 2005.
>> I could compile the x32 version without any problems.
>> But, when trying to compile the x64 version I have the popup message
>> "Windows cannot open this file  : execution_monitor.obj.rsp"
>> The command I used was:
>>
>> bjam --build-dir=C:\tmp\build-boost --toolset=msvc address-model=64
>> stage
>
> Hi,
> you have to use the 'Visual Studio x64 Win64 Command Prompt', so the 
> correct environment variables are set and then use bjam like:
>
> bjam --build-dir=C:\tmp\build-boost --toolset=msvc-8-0_64 stage
>
> HTH
>
> -chris
>
>> Any help would be highly appreciate,
>>
>> Yutaka Leon.
>>
>>
>>
>> On 2007/06/05, at 22:38, boost-users-request_at_[hidden] wrote:
>>
>>> Send Boost-users mailing list submissions to
>>> boost-users_at_[hidden]
>>>
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>> http://lists.boost.org/mailman/listinfo.cgi/boost-users
>>> or, via email, send a message with subject or body 'help' to
>>> boost-users-request_at_[hidden]
>>>
>>> You can reach the person managing the list at
>>> boost-users-owner_at_[hidden]
>>>
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of Boost-users digest..."
>>>
>>>
>>> Today's Topics:
>>>
>>>    1. Pb compiling spirit with Sun C++ 5.5 (Christophe Delarue)
>>>    2. program_options linking problem (Moritz Moeller)
>>>    3. Formatting and passing variable parameters.
>>>       (Prasanta K Chakravarty)
>>>    4. [serialization]: text (xml) iarchive - format options for
>>>       integers? (Frank Bergemann)
>>>    5. Re: [integer] Request: long long (64 bits) supportforint_t
>>>       and uint_t (me22)
>>>    6. lib folder? (Mike Wyatt)
>>>    7. Re: lib folder? (dhruva)
>>>    8. Re: Boost 1.34 and VC++ x64 (Andreas Fabri)
>>>
>>>
>>> ----------------------------------------------------------------------
>>>
>>> Message: 1
>>> Date: Tue, 5 Jun 2007 10:20:49 +0200
>>> From: "Christophe Delarue" <christophe.delarue_at_[hidden]>
>>> Subject: [Boost-users] Pb compiling spirit with Sun C++ 5.5
>>> To: boost-users_at_[hidden]
>>> Message-ID:
>>> <df19a5aa0706050120h1354f677yb7192b8cd8f78dba_at_[hidden]>
>>> Content-Type: text/plain; charset="iso-8859-1"
>>>
>>> HI boost users,
>>>
>>> We are trying to compile boost spirit to use the xml serialization,
>>> but we
>>> got compiler error on :
>>> CC -V
>>> CC: Sun C++ 5.5 2003/03/12
>>>
>>>
>>> + /Soft/sunstudio/8/bin/CC +d -g -xs -mt -DBOOST_ALL_DYN_LINK=1
>>> + -DBOOST_ALL_NO_LIB=1 -I. -I/Home/ut0bcm/Boost/boost_1_34_0
>>> + -I/Soft/sunstudio/8/prod/include/CC/stlport4 -I/usr/include
>>> + -library=stlport4 -c -o
>>> bin.v2/libs/wave/build/sun/debug/threading-multi/
>>> instantiate_cpp_exprgrammar.o
>>> libs/wave/src/instantiate_cpp_exprgrammar.cpp
>>>
>>> "./boost/spirit/phoenix/actor.hpp", line 345: Error: Could not find
>>> a match
>>> for phoenix::actor<phoenix::BaseT>::operator()(phoenix::A&) const.
>>> "./boost/spirit/phoenix/actor.hpp", line 354: Error: Could not find
>>> a match
>>> for phoenix::actor<phoenix::BaseT>::operator()(phoenix::A&,
>>> phoenix::B&)
>>> const.
>>> "./boost/spirit/phoenix/actor.hpp", line 354: Error: Too many args in
>>> template, from phoenix::B on ignored.
>>> "./boost/spirit/phoenix/actor.hpp", line 363: Error: Could not find
>>> a match
>>> for phoenix::actor<phoenix::BaseT>::operator()(phoenix::A&,
>>> phoenix::B&,
>>> phoenix::C&) const.
>>> "./boost/spirit/phoenix/actor.hpp", line 363: Error: Too many args in
>>> template, from phoenix::B on ignored.
>>> "./boost/spirit/phoenix/actor.hpp", line 373: Error: Could not find
>>> a match
>>> for phoenix::actor<phoenix::BaseT>::operator()(phoenix::A&,
>>> phoenix::B&,
>>> phoenix::C&, phoenix::D&) const.
>>> "./boost/spirit/phoenix/actor.hpp", line 373: Error: Too many args in
>>> template, from phoenix::B on ignored.
>>> "./boost/spirit/phoenix/actor.hpp", line 382: Error: Could not find
>>> a match
>>> for phoenix::actor<phoenix::BaseT>::operator()(phoenix::A&,
>>> phoenix::B&,
>>> phoenix::C&, phoenix::D&, phoenix::E&) const.
>>> "./boost/spirit/phoenix/actor.hpp", line 382: Error: Too many args in
>>> template, from phoenix::B on ignored.
>>> "./boost/spirit/phoenix/actor.hpp", line 397: Error: Could not find
>>> a match
>>> for phoenix::actor<phoenix::BaseT>::operator()(phoenix::A&,
>>> phoenix::B&,
>>> phoenix::C&, phoenix::D&, phoenix::E&, phoenix::F&) const.
>>> "./boost/spirit/phoenix/actor.hpp", line 397: Error: Too many args in
>>> template, from phoenix::B on ignored.
>>> "./boost/spirit/phoenix/actor.hpp", line 589: Error: Could not find
>>> a match
>>> for phoenix::actor<phoenix::BaseT>::operator()(const
>>> phoenix::unpack_tuple<phoenix::actor<phoenix::BaseT>::TupleT>&) const.
>>>
>>>
>>> --
>>> --
>>> Christophe Delarue
>>> mailto:christophe.delarue_at_[hidden]
>>> 06 12 95 49 56
>>> -------------- next part --------------
>>> HTML attachment scrubbed and removed
>>>
>>> ------------------------------
>>>
>>> Message: 2
>>> Date: Tue, 05 Jun 2007 12:59:27 +0100
>>> From: Moritz Moeller <mnm_at_[hidden]>
>>> Subject: [Boost-users] program_options linking problem
>>> To: boost-users_at_[hidden]
>>> Message-ID: <4665501F.7030607_at_[hidden]>
>>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>>
>>> I've got a linking issue with this lib on Linux. If I don't specify
>>> -lboost_program_options, I naturally get several pages of missing
>>> symbols. No surprise there.
>>>
>>> However, if I /do/ specify it, I still get /some/!?
>>>
>>>
>>> ______________________________________________________________________
>>> __________
>>> Creating bin/baker
>>> g++ obj/mesh.o obj/dnHumpBaker.o
>>> -L/hosts/norwich/user_data/ritz/usr/local/3delight-6.5.24/Linux-
>>> x86_64/lib
>>> -l3delight -lboost_program_options -o bin/baker
>>> obj/dnHumpBaker.o(.text+0xb84): In function `main':
>>> dnHumpBaker.cpp: undefined reference to
>>> `boost::program_options::options_description::options_description
>>> (std::basic_string<char,
>>> std::char_traits<char>, std::allocator<char> > const&, unsigned int)'
>>> obj/dnHumpBaker.o
>>> (.gnu.linkonce.t._ZN5boost15program_options25basic_command_line_parser
>>> IcE7optionsERKNS0_19options_descriptionE
>>> [boost::program_options::basic_command_line_parser<char>::options
>>> (boost::program_options::options_description
>>> const&)]+0x15): In function
>>> `boost::program_options::basic_command_line_parser<char>::options
>>> (boost::program_options::options_description
>>> const&)':
>>> dnHumpBaker.cpp: undefined reference to
>>> `boost::program_options::detail::cmdline::set_options_description
>>> (boost::program_options::options_description
>>> const&)'
>>> obj/dnHumpBaker.o
>>> (.gnu.linkonce.t._ZN5boost15program_options25basic_command_line_parser
>>> IcE10positionalERKNS0_30positional_options_descriptionE
>>> [boost::program_options::basic_command_line_parser<char>::positional
>>> (boost::program_options::positional_options_description
>>> const&)]+0x5): In function
>>> `boost::program_options::basic_command_line_parser<char>::positional
>>> (boost::program_options::positional_options_description
>>> const&)':
>>> dnHumpBaker.cpp: undefined reference to
>>> `boost::program_options::detail::cmdline::set_positional_options
>>> (boost::program_options::positional_options_description
>>> const&)'
>>> obj/dnHumpBaker.o
>>> (.gnu.linkonce.t._ZN5boost15program_options25basic_command_line_parser
>>> IcE3runEv
>>> [boost::program_options::basic_command_line_parser<char>::run()]
>>> +0x40):
>>> In function
>>> `boost::program_options::basic_command_line_parser<char>::run()':
>>> dnHumpBaker.cpp: undefined reference to
>>> `boost::program_options::detail::cmdline::run()'
>>> obj/dnHumpBaker.o
>>> (.gnu.linkonce.t._ZN5boost15program_options25basic_command_line_parser
>>> IcEC1EiPPc
>>> [boost::program_options::basic_command_line_parser<char>::basic_comman
>>> d_line_parser(int,
>>> char**)]+0x3e): In function
>>> `boost::program_options::basic_command_line_parser<char>::basic_comman
>>> d_line_parser(int,
>>> char**)':
>>> dnHumpBaker.cpp: undefined reference to
>>> `boost::program_options::detail::cmdline::cmdline
>>> (std::vector<std::basic_string<char,
>>> std::char_traits<char>, std::allocator<char> >,
>>> std::allocator<std::basic_string<char, std::char_traits<char>,
>>> std::allocator<char> > > > const&)'
>>> collect2: ld returned 1 exit status
>>> make: *** [baker] Error 1
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 3
>>> Date: Tue, 5 Jun 2007 11:18:48 +0530
>>> From: Prasanta K Chakravarty <prachakr_at_[hidden]>
>>> Subject: [Boost-users] Formatting and passing variable parameters.
>>> To: boost-users_at_[hidden]
>>> Message-ID:
>>> <OF271C97C8.3126C9FF-
>>> ON652572F1.001D5AD7-652572F1.001FC09A_at_[hidden]>
>>> Content-Type: text/plain; charset="us-ascii"
>>>
>>> Hi,
>>>
>>> 1) I have to generate unique id on the basis of file name and line
>>> no. For
>>> that I am using macros __FILE__ and __LINE__. But __FILE__ is
>>> giving full
>>> path with the file name and two double quotes at the begining and
>>> end(for
>>> example, "C:\Project\Test\log.cfg" ). I need to get the unique id
>>> in the
>>> format as <file name>_<line no>. For example if above is the file
>>> description and let line no is 11, then the unique id would be log_11.
>>> Please suggest.
>>> 2) I have to pass variable no of arguments in the macro. So, I want
>>> to use
>>> Boost PARAM macro. For example, if LIST is the macro name and I
>>> want to
>>> call it as LIST(MSG_ID, "good", 5, "failed", "50%", 10); Here
>>> parameters
>>> are of different types, only the fist parameter is fixed that is
>>> string
>>> type and always with same variable name. Other parameters will vary.
>>> Please help me out in making the macro with variable no. of
>>> parameters.
>>> Please suggest,
>>>
>>> Thanks Prasanta
>>> -------------- next part --------------
>>> HTML attachment scrubbed and removed
>>>
>>> ------------------------------
>>>
>>> Message: 4
>>> Date: Tue, 05 Jun 2007 14:40:49 +0200
>>> From: Frank Bergemann <FBergemann_at_[hidden]>
>>> Subject: [Boost-users] [serialization]: text (xml) iarchive - format
>>> options for integers?
>>> To: boost-users_at_[hidden]
>>> Message-ID: <119465730_at_[hidden]>
>>> Content-Type: text/plain; charset=iso-8859-15
>>>
>>> Hi,
>>> can i make xml_iarchive accept "0x11" instead of "17" for an int
>>> type data element?
>>> Or do i have to derive my own iarchive and implement that myself?
>>> \Frank
>>> _______________________________________________________________
>>> SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
>>> kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
>>>
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 5
>>> Date: Tue, 5 Jun 2007 08:58:05 -0400
>>> From: me22 <me22.ca_at_[hidden]>
>>> Subject: Re: [Boost-users] [integer] Request: long long (64 bits)
>>> supportforint_t and uint_t
>>> To: boost-users_at_[hidden]
>>> Message-ID:
>>> <fa28b9250706050558v7671106bj5a2f6add2ba79f3_at_[hidden]>
>>> Content-Type: text/plain; charset=UTF-8; format=flowed
>>>
>>> On 03/06/07, Niels Dekker - mail address until 2007-11-30 wrote:
>>>> Shams wrote:
>>>>> 1. With most (all?) 64-bit Linux/Unix following the LP64 model:
>>>>> http://www.unix.org/version2/whatsnew/lp64_wp.html
>>>>>
>>>>> int_t<64>::least could give either a "long" or "long long" .
>>>>> uint_t<64>::least could give either a "unsigned long" or
>>>>> "unsigned long long".
>>>>>
>>>>> In this case I'd prefer just "long" or "unsigned long".
>>>>
>>>> No problem, I guess.  I guess that after adding long-long-support,
>>>> int_t<64>::least would still select "long", rather than "long
>>>> long", on
>>>> a platform that has 64-bits "long" integers.
>>>>
>>> The current implementation method will give the potentially smaller of
>>> the 2 types, so int_t<64>::least would give long if longs and long
>>> longs are both 64-bits, just as it currently gives int for
>>> int_t<32>::least when long and int are both 32-bits.
>>>
>>> The implementation is quite ingenious, actually.  On a proverbial
>>> toaster with 42-bit everything, a request for int_t<39>::least would
>>> give a signed char, the "smallest" type.
>>>
>>>>> 2. However with M$ 64bit Windows following the ILP64 there is no
>>>>> other
>>>>> choice but int_t<64>::least gives "long" or "long long".
>>>>
>>>> Hmmm... I wasn't even aware of ILP64! Thanks! Does Boost support
>>>> ILP64
>>>> platforms?  If so, I guess int_t<32>::least should select _int32,
>>>> instead of int, on such a platform!
>>>>
>>> The current implementation deals only in standard C++98 types.
>>>
>>> Unfortunately, __int32 wouldn't fit in perfectly.  int could plausibly
>>> be 16 or 64 bits, so there's no way of knowing where in the ordering
>>> to put it.  Of course, some (rather reasonable) assumptions could be
>>> make about platforms that do provide it.
>>>
>>>>> 3. Now I remember someone already already come up with a patch?
>>>>
>>>> Apparently yes!  Just after posting my question, I found a ticket,
>>>> submitted by "me22" a year ago, and assigned to Daryle Walker:
>>>> Ticket #653, "[integer] add support for integers longer than long"
>>>> http://svn.boost.org/trac/boost/ticket/653
>>>>
>>> Apparently not everything got transitioned over to trac perfectly.  On
>>> SF it told you what this mysterious "me22"'s name was.
>>>
>>> You can still find the patch in the mailing list archives:
>>> http://lists.boost.org/Archives/boost/2006/06/106262.php
>>>
>>> Or, if you're a boost admin, at
>>> http://sourceforge.net/tracker/index.php?
>>> func=detail&aid=1507034&group_id=7586&atid=307586
>>>
>>> There was someone else who also offered a similar patch a few
>>> months back.
>>>
>>>> When would it be implemented within a Boost release version?
>>>>
>>> Hopefully soon :)
>>>
>>> My patch is nearing a year old, but with 1.34 out the door and the
>>> current push for more frequent releases, soon is plausible.
>>>
>>> ~ Scott McMurray
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 6
>>> Date: Tue, 5 Jun 2007 07:43:14 -0500
>>> From: "Mike Wyatt" <mikejohnwyatt_at_[hidden]>
>>> Subject: [Boost-users] lib folder?
>>> To: boost-users_at_[hidden]
>>> Message-ID:
>>> <140bcb8f0706050543m36ceba0fq4772518b80d6a74b_at_[hidden]>
>>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>>
>>> I just installed MinGW and Boost.  The boost_1_34_0 folder I extracted
>>> from the downloaded zip did not contain a "lib" folder, which is
>>> referred to in the Getting Started for Windows guide
>>> (http://www.boost.org/more/getting_started/windows.html).  I've
>>> already built all the Boost libraries, so I'm guessing that I need to
>>> copy the lib folder from the new stage folder into the boost root.  Is
>>> that correct?
>>>
>>> Also, I built bjam with the "mingw" toolset, and Boost with "gcc".  Is
>>> that a problem?  Here are the commands I ran:
>>>
>>> *Building bjam*: c:\Program Files\boost_1_34_0\tools\jam\src\build
>>> mingw
>>> *Building Boost*: c:\Program Files\boost_1_34_0\bjam --build-dir=build
>>> --toolset=gcc stage
>>>
>>> Does that make sense?  Am I doing everything right, so far?
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 7
>>> Date: Tue, 5 Jun 2007 19:05:36 +0530
>>> From: dhruva <dhruvakm_at_[hidden]>
>>> Subject: Re: [Boost-users] lib folder?
>>> To: boost-users_at_[hidden]
>>> Message-ID:
>>> <e3f230850706050635l7ac54163s186c6ae50da2b8af_at_[hidden]>
>>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>>
>>> Hi,
>>>
>>> On 6/5/07, Mike Wyatt <mikejohnwyatt_at_[hidden]> wrote:
>>>> *Building bjam*: c:\Program Files\boost_1_34_0\tools\jam\src\build
>>>> mingw
>>>> *Building Boost*: c:\Program Files\boost_1_34_0\bjam --build-
>>>> dir=build
>>>> --toolset=gcc stage
>>>
>>> I guess you also need to invoke "bjam --toolset=gcc
>>> --prefix=path/to/install/boost install" is required. I have done that
>>> building BOOST using VC71 on Windows. Since "bjam" is used, IMO, you
>>> need to do the same irrespective of the tool set.
>>>
>>> with best regards,
>>> dhruva
>>>
>>> --
>>> Dhruva Krishnamurthy
>>> Contents reflect my personal views only!
>>>
>>>
>>> ------------------------------
>>>
>>> Message: 8
>>> Date: Tue, 05 Jun 2007 15:38:25 +0200
>>> From: Andreas Fabri <andreas.fabri_at_[hidden]>
>>> Subject: Re: [Boost-users] Boost 1.34 and VC++ x64
>>> To: boost-users_at_[hidden]
>>> Message-ID: <46656751.4050302_at_[hidden]>
>>> Content-Type: text/plain; charset=UTF-8; format=flowed
>>>
>>> Vladimir Prus wrote:
>>>> Sebastian Pf?tzner wrote:
>>>>
>>>>> Juergen Hunold schrieb:
>>>>>> Could you please post your command line ? Maybe your build is
>>>>>> picking up
>>>>>> the 32bit version...
>>>>>> Those errors are impossible to debug without the _exact_ command
>>>>>> lines
>>>>>> executed (and response files on windows ...)
>>>>> Hello Juergen,
>>>>>
>>>>> thanks for your reply. I use the following command line to build the
>>>>> boost libraries:
>>>>>
>>>>> bjam --toolset=msvc --address-model=64 stage
>>>>
>>>> There's no such option "--address-model", please use:
>>>>
>>>>         bjam --toolset=msvc address-model=64 stage
>>>>
>>>> Incidentally, you're a second person that's confused,
>>>> I've raised issue on boost-build list about that.
>>>
>>> Hello,
>>>
>>> I tried what you said and get tons of warnings:
>>>
>>> compile-c-c++ bin.v2\libs\wave\build\msvc-8.0\debug\address-model-64
>>> \threading-m
>>> ulti\instantiate_cpp_exprgrammar.obj
>>> instantiate_cpp_exprgrammar.cpp
>>> .\boost/wave/util/flex_string.hpp(100) : warning C4103: 'c:\boost
>>> \boost_1_34_0\b
>>> oost\wave\util\flex_string.hpp' : alignment changed after including
>>> header, may
>>> be due to missing #pragma pack(pop)
>>>
>>> Can I simply ignore them?
>>>
>>> andreas
>>>
>>>
>>>
>>> ------------------------------
>>>
>>> _______________________________________________
>>> Boost-users mailing list
>>> Boost-users_at_[hidden]
>>> http://lists.boost.org/mailman/listinfo.cgi/boost-users
>>>
>>> End of Boost-users Digest, Vol 1289, Issue 2
>>> ********************************************
>>>
>>
>> _______________________________________________
>> Boost-users mailing list
>> Boost-users_at_[hidden]
>> http://lists.boost.org/mailman/listinfo.cgi/boost-users
>>
>
>
>
> -- 
> Christopher Lux |
>                 | Bauhaus University Weimar
>                 | Faculty of Media - Virtual Reality Systems Group