mirror of
https://github.com/benbusby/whoogle-search.git
synced 2026-04-25 04:05:57 +03:00
[GH-ISSUE #117] [QUESTION] docker build on ARM #85
Labels
No labels
Fixed (Pending PR Merge)
Stale
bug
enhancement
enhancement
good first issue
help wanted
keep-open
needs more info
pull-request
question
theme
unfortunate
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/whoogle-search#85
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @itenmeer on GitHub (Aug 17, 2020).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/117
Hi,
didn't want to file a bug report for this, because I'm sure it is not a bug per se, but rather an issue relating to architecture.
I wanted to try whoogle on a Raspberry Pi, running Raspbian (an ARM version of Debian). I tried starting a Docker container, but that did not work because the code is compiled for x64, not ARM.
So then I tried a docker build (using the command as instructed on your webpage). That fails to build though. It fails trying to make _cffi_backend.o, because it cannot find the header file ffi.h.
I see that the -I for gcc is both /usr/include/ffi and /usr/include/libffi. I have libffi-dev installed, but both of those paths do not exist on my system. My system does have ffi.h, it's in /usr/include/arm-linux-gnueabihf/
So two questions:
Any hints are appreciated!
Thanks!
@benbusby commented on GitHub (Aug 20, 2020):
This issue of ARM build support came up originally in #21, and there are some comments in that PR that you may find helpful. All code changes from that review are available in the branch
feature/docker-updates.Let me know if that is helpful for you -- if you end up needing further assistance I'm happy to look into it a bit more in depth.
@benbusby commented on GitHub (Sep 4, 2020):
Closing for now, feel free to reopen if you still need assistance. I'll revisit this thread when that feature branch is merged into master.