Thanks Adam, 
> I've put the revision of jpegv9a and it solved the problem of true and
> false. But now I'm having another problem. I compiled libtiff library and
> got this error message:
> 
> lib/contrib/contrib/dbs/tiff-bi.s.o: In function `main':
> /home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/dbs/tiff-bi.c:36:
> multiple definition of `main'
> lib/contrib/contrib/addtiffo/addtiffo.s.o:/home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/addtiffo/addtiffo.c:73:
> first defined here
> lib/contrib/contrib/dbs/tiff-grayscale.s.o: In function `main':
> /home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/dbs/tiff-grayscale.c:42:
> multiple definition of `main'
> lib/contrib/contrib/addtiffo/addtiffo.s.o:/home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/addtiffo/addtiffo.c:73:
> first defined here

I think you included too many files in your Makefile. libtiff also
contains programs (e.g. for testing purposes) which are not part of the
library itself. You must not include those when building the library.
Also, including files with 'win32' in the file name does not seem good
to me. I recommend to only include those files that are part of a
library build on Linux (display with "ar t libtiff.a").
After I ported libtiff library then I tried to compile simple tiff program, I found this error:

TLS definition in libuc_c.a(errno.o) section .tbss mismatches non-TLS reference in libtiff.so
libuc_c.a: could not read symbols: Bad value

What does it mean?

I found a solution for the problem which is similar to mine.

http://os.inf.tu-dresden.de/pipermail/l4-hackers/2006/002126.html
 
They said,"The errno.h file declares errno as global rather than per-thread, which is bogus on a TLS system. Official fix is to remove that errno.h file completely". But I don't know which errno.h that I should remove. Or maybe you have different solution for this problem?

Regards,
Irvanda