[UTILITY][ANDROID] XZ Utils port to Android - managing .xz archives now possible!

[osm0sis]

If you wish to compile xz statically then the following example will do the trick. It's so SIMPLE I about fell out of my seat. Pay attention to what I have in bold:

./configure --build=arm --host=arm-linux-androideabi LDFLAGS="-static"

Then, when you go to run, make, just do the following:

make LDFLAGS=-all-static


Update:

After some tests with @osm0sis we learned that using configure will ultimately overwrite the original flags ordained by the source. Running the configure normally then applying your flags using "+=" will insure the ordained flags do not get overwritten as well as including your own additional flags. This will ultimately be up to the user what they want to do and their ultimate goal at the end of the day.

--- Happy Hunting!!

Can't wait to try that out in the morning. You've just fixed static NDK compiling on anything using Autotools, bro!

Let me know how it works out for you. I tried this method on my phone too and it worked like a champ

Yup works great! The key is this: You can't add -all-static via ./configure since it'll fail the working compiler test for some reason, but overriding the LDFLAGS on the make command-line works perfectly where even an exported environment variable doesn't. Stroke of genius to force a true static compile by @Modding.MyMind!

There's nothing important by default in the LDFLAGS so really all you need to worry about is overriding your own LDFLAGS you may have added with ./configure, and that can be resolved most definitely by adding them in on the make command-line as well (since my tests with += on Cygwin weren't successful). :good:

So to summarize, all you really need to do is:

./configure --host=<toolchain> --enable-static --disable-shared LDFLAGS=-static
cd src
make LDFLAGS=-all-static

(I've also got some workarounds in place to make it all work nicely on Cygwin, which can be found in my build script post.)

 

[Modding.MyMind]

Here is a true static compiled xz binary for arm. No dynamic links whatsoever and no tampering with the source let alone the toolchain. It's as legit as it can get. Figured I would share for any of those who need it. Based on version 5.0.5.

 

[SHM]

Yup works great! The key is this: You can't add -all-static via ./configure since it'll fail the working compiler test for some reason, but overriding the LDFLAGS on the make command-line works perfectly where even an exported environment variable doesn't. Stroke of genius to force a true static compile by @Modding.MyMind!

There's nothing important by default in the LDFLAGS so really all you need to worry about is overriding your own LDFLAGS you may have added with ./configure, and that can be resolved most definitely by adding them in on the make command-line as well (since my tests with += on Cygwin weren't successful). :good:

So to summarize, all you really need to do is:

./configure --host=<toolchain> --enable-static --disable-shared LDFLAGS=-static
cd src
make LDFLAGS=-all-static



(I've also got some workarounds in place to make it all work nicely on Cygwin, which can be found in my build script post.)

Been playing around with toolchains over the months and have learned a hard lesson lol. When compiling as static the target (compiler) will typically aim for the shared object first. Using "-static" forces the compiler to ignore any shared objects and go for static libs instead. However, if other resources being compiled within a some what complex program which causes confliction towards a static lib then it will ignore "-static" for that particular case and link to the shared object instead.

A little trick I starting using since I have no need for shared objects is adding an extended extension name to all the .so libs with ".keep" so while compiling statically I can hope to insure that all static libs are targeted.

 

[kdar1987]

Does anyone have port for pbzip2?

 

[SHM]

Does anyone have port for pbzip2?

Here you go.

Attachment removed. See further posts for the attachment.

 

[kdar1987]

Thanks a lot! I been looking for it for a while.

Just tried it.. but I am getting this error:

pbzip2: *ERROR: Can't setup signal handling [22]. Aborting!

 

[SHM]

Thanks a lot! I been looking for it for a while.

Just tried it.. but I am getting this error:

What command did you apply so that I may attempt to duplicate this same error on my end?

 

[kdar1987]

After I made it executable:

chmod 777 pbzip2

I tried several commands:

./pbzip2 input/stackoverflow.com.tar
./pbzip2 -fc input/stackoverflow.com.tar > /dev/null
./pbzip2 -dc bzip2.cfd/inputCRlow.9.tar.bz2 > /dev/null

I tried to run it on Cyanogenmod 12.1 on OnePlus One

 

[SHM]

After I made it executable:

chmod 777 pbzip2

I tried several commands:

./pbzip2 input/stackoverflow.com.tar
./pbzip2 -fc input/stackoverflow.com.tar > /dev/null
./pbzip2 -dc bzip2.cfd/inputCRlow.9.tar.bz2 > /dev/null

I tried to run it on Cyanogenmod 12.1 on OnePlus One

Ok, I see it on my end as well. Didn't test it prior to sharing. Since it's compiled for arm and Android isn't necessarily linux 100% I will have to make some modifications to the source and recompile. Looking into it now to see if this can be done successfully.

 

[SHM]

@kdar1987, Almost got it working. Still need to make some more modifications to the source. Will keep you posted and hopefully I can provide you with this tool.

 

[kdar1987]

Thank you!

 

[SHM]

Thank you!

It is working. However, due to it's coding it unfortunately requires root to work. So when you open up your terminal emulator make sure you type and enter, su, before calling on pbzip2, or else it will fail with three errors (though I could probably fix this lol).

Also, pbzip2 isn't actually bzip2. It just parallelizes bzip2. So, bzip2 must be installed on your device. I tested it with busybox bzip2 being installed and it worked great. Speed differences was amazing. However, busybox bzip2 sucks at compressing stuff. Even if the compression level is set to 9. Could be a bug though with busybox bzip2.

Oh, and one more thing, due to the toolchain I used, the "off_t variable" is only 32 bits in size so this means you can only compress stuff up to 2gb using pbzip2. Anything larger than 2 gigs will be a problem.

 

[SHM]

I have uploaded the original pbzip2 source as an attachment. The attachment also includes the prebuilt static arm binary.

 

[kdar1987]

Thank you a lot! It worked great. I will be using pbzip2 only from rooted adb, so its perfect.
I will check out git.

 

[SHM]

Thank you a lot! It worked great. I will be using pbzip2 only from rooted adb, so its perfect.
I will check out git.

Glad to here it. One thing I did but didn't notice anything unusual was me commenting out -lpthread since I do not have the static pthread library for my toolchain. However, the makefile still calls for -pthread for support. I'm working on cross compiling the pthread lib right now and then will rebuild pbzip2 to see if there is any differences but the pthread source is all jacked up. Not sure what these maintainers were thinking.

Also, I did notice that if you run pbzip2 without su that it will still work even though the three errors are displayed. I ran a check on the bz2 header of the compressed archive and the check returned ok. Must be a bug in the pbzip2 source. Anyways, enough jibberjabbing on my part lol. Glad it works for you.

 

[bdrew]

Download link broken....

what is XZ Utils
***LiNK BELOW IS BROKEN, any mirrors??***
Download

You may download lastest binaries for Android-ARM here :

XZ Utils 5.0.5 – ARM – Android[/URL