[Boost-bugs] [Boost C++ Libraries] #2958: [patch] changes to make asio compile on vxWorks

Subject: [Boost-bugs] [Boost C++ Libraries] #2958: [patch] changes to make asio compile on vxWorks
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2009-04-18 22:03:37

#2958: [patch] changes to make asio compile on vxWorks
 Reporter: Dustin Spicuzza <dustin_at_[hidden]> | Owner: chris_kohlhoff
     Type: Bugs | Status: new
Milestone: Boost 1.39.0 | Component: asio
  Version: Boost 1.38.0 | Severity: Problem
 Keywords: vxworks |
 An explanation of some of the changes:

 socket/pipe interrupter: Despite that vxWorks has a pipe facility, it
 appears that you must create a named pipe, and then open the file, which
 is a bit different than the unix pipe function. Since its not clear to me
 how many different interrupters may be created by asio, its far easier to
 use the select_interrupter instead (and it works just as well).

 socket_ops: for whatever reason the arguments to its socket related
 functions take an int, and a socklen_t is an unsigned int. there are also
 a number of functions where a non-const arg is passed that apparently is
 typically a const arg on other systems.

 socket_ops/descriptor_ops: when running as a kernel module, apparently
 open and ioctl have three fixed arguments, with the third argument being
 an integer. outside of kernel modules it appears to have the traditional

 Patch from ticket #2917 is required for vxWorks as well, since it does not
 support serial ports via termios.

 There are patches to other boost libraries required also, those have been
 submitted in other bugs.

Ticket URL: <https://svn.boost.org/trac/boost/ticket/2958>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:00 UTC