RE: Compiling on Synology

["Arun Pillai" <aspillai@gmail.com>]

Hi Graham,

Thank you for your help.  

It's odd - I've confirmed that I have /lib/liblzma.so.5 in my path.
Regardless, I tried the options you provided and got further.  Now I have
this error:

./conftest: error while loading shared libraries: /lib/libcrypto.so.1.0.0:
internal error

Again, I've confirmed that /lib/libcrypto.so.1.0.0 exists.

Any ideas?

Thank you.

Arun.

-----Original Message-----
From: Graham Percival [mailto:gperciva@tarsnap.com] 
Sent: June-09-16 1:03 PM
To: Arun Pillai <aspillai@gmail.com>
Cc: tarsnap-users@tarsnap.com
Subject: Re: Compiling on Synology

On Tue, Jun 07, 2016 at 08:12:56AM -0400, Arun Pillai wrote:
> I've just been introduced to Tarsnap and find it perfectly fits what 
> I'm looking for.  Ideally, I would like to install Tarsnap on my 
> Synology DS414 Network Access Storage.
> 
> I started working on this yesterday but ran into a compile issue.

I think the most relevant lines from your config.log are:

configure:7121: checking size of wchar_t
configure:7126: gcc -o conftest -O2 -pipe -march=armv7-a
-mtune=cortex-a9 -fno-caller-saves -mfloat-abi=soft -static-libgcc
-Wl,-rpath=/opt/lib -Wl,--dynamic-linker=/opt/lib/ld-linux.so.3
-L/opt/lib conftest.c -llzma -lbz2 -lcrypto -lz -lrt  >&5
configure:7126: $? = 0
configure:7126: ./conftest
./conftest: error while loading shared libraries:
/lib/liblzma.so.5: internal error
configure:7126: $? = 127
configure: program exited with status 127


For reference, here's what mine look like (admittely on a simple
amd64 CPU):
configure:7121: checking size of wchar_t

configure:7126: gcc -o conftest -g -O2   conftest.c -lbz2 -lcrypto
-lz -lrt  >&5

configure:7126: $? = 0

configure:7126: ./conftest

configure:7126: $? = 0

configure:7140: result: 4


The configure script doesn't need lzma to do this test, and clearly
something weird is happening since you got an "internal error" in that
library.  Maybe it's a "static gcc vs. dynamic library" thing?  (note: I've
never tried cross-compiling, so perhaps this wild guess is completely wrong)

Still, I suggest trying:
    ./configure --without-lzmadec --without-lzma and see what happens.

Cheers,
- Graham