You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildstream.apache.org by GitBox <gi...@apache.org> on 2022/02/18 18:36:47 UTC

[GitHub] [buildstream] abderrahim commented on pull request #1576: _sandboxbwrap.py: try to support architectures that don't match host

abderrahim commented on pull request #1576:
URL: https://github.com/apache/buildstream/pull/1576#issuecomment-1044982684


   I'm going to propose a similar thing for buildbox-run (possibly a little more sophisticated, by looking at what other container tools like flatpak and docker/podman do).
   
   That said, it is easier with bst2: We can use remote execution, by running a buildbox docker image of the architecture we want to build for. There is also a workaround we can use with bst2: we can build buildbox-run for the non-native architecture. It'll then think it is running on the correct architecture.  We can't do that with bst1 since it means compiling python for the non-native architecture, which will make bst very slow.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org