appimageupdatetool does not work in systems without objdump about appimageupdate HOT 11 CLOSED

...or, even better, use my elf.c

from appimageupdate.

The issue has been corrected, thank you.

from appimageupdate.

As a workaround, please install objdump from your distribution.

from appimageupdate.

Actually, it should_ be bundled:

https://github.com/AppImage/AppImageUpdate/blob/65b152ef3c5737aa7bea24ccd350556482a5656d/resources/build-appimages.sh#L45

@TheAssassin please check

from appimageupdate.

@shacknetisp without telling us the version of appimageupdatetool and what OS you use, it's pretty impossible to debug this. You need to provide additional information. As @probonopd said, for quite some time, AppImageUpdate AppImages bundle objdump, so you're probably using an outdated version.
I'm kind of surprised you experience this specific issue.

The infinite hang shouldn't happen however. But that's another issue.

from appimageupdate.

The version is the latest in the release at time of writing, appimageupdatetool-167-65b152e-x86_64.AppImage

Operating Systems I tested were Ubuntu 16.04 (binutils were installed, but I reproduced the error when temporarily removing objdump) and Porteus XFCE 3.2.2 without binutils installed.

I made sure the appimageupdatetool included objdump by checking the squashfs-root/usr/bin/ directory resulting from --appimage-extract before reporting.

from appimageupdate.

@TheAssassin you are aware that there is no AppRun which would set the $PATH to include usr/bin?

from appimageupdate.

That means the bundled version isn't used. And I'm pretty certain I know why. I'll have to add some logic to call the bundled objdump specifically when running within an AppImage, and otherwise call the system wide (for development).

from appimageupdate.

I'm quick fixing it for now by adding this detection logic. I'll make this change eventually.

from appimageupdate.

@shacknetisp please retry with the latest version. Quickly tested insinde some fresh containers without a system wide objdump, works fine.

from appimageupdate.

You're welcome. Additional testers are always a plus.

By the way, since you might be interested in it, the self updating concept phase is ending in this sprint (ending next Wednesday...?), then we'll have an upstream solution for this. As of now, you can also just use libappimageupdate as-is for a more "native" look and feel. You're invited to keep track of #30.

from appimageupdate.