Fri Aug 19 06:12:15 PDT 2005
- Previous message: [Slony1-general] slony 1.1.0 compile failure
- Next message: [Slony1-general] slony 1.1.0 compile failure
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Can't you just do: emerge slony1 ? I run gentoo, and that is what I did. Works just fine. I did have to unmask slony1 in /etc/portage/package.keywords. Ujwal --- Tim Allen <tim at proximity.com.au> wrote: > I'm trying to compile slony 1.1.0, and not getting > very far. > > Platform summary: x86, gentoo linux, postgresql > 8.0.3, gcc 3.2.2 > > The first problem is that there is no such type as > "int64", as the > following compile failures in src/slon show: > > gcc -g -O2 -pthread -I../.. -I/home/tim/pg/include/ > -I/home/tim/pg/include/ > -I/home/tim/pg/include/postgresql/server/ -c -o > slon.o slon.c > In file included from slon.h:18, > from slon.c:30: > misc.h:29: parse error before "int64" > In file included from slon.c:30: > slon.h:95: parse error before "int64" > slon.h:95: warning: no semicolon at end of struct or > union > slon.h:111: parse error before '}' token > > and many more just like them. > > I kludged my way past that one with a > typedef long long int64; > in misc.h, but the next set of errors look a bit > harder to fix simply: > > gcc -g -O2 -pthread -I../.. -I/home/tim/pg/include/ > -I/home/tim/pg/include/ > -I/home/tim/pg/include/postgresql/server/ -c -o > slon.o slon.c > In file included from slon.c:31: > confoptions.h:103: initializer element is not > constant > confoptions.h:103: (near initialization for > `ConfigureNamesInt[0].gen.short_desc') > confoptions.h:104: initializer element is not > constant > confoptions.h:104: (near initialization for > `ConfigureNamesInt[0].gen.long_desc') > confoptions.h:106: initializer element is not > constant > confoptions.h:106: (near initialization for > `ConfigureNamesInt[0].gen') > confoptions.h:111: initializer element is not > constant > confoptions.h:111: (near initialization for > `ConfigureNamesInt[0]') > > and many more lines like these. > > I've browsed the mailing list archives, expecting to > see them > overflowing with similar reports, but haven't seen > any at all, so > presumably there is something relatively unusual in > my installation. Any > ideas as to what it might be? > > Tim > > -- > ----------------------------------------------- > Tim Allen tim at proximity.com.au > Proximity Pty Ltd http://www.proximity.com.au/ > _______________________________________________ > Slony1-general mailing list > Slony1-general at gborg.postgresql.org > http://gborg.postgresql.org/mailman/listinfo/slony1-general >
- Previous message: [Slony1-general] slony 1.1.0 compile failure
- Next message: [Slony1-general] slony 1.1.0 compile failure
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list