Compile error with initializers

[Mythli]

Hello,

Am I doing something wrong or why do I always get

boost/process/initializers/initializer_combination_category.hpp:29:60: error: no type named ‘combination_category’ in ‘const struct boost::process::posix::std_err_to_path’

bio::file_descriptor_sink log("log.txt");
bp::monitor child = bp::make_child
(
    bp::paths(this->cmdOptions->Executable),
    bp::std_err_to(log)
);

Any help would be really much appreciated. Tobias

[JeffFlinn]

boost/process/initializers/initializer_combination_category.hpp is not a file within boost::process. Are you using a modified version?

What version of boost are you using this with? Can you provide a complete and minimal example?

[JeffFlinn]

Did you find the solution? I see the Issue was marked closed on github. I added the following and reopened the issue there:

boost/process/initializers/initializer_combination_category.hpp is not a file within boost::process. Are you using a modified version?

What version of boost are you using this with? Can you provide a complete and minimal example?

Thanks, Jeff

On Fri, Aug 3, 2012 at 7:24 AM, Tobias < reply@reply.github.com

wrote:

Hello,

Am I doing something wrong or why do I always get

boost/process/initializers/initializer_combination_category.hpp:29:60:
error: no type named ‘combination_category’ in ‘const struct
boost::process::posix::std_err_to_path’

bio::file_descriptor_sink log("log.txt");
bp::monitor child = bp::make_child
(
        bp::paths(this->cmdOptions->Executable),
        bp::std_err_to(log)
);

Any help would be really much appreciated. Tobias

---

Reply to this email directly or view it on GitHub: https://github.com/JeffFlinn/boost-process/issues/2

[DannyHavenith]

combination_category looks like it is from my clone of the repository (DannyHavenith/boost-process). This may not be compatible with the latest changes in the original repository.

[Mythli]

Hello

Yes, I was using your version- switching back to JeffFlinn' s version resolved the issue. I should have added an explanation why I closed the issue. Keep up the good work! I apologize for the inconvenience and thank you for your patience.