Boost C++ Libraries: Ticket #5725: Different ordering of includes can lead to compilation errors ( ‘SEEK_SET’ cannot appear in a constant-expression etc )

status changed; resolution set

Ion Gaztañaga — Sat, 24 Dec 2011 10:58:25 GMT

status new → closed
resolution → wontfix

I don't think it's an interprocess error. SEEK_SET is defined in <unistd.h> and Interprocess correctly includes it in os_file_functions.hpp. I don't know what do asio and mpi define to provoke the compilation error.

arandjelovic.relja@… — Sat, 24 Dec 2011 15:05:13 GMT

Hi,

This is the first time I submit a bug report so I'm not sure what should I do next. Should I switch the component to asio or mpi and reopen the ticket?

Thanks

Relja

Marshall Clow — Sat, 24 Dec 2011 16:59:26 GMT

Reija -- I think you should spend a bit more time investigating.

What does including ASIO bring to the table - why does it fail when you include ASIO (and not when you don't)?
Also, what version of Boost are you using?

The code the compiler is whining about is:

typedef enum { file_begin     = SEEK_SET
             , file_end       = SEEK_END
             , file_current   = SEEK_CUR
             } file_pos_t;

which (given sane values for SEEK_SET, etc) looks fine to me. What's the definition of SEEK_SET, etc on your machine?

Here's the one from my (Mac):

$ grep SEEK_SET /usr/include/stdio.h
#ifndef SEEK_SET
#define	SEEK_SET	0	/* set file offset to offset */

I'm also wondering about this define in mph/config.h:

/* Force MPICH not to define SEEK_SET, SEEK_CUR, and SEEK_END, which
   conflict with the versions in <stdio.h> and <cstdio>. */
#define MPICH_IGNORE_CXX_SEEK 1