[GH-ISSUE #1042] Failed to find OpenSSL development headers. #467

Closed
opened 2026-02-28 14:49:20 +03:00 by kerem · 8 comments
Owner

Originally created by @kerbless on GitHub (Nov 9, 2022).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/1042

I'm trying to build from AUR, but makepkg runs into:

--- stderr
  thread 'main' panicked at '
  Header expansion error:
  Error { kind: ToolExecError, message: "Command \"cc\" \"-O3\" \"-ffunction-sections\" \"-fdata-sections\" \"-fPIC\" \"-m64\" \"-march=x86-64\" \"-mtune=generic\" \"-O2\" \"-pipe\" \"-fno-plt\" \"-fexceptions\" \"-Wp,-D_FORTIFY_SOURCE=2\" \"-Wformat\" \"-Werror=format-security\" \"-fstack-clash-protection\" \"-fcf-protection\" \"-I\" \"/usr/include\" \"-E\" \"build/expando.c\" with args \"cc\" did not execute successfully (status code exit status: 1)." }

  Failed to find OpenSSL development headers.

The arch wiki states:

On Arch Linux the OPENSSLDIR is /etc/ssl

But in my system I have:

/usr/bin/openssl
/usr/include/openssl

The openssl documentation states:

OPENSSL_LIB_DIR and OPENSSL_INCLUDE_DIR - If specified, the directories containing the OpenSSL libraries and headers respectively. This can be used if the OpenSSL installation is split in a nonstandard directory layout.

But setting those two environment variables respectively to /usr/bin/openssl and /usr/include/openssl doesn't change anything.

If this is not a spotify-tui issue, sorry.

Originally created by @kerbless on GitHub (Nov 9, 2022). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/1042 I'm trying to build from AUR, but `makepkg` runs into: ``` --- stderr thread 'main' panicked at ' Header expansion error: Error { kind: ToolExecError, message: "Command \"cc\" \"-O3\" \"-ffunction-sections\" \"-fdata-sections\" \"-fPIC\" \"-m64\" \"-march=x86-64\" \"-mtune=generic\" \"-O2\" \"-pipe\" \"-fno-plt\" \"-fexceptions\" \"-Wp,-D_FORTIFY_SOURCE=2\" \"-Wformat\" \"-Werror=format-security\" \"-fstack-clash-protection\" \"-fcf-protection\" \"-I\" \"/usr/include\" \"-E\" \"build/expando.c\" with args \"cc\" did not execute successfully (status code exit status: 1)." } Failed to find OpenSSL development headers. ``` The arch wiki states: > On Arch Linux the OPENSSLDIR is /etc/ssl But in my system I have: ``` /usr/bin/openssl /usr/include/openssl ``` The [openssl documentation](https://docs.rs/openssl/latest/openssl/) states: > OPENSSL_LIB_DIR and OPENSSL_INCLUDE_DIR - If specified, the directories containing the OpenSSL libraries and headers respectively. This can be used if the OpenSSL installation is split in a nonstandard directory layout. But setting those two environment variables respectively to `/usr/bin/openssl` and `/usr/include/openssl` doesn't change anything. If this is not a spotify-tui issue, sorry.
kerem closed this issue 2026-02-28 14:49:20 +03:00
Author
Owner

@lahwaacz commented on GitHub (Nov 10, 2022):

Arch Linux has recently upgraded to OpenSSL 3.0, see https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/IZT6ADWS5YUUNC7IFBUVYIB7O4QIJGZV/

<!-- gh-comment-id:1309854190 --> @lahwaacz commented on GitHub (Nov 10, 2022): Arch Linux has recently upgraded to OpenSSL 3.0, see https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/IZT6ADWS5YUUNC7IFBUVYIB7O4QIJGZV/
Author
Owner

@Quadrubo commented on GitHub (Nov 10, 2022):

I also encounter this problem, what do I have to do to fix this

<!-- gh-comment-id:1310188955 --> @Quadrubo commented on GitHub (Nov 10, 2022): I also encounter this problem, what do I have to do to fix this
Author
Owner

@maya-doshi commented on GitHub (Nov 10, 2022):

you can install the openssl-1.1 and openssl-1.0 packages along with the new one.

<!-- gh-comment-id:1310721436 --> @maya-doshi commented on GitHub (Nov 10, 2022): you can install the `openssl-1.1` and `openssl-1.0` packages along with the new one.
Author
Owner

@modMars commented on GitHub (Nov 13, 2022):

How to fix this issue?
I can't get the app to work :(.

<!-- gh-comment-id:1312639973 --> @modMars commented on GitHub (Nov 13, 2022): How to fix this issue? I can't get the app to work :(.
Author
Owner

@toh995 commented on GitHub (Nov 24, 2022):

Hi @kerbless I noticed you closed this issue. Would you be able to share with us what you did to make it work? 😅

<!-- gh-comment-id:1326061294 --> @toh995 commented on GitHub (Nov 24, 2022): Hi @kerbless I noticed you closed this issue. Would you be able to share with us what you did to make it work? :sweat_smile:
Author
Owner

@kerbless commented on GitHub (Nov 24, 2022):

Hi @toh995, I ended up installing the normal version of Spotify, I closed the issue because it's not an issue of spotify-tui but more about how you handle the openssl package.

you can install the openssl-1.1 and openssl-1.0 packages along with the new one.

Have you tried this?

<!-- gh-comment-id:1326841898 --> @kerbless commented on GitHub (Nov 24, 2022): Hi @toh995, I ended up installing the normal version of Spotify, I closed the issue because it's not an issue of spotify-tui but more about how you handle the openssl package. > you can install the `openssl-1.1` and `openssl-1.0` packages along with the new one. Have you tried this?
Author
Owner

@toh995 commented on GitHub (Nov 25, 2022):

Thanks for the response @kerbless!

Yes, I tried it, no luck. Also doing yay -S spotify doesn't work for me either - seems like the AUR package needs to be updated.

I guess I'll stick with the web client for now haha

<!-- gh-comment-id:1327838318 --> @toh995 commented on GitHub (Nov 25, 2022): Thanks for the response @kerbless! Yes, I tried it, no luck. Also doing `yay -S spotify` doesn't work for me either - seems like the AUR package needs to be updated. I guess I'll stick with the web client for now haha
Author
Owner

@mrtztg commented on GitHub (Nov 29, 2022):

I have the same problem. I installed openssl-1.1 and openssl-1.0. But still not success.

<!-- gh-comment-id:1330956859 --> @mrtztg commented on GitHub (Nov 29, 2022): I have the same problem. I installed `openssl-1.1` and `openssl-1.0`. But still not success.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify-tui#467
No description provided.