Some supplements about snzip

[kubo]

When libsnappy.so.1 is in /root/software/snappy/lib, snzip works fine because it is configured with --with-snappy=/root/software/snappy and it has a rpath attribute whose value is /root/software/snappy/lib.

$ wget https://github.com/kubo/snzip/files/2084488/snzip.tar.gz
$ tar xvfz snzip.tar.gz
$ readelf -d snzip/bin/snzip | grep RPATH
 0x000000000000000f (RPATH)              Library rpath: [/root/software/snappy/lib]

When libsnappy.so.1 is not found in /root/software/snappy/lib or standard shared library directories, snzip doesn't run. I don't think it is a problem related to snzip. It is by design.

Could you explain your request? I cannot understand 30 percents of characters in your Chinese comment. I guess that they are simplified characters used in China. Even when they have same shape, some of them have definitely different meanings. For example 后 in Japanese is the wife of a king and I don't think that you use it with such meaning. I guess that 安装 in Chinese is install, which is, however, インストール or 導入 in Japanese.

[kubo]

@Mr-Malone
Could you write it in English? I cannot read Chinese.

[x-otto-x]

Follow your steps to compile snzip, and some problems arise.

[x-otto-x]

Above are the steps I practiced and corrected.

[x-otto-x]

I agree with you

[x-otto-x]

There are some problems with your readme, because if you follow your steps to compile, there will be some problems. What I provide is the green version of snzip.I think you need the green version of snzip, and I hope you'll allow me to make some modifications to readme to perfect your project.

[kubo]

Could you summarize the problems? The procedures in README are fine for me. I'm using Ubuntu 16.04 x86_64.
One problem seems to be caused by autoconf version. It is worth to notice required autoconf version.
What are others?

[x-otto-x]

I'm using Centos6 x86_64.The problem I want to solve is that compiled software can be put anywhere, that is, green software.Not everyone has access to the server.Another point is that the software compiled according to your instructions is not available, and I want it to be friendlier and easier to use.

[kubo]

The problem I want to solve is that compiled software can be put anywhere, that is, green software. Not everyone has access to the server.

I have not heard green software. I googled with "green software" and cannot find such definition.
Well, I understand that some people need such software. However most linux programs are not designed to be what you say green software. So I have no will to change snzip if it isn't easy. Luckily for you, it is easy. Just linking with static version of snappy library. I'll add a new configure option --with-static-snappy which creates snzip including snappy library.

Another point is that the software compiled according to your instructions is not available, and I want it to be friendlier and easier to use.

Which do you say?

1. It is not available even on the machine where it was compiled.
2. It is not available as what you say green software.

If it is the former, I'll fix document. If the latter, I don't think that it is a problem.

[kubo]

I'll rewrite README.md to build with snappy 1.1.7. Autoconf build configuration had been deprecated since snappy 1.1.5 and was removed in snappy 1.1.7.

[x-otto-x]

That's the good news.
Green software is a special name in China.
portable application.

[kubo]

809c6f2 was committed. It adds --with-static-snappy configure option.
README.md has not been rewritten yet.

[x-otto-x]

Can I join the contributors?

[kubo]

Can I join the contributors?

What type of contributor do you want to become?