[postgis-users] PostGIS 2.2.0 build error on Linux.

Bandaru Muralikrishna bandaru.muralikrishna at enterprisedb.com
Tue Oct 13 01:08:15 PDT 2015


My compiler version is :

gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-55)

One more question , is bison 3.0 version required to build PostGIS
2.2.0 ?  because i got the below build error when i build with bison
2.3 version. After upgrade bison to 3.0.4, the build issue got
resolved. Interestingly build was passed on OS X  ( 10.9 ) with bison
2.3 version without any build issue.

-----

bison -y -o'lwin_wkt_parse.c' -d lwin_wkt_parse.y

lwin_wkt_parse.y:106.14-21: syntax error, unexpected string, expecting =

make[1]: Leaving directory
`/mnt/hgfs/pginstaller.pune/PostGIS/source/postgis.linux/liblwgeom'

make[1]: *** [lwin_wkt_parse.h] Error 1

make: *** [all] Error 1
Murali Krishna
Software Engineer

phone: +919767825021
Website: www.enterprisedb.com
EnterpriseDB Blog: http://blogs.enterprisedb.com/
Follow us on Twitter: http://www.twitter.com/enterprisedb


On Tue, Oct 13, 2015 at 1:14 PM, Sandro Santilli <strk at keybit.net> wrote:
> On Tue, Oct 13, 2015 at 11:47:09AM +0530, Bandaru Muralikrishna wrote:
>> Hi,
>>
>> I am trying build PostGIS 2.2.0 source code on linux platform . I am
>> getting below build error:
>> -----
>> In file included from bytebuffer.c:40:
>> bytebuffer.h:1: error: stray ‘\357’ in program
>> bytebuffer.h:1: error: stray ‘\273’ in program
>> bytebuffer.h:1: error: stray ‘\277’ in program
>> In file included from bytebuffer.h:44,
>>                  from bytebuffer.c:40:
>> varint.h:1: error: stray ‘\357’ in program
>> varint.h:1: error: stray ‘\273’ in program
>> varint.h:1: error: stray ‘\277’ in program
>> make[1]: make[1]: Leaving directory
>> `/mnt/hgfs/pginstaller.pune/PostGIS/source/postgis.linux/liblwgeom'
>> *** [bytebuffer.lo] Error 1
>> make: *** [all] Error 1
>>
>> ---------
>>
>> I found that the file types for the files mentioned below are UTF-8
>> Unicode. When I converted these files to ASCII type the build issue
>> get resolved. Should this change go in git?
>
> YES, it's a byte-order-mark (BOM) !
>
>> bytebuffer.h
>> effectivearea.h
>> varint.h
>> lwin_twkb.c
>
> Thanks for the list.
>
> Now fixed with r14269 in trunk and r14270 in 2.2 branch.
> Out of curiosity, which compiler (or preprocessor) did not understand
> the BOM ?
>
> --strk;
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users


More information about the postgis-users mailing list