You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, thanks for the awesome tool, I originally looked at undocked.py but the Go implementation looks more elaborate and can be installed with a single executable, which is nice.
I have a small feature request that would make a huge difference: I am working on using docker images to produce sysroots meant for cross-compilation outside of a docker container. The main issue I encounter when using the "raw" docker container contents are absolute symlinks that can point to invalid locations on the build host, while they really should be pointing inside the sysroot directory.
One instance of such a problem I encountered is with libgcc_s.so which can often be a symlink to the real .so, unfortunately often set with an absolute path:
In the above example, the 32-bit ubuntu sysroot has a libgcc_s.so symlink to '/lib/i386-linux-gnu/libgcc_s.so.1', which obviously makes no sense when outside of the container. Replacing the symlink by '../../../../../lib/i386-linux-gnu/libgcc_s.so.1' (relative) fixes the symlink such that it can point to the right location again.
The Dockerfile I used for this example is simple, it's just an ubuntu environment with a few development packages:
First, thanks for the awesome tool, I originally looked at undocked.py but the Go implementation looks more elaborate and can be installed with a single executable, which is nice.
I have a small feature request that would make a huge difference: I am working on using docker images to produce sysroots meant for cross-compilation outside of a docker container. The main issue I encounter when using the "raw" docker container contents are absolute symlinks that can point to invalid locations on the build host, while they really should be pointing inside the sysroot directory.
One instance of such a problem I encountered is with libgcc_s.so which can often be a symlink to the real .so, unfortunately often set with an absolute path:
In the above example, the 32-bit ubuntu sysroot has a libgcc_s.so symlink to '/lib/i386-linux-gnu/libgcc_s.so.1', which obviously makes no sense when outside of the container. Replacing the symlink by '../../../../../lib/i386-linux-gnu/libgcc_s.so.1' (relative) fixes the symlink such that it can point to the right location again.
The Dockerfile I used for this example is simple, it's just an ubuntu environment with a few development packages:
I then built and extracted its contents this way:
Let me know if this could be done, thanks a lot!
The text was updated successfully, but these errors were encountered: