We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've just started using docker, on my mac, and am attempting to share "source trees", git checkouts, presumably all read only or read-mostly.
This pattern:
ls /s/emsdk/clang/e1.37.38_64bit/llc /s/emsdk/clang/e1.37.38_64bit/llc root@228e220e3562:/o/qt1# file /s/emsdk/clang/e1.37.38_64bit/llc /s/emsdk/clang/e1.37.38_64bit/llc: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=a08f1128d883a9ee1fb790e1b839b62348677478, not stripped root@228e220e3562:/o/qt1#
breaks me. Can you please put "linux" or "mac" or such in the paths?
I guess I'll make a new git clone per os.
The text was updated successfully, but these errors were encountered:
Merge pull request emscripten-core#142 from dotnet/darc-main-33115071…
64d5547
…-678b-4410-b56d-c2e28f3e4100 [main] Update dependencies from dotnet/arcade
No branches or pull requests
I've just started using docker, on my mac, and am attempting to share "source trees", git checkouts, presumably all read only or read-mostly.
This pattern:
ls /s/emsdk/clang/e1.37.38_64bit/llc
/s/emsdk/clang/e1.37.38_64bit/llc
root@228e220e3562:/o/qt1# file /s/emsdk/clang/e1.37.38_64bit/llc
/s/emsdk/clang/e1.37.38_64bit/llc: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=a08f1128d883a9ee1fb790e1b839b62348677478, not stripped
root@228e220e3562:/o/qt1#
breaks me. Can you please put "linux" or "mac" or such in the paths?
I guess I'll make a new git clone per os.
The text was updated successfully, but these errors were encountered: