[gs-bugs] [Bug 691312] New: './autogen "CC=gcc -m32" ; make' broken starting with r.11171

bugzilla-daemon at ghostscript.com bugzilla-daemon at ghostscript.com
Mon May 17 02:46:48 UTC 2010


http://bugs.ghostscript.com/show_bug.cgi?id=691312

           Summary: './autogen "CC=gcc -m32" ; make' broken starting with
                    r.11171
           Product: Ghostscript
           Version: HEAD
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P4
         Component: Build Process
        AssignedTo: hintak at ghostscript.com
        ReportedBy: marcos.woehrmann at artifex.com
         QAContact: gs-bugs at ghostscript.com
   Estimated Hours: 0.0


Starting with r11171 the command

  ./autogen "CC=gcc -m32" ; make

no longer works (with previous versions it builds a 32 bit version of
Ghostscript on 64 bit Linux boxes).

The error message produced is:

  gcc -m32  -DHAVE_MKSTEMP -DHAVE_HYPOT -DHAVE_FILE64 -DHAVE_MKSTEMP64
-DHAVE_FONTCONFIG -DHAVE_LIBIDN -DHAVE_SETLOCALE -O2 -Wall -Wstrict-prototypes
-Wundef -Wmissing-declarations -Wmissing-prototypes -Wwrite-strings
-Wno-strict-aliasing -Wdeclaration-after-statement -fno-builtin -fno-common
-DHAVE_STDINT_H -DGX_COLOR_INDEX_TYPE="unsigned long long"   -I./psi -I./obj
-I./obj -I./base  -o ./obj/zpdfops.o -c ./psi/zpdfops.c
./psi/zpdfops.c:30:26: error: stringprep.h: No such file or directory
.
.
.

This appears to be because on a default Ubuntu installation the file 

  /usr/lib32/libidn.so

exists but the corresponding /usr/lib/libidn.so file does not.  autogen.sh in
-m32 mode detects the library and assumes that the libidn11-dev package is
installed.

It is possible to work around this problem by installing that package (or
probably removing the /usr/lib32/libidn.so file) but it would be preferable
Ghostscript compiled without this change.

Note that peeves fails in this way so can be used for testing.

-- 
Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the gs-bugs mailing list