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

Error building Appimage after latest update #272

Open
namanlp opened this issue Feb 19, 2024 · 7 comments
Open

Error building Appimage after latest update #272

namanlp opened this issue Feb 19, 2024 · 7 comments

Comments

@namanlp
Copy link

namanlp commented Feb 19, 2024

Hi there!

After the latest Arch Linux package updates, the LinuxDeploy is having errors, and can't build at all. The error is as shown below

ERROR: Strip call failed: /tmp/appimage_extracted_0299051fc9707c0ee1f44f4a07981aee/usr/bin/strip: tauri-example.AppDir/usr/lib/libffi.so.8: unknown type [0x13] section `.relr.dyn'

/tmp/appimage_extracted_0299051fc9707c0ee1f44f4a07981aee/usr/bin/strip: Unable to recognise the format of the input file `tauri-example.AppDir/usr/lib/libffi.so.8'

And same errors for a couple of libraries, like libpango, libgstreamer , libgsttag , libgsttranscoder etc.

I have tried

  • Installing a new system and updating that.
  • Downgrading these packages fixes the issue.

Any insight on this issue?

@namanlp
Copy link
Author

namanlp commented Feb 19, 2024

Also, using NO_STRIP=true environment variable compiles fine without errors

@hdclark
Copy link
Contributor

hdclark commented Feb 20, 2024

Note this isn't strictly related to libffi.so.8, libpangoft2-1.0.so.0 has the same issue.

The current linuxdeploy CI release succeeds on Debian stable, but fails when stripping on Arch Linux.

hdclark pushed a commit to hdclark/DICOMautomaton that referenced this issue Feb 20, 2024
Found an upstream bug report. See linuxdeploy/linuxdeploy#272 for context.
@namanlp
Copy link
Author

namanlp commented Feb 21, 2024

Yeah, as I mentioned in the bug report itself, it is having issue with a bunch of libraries, so I guess it is issue with the LinuxDeploy itself.

Regarding Debian, it is not an issue right now, because the libraries are not updated for Debian yet. Downgrading only these libraries on Arch work fine as well. After a few weeks, the issue will be faced on Debian as well.

@vorporeal
Copy link
Contributor

Should linuxdeploy be using the host system's strip instead of a bundled one? If it's working with host system libraries, using a bundled strip (potentially from a different toolchain) is prone to issues like this.

@namanlp
Copy link
Author

namanlp commented Apr 9, 2024

YES!

@FrancoRATOVOSON
Copy link

Also, using NO_STRIP=true environment variable compiles fine without errors

Sorry, how do I use it ? Where do I put NO_STRIP=true ?

@hdclark
Copy link
Contributor

hdclark commented Apr 22, 2024

@FrancoRATOVOSON Define it as an environment variable before running linuxdeploy. Here is an example where I unpack the linuxdeploy AppImage and then define NO_STRIP as a temporary environment variable for the invocation: hdclark/DICOMautomaton@35d7c4c

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants