Bug#749944: build ogre-1.9 against new boost-defaults 1.55?

2014-06-25 Thread Manuel A. Fernandez Montecelo
Control: forwarded -1 https://ogre3d.atlassian.net/browse/OGRE-420 2014-06-13 6:21 GMT+01:00 Scott Howard showard...@gmail.com: block 744171 by 749944 thanks On Sun, Jun 1, 2014 at 12:29 PM, Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote: I don't know if I mention this to

Bug#749944: build ogre-1.9 against new boost-defaults 1.55?

2014-06-12 Thread Scott Howard
block 744171 by 749944 thanks On Sun, Jun 1, 2014 at 12:29 PM, Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote: I don't know if I mention this to them in the past. It happened in a time when development was not very active and the old leader had to retire for some reason, I

Bug#749944: build ogre-1.9 against new boost-defaults 1.55?

2014-06-01 Thread Manuel A. Fernandez Montecelo
2014-05-31 16:30 GMT+01:00 Scott Howard showard...@gmail.com: Thanks for all the info, sorry to make you spend time rehashing this! For my own sanity, I'll try to summarize the technical problem: It looks like the troublesome functions are defined in headers [1], so ogre gets the definitions

Bug#749944: build ogre-1.9 against new boost-defaults 1.55?

2014-05-31 Thread Manuel A. Fernandez Montecelo
2014-05-31 2:06 GMT+01:00 Scott Howard showard...@gmail.com: reopen 749944 On Fri, May 30, 2014 at 7:50 PM, Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote: 2014-05-31 0:18 GMT+01:00 Scott Howard showard...@gmail.com: On Fri, May 30, 2014 at 4:46 PM, Manuel A. Fernandez

Bug#749944: build ogre-1.9 against new boost-defaults 1.55?

2014-05-31 Thread Scott Howard
Thanks for all the info, sorry to make you spend time rehashing this! For my own sanity, I'll try to summarize the technical problem: It looks like the troublesome functions are defined in headers [1], so ogre gets the definitions hardcoded if it pulls in the headers. Those functions are now

Bug#749944: build ogre-1.9 against new boost-defaults 1.55?

2014-05-30 Thread Scott Howard
Source: ogre-1.9 Severity: wishlist Hello, Ogre-1.9 builds against boost 1.54. Debian just bumped boost-defaults to 1.55. Is it possible to bump debian/control BDs such that it builds against libboost-dev instead of libboost1.54-dev? It will make future transitions easier. Thank you.

Bug#749944: build ogre-1.9 against new boost-defaults 1.55?

2014-05-30 Thread Manuel A. Fernandez Montecelo
2014-05-30 20:39 GMT+01:00 Scott Howard showard...@gmail.com: Source: ogre-1.9 Severity: wishlist Hello, Ogre-1.9 builds against boost 1.54. Debian just bumped boost-defaults to 1.55. Is it possible to bump debian/control BDs such that it builds against libboost-dev instead of

Bug#749944: build ogre-1.9 against new boost-defaults 1.55?

2014-05-30 Thread Manuel A. Fernandez Montecelo
2014-05-31 0:18 GMT+01:00 Scott Howard showard...@gmail.com: On Fri, May 30, 2014 at 4:46 PM, Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote: The versions are hardcoded to force reverse build-depends using the same versions, due to problems in the past (incompatibilities

Bug#749944: build ogre-1.9 against new boost-defaults 1.55?

2014-05-30 Thread Scott Howard
reopen 749944 On Fri, May 30, 2014 at 7:50 PM, Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote: 2014-05-31 0:18 GMT+01:00 Scott Howard showard...@gmail.com: On Fri, May 30, 2014 at 4:46 PM, Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote: The versions are

Bug#749944: build ogre-1.9 against new boost-defaults 1.55?

2014-05-30 Thread Scott Howard
On Fri, May 30, 2014 at 9:06 PM, Scott Howard showard...@gmail.com wrote: You can reduce the effects of that breakage by build-depending on libboost-dev, thus forcing those users to also upgrade their code/compilation to the new versions of boost as well. typo: you can reduce the effects of