Documentation | waf: Fix singlehtml output (!104)

[Frank Kuehndel (@frank_k)]

Frank Kuehndel commented on a discussion: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/104#note_119699


Thanks for looking into this issue.

I build the docs in a Podman container and if I do this manually, I use the Podman flags `-it`, i.e. stdin/-out/-err of the `bash` command in the container are connected to the terminal outside the container. Moreover, `-t` make it use a `tty`.

My CI job uses also a Podman container but has no stdin and redirects stdout/-err to a file - and it does not normally use a `tty`.

In general Podman containers do not throw away sdtin/-out/-err before the container terminates. If no `-i` flag is used, I guess the stdin/-out/-err of the process in the container is redirected to `/dev/null`.

I do not understand how all this affects `inliner` because its `stdout/-err` is redirected anyhow by the Python script running in the container. I can only guess that `inliner` needs a `tty` because it does some fancy progress output and needs to know the terminal capabilities for that.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/104#note_119699
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250211/286cff81/attachment-0001.htm>