bug-ghostscript
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

minor compilation problems with 8.62.0 on MacOSX


From: Jim Reid
Subject: minor compilation problems with 8.62.0 on MacOSX
Date: Tue, 23 Sep 2008 18:54:41 +0100

Hi. There's a small compilation/configuration error with gnu- ghostscript-8.62.0 on MacOSX 10.5. Compilation of mkromfs fails because of a missing linker argument:

gcc -Wall -Wstrict-prototypes -Wundef -Wmissing-declarations -Wmissing- prototypes -Wwrite-strings -Wnostrict-aliasing -fno-builtin -fno- common -DHAVE_STDINT_H -DGX_COLOR_INDEX_TYPE="unsigned long long" - O2 -Wall -Wstrict-prototypes -Wundef -Wmissing-declarations -Wmissing- prototypes -Wwrite-strings -Wno-strict-aliasing -fno-builtin -fno- common -DHAVE_STDINT_H -DGX_COLOR_INDEX_TYPE="unsigned long long" - I./src -I./obj/ -Isrc ./src/mkromfs.c -o ./obj/mkromfs ./obj/ gscdefs.o ./obj/gsmisc.o ./obj/gpmisc.o ./obj/gslibctx.o ./obj/ gp_getnv.o ./obj/gp_unix.o ./obj/gp_unifs.o ./obj/gp_unifn.o ./obj/ gp_stdia.o ./obj/gsutil.o -lm -ldl -lm -liconv -lstdc++
./src/mkromfs.c: In function 'inode_write':
./src/mkromfs.c:287: warning: pointer targets in passing argument 2 of 'put_byte
s_padded' differ in signedness
Undefined symbols:
  "_compress", referenced from:
      _process_path in cckSTrxL.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make: *** [obj/mkromfs] Error 1

Rather than fight configure (:-() I just added a -lz argument to the compilation invocation and all went well. Perhaps this could be incorporated in a cleaner way in the next update?

BTW, I think it would be nice if you just bundled the jpeg and png libraries with the source distribution. There doesn't seem much point separating these. The code for these libraries is very stable (old?) so they might as well be included with the standard ghostscript build. Downloading these separately, unpacking them and then moving their source directories around to get a nice ghostscript build/install is a little annoying make-work. Is there some reason why these have deliberately been kept apart?






reply via email to

[Prev in Thread] Current Thread [Next in Thread]