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

gollvm: missing kernel headers, broken build script for libffi on x86_64 Void Linux #43610

Open
advancedwebdeveloper opened this issue Jan 9, 2021 · 5 comments
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone

Comments

@advancedwebdeveloper
Copy link

Hello again.
I tried to build gollvm on another musl based Linux distro (additionally to Alpine).
https://www.reddit.com/r/voidlinux/comments/koyhl8/cant_compile_gollvm_on_void_linux/ - reported to the maintainers of Void Linux.
https://gist.github.com/advancedwebdeveloper/28e6c970c2c5301a1666435439312246 - here is the log.

libffi related stuff looks like this:

/home/oceanfish81/workarea/llvm-project/llvm/tools/gollvm/gofrontend/libgo/go/runtime/ffi.go:18:26: error: use of undefined type '__ffi_type'

You can check my compressed build folder
https://drive.google.com/file/d/1EwHPzIcrKFRTWPXEXJRz7yf-PfNRuQnE/view?usp=sharing

@advancedwebdeveloper
Copy link
Author

Sharing my compressed VDI (virtual storage device) file, for a VM:
https://drive.google.com/file/d/1g1-vTJ9PxjfSXhqBh613iXEChU3AxFL2/view?usp=sharing
. You can configure a VM, for it, and boot it.

@advancedwebdeveloper
Copy link
Author

@thanm, using Ninja was less desirable: it performed unnecessary re-compiling/re-linking, despite the presence of the build artifacts (which could be re-used).

https://www.reddit.com/r/voidlinux/comments/kq5gx8/ninja_1102_does_not_save_states_of_successfully/
ninja-build/ninja#1902

@cagedmantis cagedmantis added this to the Backlog milestone Jan 11, 2021
@cagedmantis cagedmantis added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jan 11, 2021
@cagedmantis
Copy link
Contributor

/cc @thanm @cherrymui

@thanm thanm modified the milestones: Backlog, gollvm Jan 11, 2021
@thanm thanm self-assigned this Jan 11, 2021
@thanm
Copy link
Contributor

thanm commented Jan 11, 2021

I can't really comment on the problems with ninja-- porting gollvm to a new build system is not something that I have time to tackle. Ninja is not perfect, but it's what we've got at the moment.

Regarding porting gollvm to musl-based systems, this is an interesting idea but like all ports it will require investigation and development work (it's not simply a question of the existing gollvm being "buggy").

@advancedwebdeveloper
Copy link
Author

I can't really comment on the problems with ninja-- porting gollvm to a new build system is not something that I have time to tackle. Ninja is not perfect, but it's what we've got at the moment.

@thanm, in such a situation you can help to resolve Ninja's issue. Of course I could re-run using Ninja, after everything would be OK under GNU make.
And I will report both summaries, of course.

Regarding porting gollvm to musl-based systems, this is an interesting idea but like all ports it will require investigation and development work (it's not simply a question of the existing gollvm being "buggy").

Let's get back to this, once you would submit a patch for sys.GoosIos

@rsc rsc unassigned thanm Jun 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Development

No branches or pull requests

3 participants