Library release build failure

[pbalduz]

I wrote a Vapor application which uses the library to parse routes and the parsing works nicely when debugging. Then I tried to deploy it to a hosting service (in this case I'm using Fly.io) but the build fails.

The deploy command runs the following command for the build:

swift build -c release --static-swift-stdlib -Xlinker -ljemalloc

Running it fails with the following error:

error: link command failed with exit code 1 (use -v to see invocation)
ld: library 'jemalloc' not found
clang: error: linker command failed with exit code 1 (use -v to see invocation)
error: fatalError

The problem comes with jemalloc because removing it and running swift build -c release --static-swift-stdlib builds fine but it seems to be necessary for the deploy to complete successfully. Is there a way to make the library build using it?

Thank you!

[mbrandonw]

Hi @pbalduz, are you sure the build is failing due to this library? The logs you shared do not mention this library, and our library certainly does not require jemalloc. Can you share a minimal project that reproduces the problem so that we can investigate?

[mbrandonw]

Can you try reproducing the problem using plain Swift tools? Have you tried building for release locally using swift build?

[pbalduz]

Yes I tried and it builds for swift build -c release --static-swift-stdlib but fails for swift build -c release --static-swift-stdlib -Xlinker -ljemalloc with the jemalloc error thing which can make sense since I may not have it locally installed.

When running it with Fly.io tools it does install it though because the Dockerfile specifies it (it includes apt-get install -y libjemalloc-dev) but in the process it prints the logs posted above and fails.

[mbrandonw]

Have you tried running docker locally so that you can install and use jemalloc?

[pbalduz]

No that I didn't, I will try.

Sorry if it's a bit off topic, it most probably has something to do with the whole configuration rather than the library but I couldn't find much useful info out there and decided to try here and see if it ringed someone's bell 🙂

[pbalduz]

Everything worked fine locally, there is no problem with the library. It seems the issue was related to cross-compiling on ARM for x86. I'll close the discussion since it is not related to the library.

Thanks for your time @mbrandonw !