Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Add the musl-g++ issue fix in the README.md file. #150

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add the musl-g++ issue fix in the README.md file. #150

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
34c2ea0
Add the musl-g++ issue fix in the README.md file.
iddm Sep 6, 2024
1029daa
Update README.md
iddm Nov 7, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,6 +165,38 @@ extern crate openssl;

This is true even if you connect without `sslmode=require`.

### ZeroMQ (ZMQ), unrar and some other crates issues with musl-g++

Sometimes, when building Rust projects with the musl environment, one may observe an error:

```
#10 365.1 Running `/volume/target/release/build/zmq-sys-5a9c7df2068dc61d/build-script-main`
#10 365.1 The following warnings were emitted during compilation:
#10 365.1
#10 365.1 warning: [email protected]: Compiler family detection failed due to error: ToolNotFound: Failed to find tool. Is `musl-g++` installed?
#10 365.1
#10 365.1 error: failed to run custom build command for `zmq-sys v0.12.0`
#10 365.2
#10 365.2 Caused by:
#10 365.2 process didn't exit successfully: `/volume/target/release/build/zmq-sys-5a9c7df2068dc61d/build-script-main` (exit status: 1)
```

To fix it, simply in your Dockerfile, before building, force the OS to use the `/usr/bin/musl-g++` instead of `/usr/bin/g++`. For example:

```
# Stage 1: Build the Rust executable
FROM clux/muslrust as builder

# Copy the source code into the container
COPY . .

# Build the statically-linked binary
RUN chown 777 -R `pwd` && \
chown -R $(id -u) . && \
ln -s /usr/bin/g++ /usr/bin/musl-g++ && \
cargp build --target=x86_64-unknown-linux-musl
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! There's a typo in cargo though

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the review! Should be fixed!

```

### Filesystem permissions on local builds

When building locally, the permissions of the musl parts of the `./target` artifacts dir will be owned by `root` and requires `sudo rm -rf target/` to clear. This is an [intended](https://github.com/clux/muslrust/issues/65) complexity tradeoff with user builds.
Expand Down