Opened 9 years ago

Closed 9 years ago

#3379 closed defect (fixed)

Error during compilation of PostGIS source code

Reported by: bleukert Owned by: strk
Priority: low Milestone: PostGIS 2.2.1
Component: build Version: 2.2.x
Keywords: Cc:

Description

During the compilation of the PostGIS source code (exported from svn-2.2 branch) I received the following error message:

gcc -O2 -Wall -Wmissing-prototypes -I/opt/libgeos/include -I/opt/libproj/include -I/opt/cunit/include -I.. -c -o cu_out_twkb.o cu_out_twkb.c
cu_out_twkb.c:1: error: stray ‘\357’ in program
cu_out_twkb.c:1: error: stray ‘\273’ in program
cu_out_twkb.c:1: error: stray ‘\277’ in program
make[2]: * [cu_out_twkb.o] Error 1
make[2]: Leaving directory `/tmp/postgis/postgis-svn-2.2/liblwgeom/cunit'
make[1]:
* [check] Error 2
make[1]: Leaving directory `/tmp/postgis/postgis-svn-2.2/liblwgeom'
make: * [check] Error 1

Can you please fix the file cu_out_twkb.c?

Best regards,
Boris

Change History (7)

comment:1 by robe, 9 years ago

Boris,

Which version of gcc, CUnit, and what platform are you on.

I haven't had issue with cu_out_twkb and none of our ci bots - https://trac.osgeo.org/postgis/ have failed on testing 2.2.1 branch.

Last edited 9 years ago by robe (previous) (diff)

comment:2 by bleukert, 9 years ago

Platform: SUSE Linux Enterprise Server 11 (x86_64) SP3
Version gcc: gcc version 4.3.4 [gcc-4_3-branch revision 152973] (SUSE Linux)
Version CUnit: 2.1-3

I think it's similar problem which was solved for other files with commit 90d2de2 "Strip BOM from files " on 13 October by strk.

comment:3 by strk, 9 years ago

(In [14442]) Trip BOM from unit test

See #3379

comment:4 by strk, 9 years ago

(In [14443]) Trip BOM from unit test

See #3379

comment:5 by strk, 9 years ago

Should be fixed by r14442 in trunk and r14443 in 2.2 branch. Please confirm.

comment:6 by bleukert, 9 years ago

No errors during compilation after your change.

Thanks a lot,
Boris

comment:7 by strk, 9 years ago

Resolution: fixed
Status: newclosed

thanks for reporting

Note: See TracTickets for help on using tickets.