2014.10.02 12:04 "[Tiff] Vulnerability CVE-2010-2596", by Petr Hracek

2014.10.07 23:35 "Re: [Tiff] build a static tiff2pdf", by Joel Costigliola

We are building different versions of tiff2pdf for different environments indeed.

Thx Bob

From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us> Sent: Wednesday, 8 October 2014 11:40 a.m.

To: Joel Costigliola
Cc: tiff@lists.maptools.org
Subject: Re: [Tiff] build a static tiff2pdf

On Tue, 7 Oct 2014, Joel Costigliola wrote:

So I just ran the link command manually adding the static option:

gcc -g -O2 -Wall -W -static -o tiff2pdf tiff2pdf.o ../libtiff/.libs/libtiff.a ../port/.libs/libport.a -ljpeg -lm /usr/local/lib/libjpeg.a

It's not the cleanest way of building a static binary but at least it worked.

Be aware that pure static executables are not necessarily portable to other systems. The C shared library interface is much more dependable than the raw system call interface used between the C library and the kernel.

Statically linking libjpeg should not be a problem. Statically linking libc is not a wise idea.