Patches for OpenVMS support for Boost (Asio mostly)
Hello, I want to submit patches for Boost, mostly Asio for better support of OpenVMS IA64 for 32 and 64 bit builds. The fixes come from an organization I work for that prefers to stay anonymous for security reasons. We've mostly concerned about Boost.Asio and we've managed to compile and run all Boost.Asio unit tests actually giving VMS very good Asio support. The fixes cover several independent libraries that should be fixed in order to make them compile: - Boost.Asio - mostly, configuration and 64 bit quirks - Boost.Test - 64 bit issues and compiler issues. - Boost.Config - added new vms.hpp platform config. - Boost.DateTime - 64 bit fixes. - Boost.Thread - compiler issues workarounds. - Boost.Function - 64 bit fixes as sizeof(size_t) < sizeof(void *); I understand that many library maintainers should be involved in integration of these patch. And it is **very important** for the organization I work for to submit them to upstream Boost in order to make an upgrade to future Boost versions simpler. Questions: - How should I submit so wide patch that covers many libraries? Artyom. P.S.: The patch is attached.
On 7/27/2010 4:13 AM, Artyom wrote:
Questions:
- How should I submit so wide patch that covers many libraries?
Best might be to break the patch up on a per-library basis, then file tickets against each library and attach the appropriate patch to each ticket. That way the right person sees it. You can create tickets at http://svn.boost.org. Awesome work, thanks. -- Eric Niebler BoostPro Computing http://www.boostpro.com
----- Original Message ----
From: Eric Niebler <eric@boostpro.com> On 7/27/2010 4:13 AM, Artyom wrote:
Questions:
- How should I submit so wide patch that covers many libraries?
Best might be to break the patch up on a per-library basis, then file tickets against each library and attach the appropriate patch to each ticket. That way the right person sees it. You can create tickets at http://svn.boost.org.
Awesome work, thanks.
-- Eric Niebler
I've created 4 tickets: https://svn.boost.org/trac/boost/ticket/4473 to 4476 for asio, config, date_time, function But meanwhile my IP was banned for spam... I still need more 5 tickets for functional, smart_ptr, system, thread and test... Any workarounds or just wait? Artyom
On 7/27/2010 10:29 AM, Artyom wrote:
----- Original Message ----
From: Eric Niebler <eric@boostpro.com> On 7/27/2010 4:13 AM, Artyom wrote:
Questions:
- How should I submit so wide patch that covers many libraries?
Best might be to break the patch up on a per-library basis, then file tickets against each library and attach the appropriate patch to each ticket. That way the right person sees it. You can create tickets at http://svn.boost.org.
Awesome work, thanks.
I've created 4 tickets: https://svn.boost.org/trac/boost/ticket/4473 to 4476 for asio, config, date_time, function But meanwhile my IP was banned for spam... I still need more 5 tickets for functional, smart_ptr, system, thread and test...
Any workarounds or just wait?
Oh, good lord. Sorry for that. Rene? -- Eric Niebler BoostPro Computing http://www.boostpro.com
On 7/27/2010 10:03 AM, Eric Niebler wrote:
On 7/27/2010 10:29 AM, Artyom wrote:
----- Original Message ----
From: Eric Niebler<eric@boostpro.com> On 7/27/2010 4:13 AM, Artyom wrote:
Questions:
- How should I submit so wide patch that covers many libraries?
Best might be to break the patch up on a per-library basis, then file tickets against each library and attach the appropriate patch to each ticket. That way the right person sees it. You can create tickets at http://svn.boost.org.
Awesome work, thanks.
I've created 4 tickets: https://svn.boost.org/trac/boost/ticket/4473 to 4476 for asio, config, date_time, function But meanwhile my IP was banned for spam... I still need more 5 tickets for functional, smart_ptr, system, thread and test...
Any workarounds or just wait?
Oh, good lord. Sorry for that. Rene?
Basic option is to wait. But I marked the tickets as not-spam in the system. And increased the posts per hour limit. HTH. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
Thanks, I've managed to open all tickets I needed for all patches... So far 9. Artyom --- On Tue, 7/27/10, Rene Rivera <grafikrobot@gmail.com> wrote:
On 7/27/2010 10:29 AM, Artyom wrote:
----- Original Message ----
From: Eric Niebler<eric@boostpro.com> On 7/27/2010 4:13 AM, Artyom wrote:
Questions:
- How should I submit so wide patch
Best might be to break the patch up on a
tickets against each library and attach
From: Rene Rivera <grafikrobot@gmail.com> Subject: Re: [boost] [trac] this is NOT a spammer To: boost@lists.boost.org Date: Tuesday, July 27, 2010, 6:15 PM On 7/27/2010 10:03 AM, Eric Niebler wrote: that covers many libraries? per-library basis, then file the appropriate patch to each
ticket. That way the right person sees it. You can create tickets at http://svn.boost.org.
Awesome work, thanks.
I've created 4 tickets: https://svn.boost.org/trac/boost/ticket/4473 to 4476 for asio, config, date_time, function But meanwhile my IP was banned for spam... I still need more 5 tickets for functional, smart_ptr, system, thread and test...
Any workarounds or just wait?
Oh, good lord. Sorry for that. Rene?
Basic option is to wait. But I marked the tickets as not-spam in the system. And increased the posts per hour limit.
HTH.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Ok, Thanks... I divided all patches to parts according to libraries and opened tickets 4473 to 4481 with all patches. The fix of cstdint.hpp I've send to config "library", didn't find any specific library that is responsible for this, I hope this is correct. Artyom
- How should I submit so wide patch that covers many libraries?
Best might be to break the patch up on a per-library basis, then file tickets against each library and attach the appropriate patch to each ticket.
Eric Niebler
AMDG Artyom wrote:
Ok, Thanks...
I divided all patches to parts according to libraries and opened tickets 4473 to 4481 with all patches.
The fix of cstdint.hpp I've send to config "library", didn't find any specific library that is responsible for this,
Isn't there an Integer library? In Christ, Steven Watanabe
The fix of cstdint.hpp I've send to config "library", didn't find any specific library that is responsible for this,
Isn't there an Integer library?
In Christ, Steven Watanabe
Yes, you are right, Integer library is indeed responsible for cstdint.hpp (according to their docs). So I opened a separate ticket for integer with appropriate patch. Thanks, Artyom
Anybody? So far there is 9 opened tickets with patches but AFAIK nothing but small warning patch had been related so far. This is very important for us to get these patches upstream. Thanks, Artyom Beilis
On 7/30/2010 8:07 AM, Artyom wrote:
Anybody?
So far there is 9 opened tickets with patches but AFAIK nothing but small warning patch had been related so far.
This is very important for us to get these patches upstream.
Sometimes nagging the library maintainers directly has been known to help. But please keep in mind that most of us are volunteers here with other lives and other priorities. Please be patient. If you can't wait, you have 2 choices: 1) Create your own clone of the git mirror and apply your patches there. You'll be responsible for resolving future merge conflicts. Please don't claim such a patched repo is an official boost release since the patches have not been vetted by boost maintainers. This is currently what the users of the Boost.CMake build system are doing. 2) Professionally contract with BoostPro (see sig) to get your patches in, maintained and tested. -- Eric Niebler BoostPro Computing http://www.boostpro.com
participants (4)
-
Artyom -
Eric Niebler -
Rene Rivera -
Steven Watanabe