search

xinxinlx / openjpeg

Automatically exported from code.google.com/p/openjpeg
Other
0 stars 0 forks source link

Minimal patch for openjpeg-1.5.x II #304

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
No, the issue is NOT fixed in openjpeg-branch15-r2770 .
You have only placed your beloved OPJ_BIG_ENDIAN in 'convert.c'.

-------------------------------------------------------------------
#ifndef WORDS_BIGENDIAN
#ifdef WORDS_BIGENDIAN
#ifndef WORDS_BIGENDIAN
#ifdef WORDS_BIGENDIAN
#ifdef WORDS_BIGENDIAN
./thirdparty/libtiff/tif_open.c

#if WORDS_BIGENDIAN
#if WORDS_BIGENDIAN
./thirdparty/libtiff/tif_predict.c

/* #undef WORDS_BIGENDIAN */
./thirdparty/libtiff/tif_config.h

#if defined(_HOST_BIG_ENDIAN) || defined(__BIG_ENDIAN__) || 
defined(WORDS_BIGENDIAN)
./thirdparty/liblcms2/include/lcms2.h
-------------------------------------------------------------------
I have now tried to compile openjpeg-branch15-r2770 on a G5 machine.
It runs DEBIAN wheezy.

PROBLEM 4: CMAKE version 2.8.7
===============================
/usr/bin/ld: ../../../bin/libopenjpip_server.a(auxtrans_manager.c.o): undefined 
reference to symbol 'pthread_create@@GLIBC_2.1'
/usr/bin/ld: note: 'pthread_create@@GLIBC_2.1' is defined in DSO 
/lib/powerpc-linux-gnu/libpthread.so.0 so try adding it to the linker command 
line
/lib/powerpc-linux-gnu/libpthread.so.0: could not read symbols: Invalid 
operation
-------------------------------------------------------------------
PROBLEM 5: CONFIGURE and Makefile.am:
=====================================
With the manually repaired 'opj_config.h' for CONFIGURE:

/usr/bin/ld: JPWL_image_to_j2k-index.o: undefined reference to symbol 
'pow@@GLIBC_2.0'
/usr/bin/ld: note: 'pow@@GLIBC_2.0' is defined in DSO 
/lib/powerpc-linux-gnu/libm.so.6 so try adding it to the linker command line
/lib/powerpc-linux-gnu/libm.so.6: could not read symbols: Invalid operation
-------------------------------------------------------------------

The patch is attached.

winfried

Original issue reported on code.google.com by szukw...@arcor.de on 19 Mar 2014 at 9:13

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by mathieu.malaterre on 19 Mar 2014 at 12:57

GoogleCodeExporter commented 9 years ago

Original comment by mathieu.malaterre on 25 Mar 2014 at 1:21

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r2800.

Original comment by mathieu.malaterre on 25 Mar 2014 at 4:42