Program headers not in the first page when trying to run on FreeBSD
See original GitHub issueProgram headers not in the first page
error message when trying to run the contents of extracted AppImages on FreeBSD.
https://github.com/AppImage/AppImageKit/issues/98#issuecomment-682099792
Same issue with the GCompris AppImage.
Interestingly, this error does not happen e.g., with the Akira AppImage that was made with go-appimage’s appimagetool -s deploy
: https://github.com/akiraux/Akira/issues/3#issuecomment-686786377
I don’t have any idea yet what may be causing this. Probably something related to the way the ingredients are compiled, or something about the systems/tools they are compiled on?
(May be useful for testing: https://www.nomadbsd.org/)
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
missing headers even they are present | The FreeBSD Forums
Salamo Alikom when i try a simple program that require headers from /usr/local/include i get error MSGS from compiler : curl.c:13:23: error: ...
Read more >HTTP::Headers(3) - FreeBSD
Get or set the value of one or more header fields. The header field name ($field) is not case sensitive. To make the...
Read more >elf - FreeBSD
The system loader treats them as a set of segments described by the program headers. The general format of an ELF file is...
Read more >Header Pages - FreeBSD Documentation
Why? Because the output filter is the only external program that will have control when the header page is printed that could do...
Read more >Chapter 2. Programming Tools | FreeBSD Documentation Portal
It does not attempt to describe coding in any detail. ... languages are the best way to start if you have not done...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m only patching the executable (not the libraries), maybe that’s why it doesn’t produce any issues.
The binaries ran well on FuryBSD after being patched, also they ran on all the docker containers.
Do you remember in which systems this used to happen?