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.

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

[Musl] chromium-based: perfetto build error #375

Open
Kawanaao opened this issue Sep 23, 2024 · 5 comments
Open

[Musl] chromium-based: perfetto build error #375

Kawanaao opened this issue Sep 23, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@Kawanaao
Copy link
Contributor

Kawanaao commented Sep 23, 2024

Hello!
I wanted to build for musl cromite and vscode, but I encountered a problem that perfetto in all packages related to chromium (cromite, electron) causes a compilation error related to the redefinition of structures from linux-headers, created an issue in perfetto, bug was fixed, but can this patch be applied to current versions of applications that use perfetto? Thanks!

@Kawanaao Kawanaao added the bug Something isn't working label Sep 23, 2024
@PF4Public
Copy link
Owner

but can this patch be applied to current versions of applications that use perfetto?

Have you tried? Unfortunately I don't have any system with musl.

@Kawanaao
Copy link
Contributor Author

Kawanaao commented Sep 23, 2024

but can this patch be applied to current versions of applications that use perfetto?

Have you tried? Unfortunately I don't have any system with musl.

I honestly can't understand where to insert the patch, perfetto remains uninitialized when cloning, where can apply it?

UPD: found where they are used, applied the patch and waiting for compilation

@Kawanaao
Copy link
Contributor Author

Yea, the patch helped, but apparently this requires a separate PR, since within the same perfetto, errors related to cdefs.h arose

@PF4Public
Copy link
Owner

I'd be happy to help if I knew how I could be of help :)

@Kawanaao
Copy link
Contributor Author

I'd be happy to help if I knew how I could be of help :)

hah, there is no limit to human hope ;)
hoped that if make the compiler think that it works on glibc via define __GLIBC__ then clang will somehow apply libc-compat and everything will be wonderful :h

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants