-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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.
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
Issues with "make install" #232
Comments
Hi, and thanks for your report! I believe the third issue has been fixed in the meanwhile: 52a5079 Regarding the first issue, would you be happy with an option such as Regarding second issue, this is a remainder of the time when we installed under both name (polarssl and mbedtls), I'll remove the PS: which name would you like us to use for attribution in the ChangeLog? |
Hi mpg, For attribution in the changelog, just use my username 👍 |
Hi, in the meantime I noticed we don't even need |
Make fixes related to using Mbed Crypto as a service
Hello mbed TLS developers,
I have experienced some issues with 'make install'.
no_test
target was specified earlier,make install
tries to build the test cases (because theinstall
target depends onall
):make no_test make install # tries to build test cases
busybox
asln
-implementation,make install
will create symbolic link loops for all binaries. From the Makefile (line 36 in mbedtls-2.0):From what I understand,
$$o
is always empty?(What happens is, that the binary gets overwritten by a symlink to itself!)
libmbedtls.a
file get copied.libmbedx509.a
andlibmbedcrypto.a
are missing. When compiling against libmbedtls.a alone, lots of undefined reference errors pop up - because these functions are in the other .a files, so we definitely need them.I've built mbedtls-2.0 on sabotage linux (my recipe with workarounds for these issues).
The text was updated successfully, but these errors were encountered: