Issue 51397 - Update C++ Boost support to 1.33
Summary: Update C++ Boost support to 1.33
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: ooo
QA Contact: issues@api
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-30 09:27 UTC by Daniel Boelzle [:dbo]
Modified: 2013-02-24 21:08 UTC (History)
8 users (show)

See Also:
Issue Type: PATCH
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Adds support for boost 1.33. Compiling with older boost is also possible (71.54 KB, patch)
2006-02-26 10:50 UTC, moxfox
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this issue.
Description Daniel Boelzle [:dbo] 2005-06-30 09:27:23 UTC
.
Comment 1 Daniel Boelzle [:dbo] 2006-01-11 11:43:07 UTC
cancelled for now.
Comment 2 jjmckenzie 2006-02-07 03:27:29 UTC
Why did you cancel this issue?

James
Comment 3 Daniel Boelzle [:dbo] 2006-02-07 08:45:53 UTC
@James: because the current SunCC Solaris compiler does (at least) not work with
the current spirit inside boost.  And, there is currently little demand for
further boost features.
But IMO we have to update our boost in the future, getting fixes in.
Comment 4 Daniel Boelzle [:dbo] 2006-02-20 14:57:52 UTC
reopening.
Comment 5 Daniel Boelzle [:dbo] 2006-02-20 14:59:06 UTC
you wanted it, you get it.
Comment 6 jjmckenzie 2006-02-20 17:55:50 UTC
jjmckenzie -> dbo

Thank you.  Is boost actually required for Solaris builds?  If so, I suggest
that we (and I mean we) look at moving to spirit 1.6.3 rather than 1.8.3 (which
I think is the included spirit with boost) if possible.  I might be able to get
ahold of a Sun system to do a build on, but that depends on what my employer
says.  I am a Solaris administrator in real life, but this position is very
unsteady at the present time.

James
Comment 7 Daniel Boelzle [:dbo] 2006-02-21 08:43:38 UTC
@jjmckenzie: the whole stuff must compile on Solaris SunPRO CC, of course.
Whether we have to stick to spirit 1.6.3 or can use boost's 1.8.3 is still open;
AFAIK there are newer CC versions which ought to be evaluated, and we stay in
contact with CC developers.
Finally, thank you for your offer, but we have lots of Sun systems we can use
for testing.
Comment 8 moxfox 2006-02-21 19:41:52 UTC
Hmm. So actually we should only need just boost (that includes spirit) rather
than have both of them?

If there is no SUN cc compilation problems with boost 1.33 et al., I think this
would be a good small way to reduce the complexity the OOo build has. 

Trying to build now on Mac OS X with boost 1.33 + spirit 1.6.3. The downloaded
files were: http://mesh.dl.sourceforge.net/sourceforge/boost/boost_1_33_1.tar.gz
and http://mesh.dl.sourceforge.net/sourceforge/spirit/spirit-1.6.3.tgz

applied the patch in issue 60951. Note that the spirit -package have to be
repackaged so that in unpacks to "spirit-1.6.3" (as is the default), and not
"boost".
Comment 9 moxfox 2006-02-26 10:50:54 UTC
Created attachment 34455 [details]
Adds support for boost 1.33. Compiling with older boost is also possible
Comment 10 moxfox 2006-02-26 11:04:01 UTC
With the above patch, you need to download
http://mesh.dl.sourceforge.net/sourceforge/boost/boost_1_33_1.tar.gz and put it
to boost/download/

NOTE: when compiling with boost 1.33.1, there is no need for separate spirit
-package, because the spirit (1.80) within boost is used.

The patch enables boost 1.33.1 by default for all archs except CC on Solaris.

I have tested a complete build with 1.33.1 and it both builds and runs fine.

any willing testers for others archs?
Comment 11 jjmckenzie 2006-02-26 15:05:14 UTC
jjmckenzie -> mox

The problem is that the Sun CC compiler is not compatible with the 1.33.1
version of boost.  I can try to get some time on a Sun computer to see what can
be done to look at this.  Otherwise, could one of the folks who have a Sun
system at home look at this patch and the boost 1.33.1 issue.

James
Comment 12 moxfox 2006-02-26 17:56:12 UTC
James: please read my message carefully before writing. 

I am aware that Solaris CC has problems with boost 1.33.1. The patch I posted
uses the old boost and spirit for that compiler.
Comment 13 jjmckenzie 2006-03-02 00:42:37 UTC
*** Issue 60951 has been marked as a duplicate of this issue. ***
Comment 14 jjmckenzie 2006-03-02 00:46:25 UTC
Closed issue 60951 as a duplicate of this issue as the resolution of that issue
is to upgrade to boost 1.33.1 which also eliminates the need to use the Spirit
libraries separately.  
Cannot build with boost 1.33.1 on Solaris 9 system as tcsh was removed and not
available.
Will do test build with the patch for QA, unless this patch is already
incorporated in pjanik's cws pj50.

Comment 15 ooo 2006-03-17 09:41:38 UTC
added Cc's
Comment 16 jjmckenzie 2006-03-17 11:33:16 UTC
Patch as proposed by Mox works on Mac OS X with gcc 3.3/XCode 2.2/Mac OS X
10.4.5.  Need test build on Solaris 8 or Solaris 9 to insure that boost
1.30.2/spirit 1.6.1 is selected vice boost 1.33.1.
Also needs to be tested on other major build systems.
pjanik will you do this?

James
Comment 17 pavel 2006-03-19 08:37:42 UTC
jjmckenzie: No. I consider this as lost time now. I'll do so once we decide to
update boost/spirit for all platforms.

We do not have enough knowledge/manpower to do complete QA and all tests now.
Comment 18 jjmckenzie 2006-04-28 03:53:49 UTC
Closing issue as won't fix for now.  Due to the conflict with Sun's CC and the
fact that a simple edit will clear the error message.  Will propose a change to
the current boost patch to clear the error message on MacOSX (and any other
system that uses gcc-4.0 or gcc-4.1 as they both compile the current version of
boost without errors.)

James
Comment 19 jjmckenzie 2006-04-28 03:54:41 UTC
Will reopen issue when Sun's CC will work with boost 1.33

James M.
Comment 20 jjmckenzie 2006-04-28 03:59:39 UTC
Cancelling cws boost 1331 as this issue is delayed.

James M.
Comment 21 ooo 2010-09-30 19:41:27 UTC
closed, since we are already on 1.39