Re: [Boost-users] Error:" Non-const function called for const object" on Sun CC while using boost::multi_index::multi_index_container

Subject: Re: [Boost-users] Error:" Non-const function called for const object" on Sun CC while using boost::multi_index::multi_index_container
From: Alexander Vinokur (Alexander.Vinokur_at_[hidden])
Date: 2008-10-16 02:17:32

Done.
Now it works fine.

% CC -m64 -library=stlport4 -I./boost_patch -I/home/BOOST/boost_1_34_0
foo1.cpp 

// No problem

Thanks,

Alex Vinokur

"JOAQUIN M. LOPEZ MU?OZ" <joaquin_at_[hidden]> wrote in message
news:<D1B8B06869125E44A4B33FF31CBAEA591187ADF181_at_EXCLU2K7.hi.inet>...
________________________________________
De: Alexander Vinokur [Alexander.Vinokur_at_[hidden]]
Enviado el: domingo, 12 de octubre de 2008 8:44
Para: boost-users_at_[hidden]
CC: JOAQUIN M. LOPEZ MU?OZ
Asunto: Re: Error:" Non-const function called for const object" on Sun
CC  =    while using boost::multi_index::multi_index_container
>
> Hi Joaqu?n,
>
> I was out of office several days. Sorry.
> So, I send my reply today.

No problem at all :)

> I don't have permissions to change something under /boost.

Maybe you can still perform the test by doing the following:

  1 Create a local folder structure more or less like this:

    ~alex/boost_patch/boost/detail

  and copy there the allocator_utilities.hpp modified file I sent you
previ=usly.

  2 When compiling your multi-index example add a compiler option (or
  IDE setting, etc.) so that ~alex/boost_patch/ is added to the list of
  include directories *and* takes precedence over the official copy of
Boos=.

If you finally manage to do the test please report back your results.

> But here other test I did:
[example core snipped]

I take this a sufficient evidence that the patch should work, so I went
ahe=d
and added it to the trunk:

  http://svn.boost.org/trac/boost/changeset/49289

If nothing wrong happens with the patch, it'll be shipped with Boost
1.38.

Joaqu?n M L?pez Mu?oz
Telef?nica, Investigaci?n y Desarrollo

----------

This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp