Bug 690311 - SunPRO dislikes line endings in jasper/src/libjasper/jpc/jpc_qmfb.c
Summary: SunPRO dislikes line endings in jasper/src/libjasper/jpc/jpc_qmfb.c
Status: RESOLVED DUPLICATE of bug 690292
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: Build Process (show other bugs)
Version: 8.64
Hardware: Sun Solaris
: P4 trivial
Assignee: Ralph Giles
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-27 15:27 UTC by Jon Peatfield
Modified: 2009-02-27 16:04 UTC (History)
0 users

See Also:
Customer:
Word Size: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jon Peatfield 2009-02-27 15:27:06 UTC
In building gs 8.64 on Solaris8 with the SunPRO 5 compilers all is going well
until it hits jasper/src/libjasper/jpc/jpc_qmfb.c when the Sun compilers fall
over.  This turns out to be because of the line-endings in that file (DOS style
I think).

This doesn't happen when using gcc on Linux or MacOSX so perhaps the SunPRO
compiler is just being picky, but it didn't happen when building 8.63 with the
same SunPRO compiler so something has changed.

Configured with:

  CC=cc CFLAGS=-O ./configure --prefix=/opt/gs$GSVV --without-ijs --without-omni
--disable-cups --with-drivers=ALL --disable-compile-inits

the make then fails with:

...
cc  -DHAVE_MKSTEMP -DHAVE_HYPOT -DHAVE_FILE64 -DHAVE_MKSTEMP64  -O
-DSYS_TYPES_HAS_STDINT_TYPES -DGX_COLOR_INDEX_TYPE="unsigned long long" -O 
-I./obj/ -Ijasper/src/libjasper/include -DJAS_CONFIGURE -DEXCLUDE_BMP_SUPPORT=1
-DEXCLUDE_JPG_SUPPORT=1 -DEXCLUDE_MIF_SUPPORT=1 -DEXCLUDE_PGX_SUPPORT=1
-DEXCLUDE_PNM_SUPPORT=1 -DEXCLUDE_RAS_SUPPORT=1 -DEXCLUDE_PNG_SUPPORT=1 -o
./obj/jpc_qmfb.o -c jasper/src/libjasper/jpc/jpc_qmfb.c
"jasper/src/libjasper/jpc/jpc_qmfb.c", line 76: warning: invalid white space
character in directive
"jasper/src/libjasper/jpc/jpc_qmfb.c", line 78: warning: invalid white space
character in directive
"jasper/src/libjasper/jpc/jpc_qmfb.c", line 79: warning: invalid white space
character in directive
<snip many similar warnings>
"jasper/src/libjasper/jpc/jpc_qmfb.c", line 494: warning: invalid white space
character in directive
"jasper/src/libjasper/jpc/jpc_qmfb.c", line 495: syntax error before or at: {
"jasper/src/libjasper/jpc/jpc_qmfb.c", line 495: invalid source character: '\'
"jasper/src/libjasper/jpc/jpc_qmfb.c", line 496: auto/register inappropriate here
"jasper/src/libjasper/jpc/jpc_qmfb.c", line 496: undefined symbol: lstartptr
"jasper/src/libjasper/jpc/jpc_qmfb.c", line 496: warning: improper
pointer/integer combination: op "="
"jasper/src/libjasper/jpc/jpc_qmfb.c", line 496: non-constant initializer: op "NAME"
"jasper/src/libjasper/jpc/jpc_qmfb.c", line 496: invalid source character: '\'
...

Using our usual 'fix dos files' perl script to transform it works for us:

#! /usr/bin/perl
while ($arg = shift) {
    rename($arg, "$arg.old") ;
    open(IN, "<$arg.old") ;
    open(OUT, ">$arg") ;

    while (<IN>) {
        s/(\012)*\015(\012)*/\012/g;
        s/\032//g;
        print OUT $_ ;
    }
    close(IN) ;
    close(OUT) ;
}

and I'm sure that any other dos-to-unix convertor would as well.

In case you are interested I probably should have reported before that this
system also objects to the contents of psi/psromfs.mak since it can't understand
continuation lines - but the fix is pretty obvious.
Comment 1 Ralph Giles 2009-02-27 16:04:29 UTC
Fixed in r9481. I've combined the psromfs.mak line in r9513.

Thanks for the well written report!

*** This bug has been marked as a duplicate of 690292 ***