Skip to content

AIX build fix: Fix return type in get_invalid_systemwide_thread_id#280

Merged
igaztanaga merged 1 commit into
boostorg:developfrom
tkoecker-dt:aix-build-fix
Jun 26, 2026
Merged

AIX build fix: Fix return type in get_invalid_systemwide_thread_id#280
igaztanaga merged 1 commit into
boostorg:developfrom
tkoecker-dt:aix-build-fix

Conversation

@tkoecker-dt

Copy link
Copy Markdown
Contributor

The build fails on AIX with the following error:

include/boost/interprocess/detail/os_thread_functions.hpp: In function 'boost::interprocess::ipcdetail::OS_systemwide_thread_id_t boost::interprocess::ipcdetail::get_invalid_systemwide_thread_id()':
include/boost/interprocess/detail/os_thread_functions.hpp:375:12: error: 'thread_t' was not declared in this scope; did you mean 'boost::asio::execution::detail::mapping::thread_t'?
  375 | {  return (thread_t)(-1);  }
      |            ^~~~~~~~
      |            boost::asio::execution::detail::mapping::thread_t

It seems that this is caused by a copy paste error from the Solaris implementation in bfce9f1

The build fails on AIX with the following error:
```
include/boost/interprocess/detail/os_thread_functions.hpp: In function 'boost::interprocess::ipcdetail::OS_systemwide_thread_id_t boost::interprocess::ipcdetail::get_invalid_systemwide_thread_id()':
include/boost/interprocess/detail/os_thread_functions.hpp:375:12: error: 'thread_t' was not declared in this scope; did you mean 'boost::asio::execution::detail::mapping::thread_t'?
  375 | {  return (thread_t)(-1);  }
      |            ^~~~~~~~
      |            boost::asio::execution::detail::mapping::thread_t
```
It seems that this is caused by a copy paste error from the Solaris implementation in     
boostorg@bfce9f1
@igaztanaga igaztanaga merged commit 07e3095 into boostorg:develop Jun 26, 2026
@igaztanaga

Copy link
Copy Markdown
Member

Many thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants