Compile error when building civetweb samples for posix_native #34226
Comments
|
Could this be related to the following topic #13054? Is it currently not possible to use POSIX subsytem for ARCH_POSIX? |
jukkar
added
area: Networking
area: civetweb
priority: low
|
Hello and thank you for your bug description. I think, that posix support for civetweb need to be rethinked. |
|
I must say it's been a while, and the civetweb module got pulled in during a very heated discussion on the POSIX APIs. I'm not very familiar with the current state of affairs in this topic. If what @mglettig mentions still holds, then it is definitely a relevant problem. And it does seem so from your log: So Civetweb relies on the POSIX_API, and I'm not aware if there is any "switch" that you can use to turn to native POSIX. If there's a "standard way of handling this", then it should not be very difficult to apply to Civetweb, the port is not very complex. I would assume that we'd need to adjust |
|
@Nukersson any updates on this? |
Some progress can be seen here: #34438 But I am not actively involved into it. Just monitoring and trying to help, where I can. At the end I can do the tests on my HW of course, before the merge can be done. Would you like to support? |
|
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
stephanosio
changed the title
|
Re-opening since this is still a valid issue. |
|
This is |
This code has gone unmaintained and bugs continue to be reported against it. We do not have the resources as a project to maintain this in "odd fixes" mode, and nobody has stepped up to maintain it [1], so sadly this must be removed for now. If anyone would like to see civetweb supported in upstream Zephyr again, they are welcome to add it back, as long as they promise to maintain it going forward. Many thanks to everyone who has contributed to civetweb support in Zephyr while it was here. So long and thanks for all the fish. Fixes: zephyrproject-rtos#45807 Fixes: zephyrproject-rtos#43910 Fixes: zephyrproject-rtos#34226 Fixes: zephyrproject-rtos#46743 [1] https://lists.zephyrproject.org/g/devel/message/8466 Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
This code has gone unmaintained and bugs continue to be reported against it. We do not have the resources as a project to maintain this in "odd fixes" mode, and nobody has stepped up to maintain it [1], so sadly this must be removed for now. If anyone would like to see civetweb supported in upstream Zephyr again, they are welcome to add it back, as long as they promise to maintain it going forward. Many thanks to everyone who has contributed to civetweb support in Zephyr while it was here. So long and thanks for all the fish. Fixes: #45807 Fixes: #43910 Fixes: #34226 Fixes: #46743 [1] https://lists.zephyrproject.org/g/devel/message/8466 Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
|
"Fixed" by the removal of civetweb. See #46746 for more details. Thanks for taking the time to file an issue and sorry for the inconvenience. |
Describe the bug
Using Zephyr 2.5.0 the build of civetweb http_server sample fails for the board posix_native. From the build logs it looks like an issue with conflicting types (useconds_t, pthread_t, pthread_mutexattr_t, pthread_condattr_t, ...)
To Reproduce
west build -b native_posix samples/net/civetweb/http_serverExpected behavior
The build should succeed.
Impact
For testing purposes it would be very convenient to run the webserver on x86. An alternative approach would be to use QEMU. But this doesn't work to to limited SRAM of qemu_cortex_m3.
Logs and console output
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: