Re: [GENERAL] Error compiling Slony I

2007-11-29 Thread Vivek Khera


On Nov 28, 2007, at 11:17 AM, Glyn Astill wrote:


I've already tried removing and re-installing bison, but I shall try
again as you suggest.



I recommended uninstalling bison, not re-installing it.


---(end of broadcast)---
TIP 6: explain analyze is your friend


Re: [GENERAL] Error compiling Slony I

2007-11-28 Thread Alvaro Herrera
Glyn Astill wrote:
> Hi Vivek,
> 
> Ah thanks, I have posted this to the slony list tooo, but it doesn't
> seem to have appeared yet so I thought I'd ask here.
> 
> I've already tried removing and re-installing bison, but I shall try
> again as you suggest.

Actually I think the suggestion is to remove bison and recompile Slony
without reinstalling it.



-- 
Alvaro Herrera   Valdivia, Chile   ICBM: S 39º 49' 18.1", W 73º 13' 56.4"
"La virtud es el justo medio entre dos defectos" (Aristóteles)

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [GENERAL] Error compiling Slony I

2007-11-28 Thread Glyn Astill
Hi Vivek,

Ah thanks, I have posted this to the slony list tooo, but it doesn't
seem to have appeared yet so I thought I'd ask here.

I've already tried removing and re-installing bison, but I shall try
again as you suggest.

You can't remember any other detail can you?

Thanks
Glyn
--- Vivek Khera <[EMAIL PROTECTED]> wrote:

> 
> On Nov 28, 2007, at 8:50 AM, Glyn Astill wrote:
> 
> > Hi people,
> >
> > When I try to compile Slony 1.2 I get the following error:P
> >
> > parser.y:1090:18: error: scan.c: No such file or directory
> > make[2]: *** [parser.o] Error 1
> > make[2]: Leaving directory
> `/tmp/slony1-1.2.12/src/slony_logshipper'
> > make[1]: *** [all] Error 2
> > make[1]: Leaving directory `/tmp/slony1-1.2.12/src'
> >
> > I've installed bison.
> >
> > Anyone got any idea what I may be doing wrong?
> 
> Slony mailing list will be more helpful... but I ran into this. 
> the  
> solution for me was to uninstall bison and re-build.  for some
> reason  
> if the slony configure script finds bison, it forces it to rebuild
> the  
> parser.  i think the parser requires a certain version of bison.
> 
> 
> ---(end of
> broadcast)---
> TIP 3: Have you checked our extensive FAQ?
> 
>http://www.postgresql.org/docs/faq
> 



Glyn Astill



  ___
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/ 

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [GENERAL] Error compiling Slony I

2007-11-28 Thread Vivek Khera


On Nov 28, 2007, at 8:50 AM, Glyn Astill wrote:


Hi people,

When I try to compile Slony 1.2 I get the following error:P

parser.y:1090:18: error: scan.c: No such file or directory
make[2]: *** [parser.o] Error 1
make[2]: Leaving directory `/tmp/slony1-1.2.12/src/slony_logshipper'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/slony1-1.2.12/src'

I've installed bison.

Anyone got any idea what I may be doing wrong?


Slony mailing list will be more helpful... but I ran into this.  the  
solution for me was to uninstall bison and re-build.  for some reason  
if the slony configure script finds bison, it forces it to rebuild the  
parser.  i think the parser requires a certain version of bison.



---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

  http://www.postgresql.org/docs/faq


[GENERAL] Error compiling Slony I

2007-11-28 Thread Glyn Astill
Hi people,

When I try to compile Slony 1.2 I get the following error:P

parser.y:1090:18: error: scan.c: No such file or directory
make[2]: *** [parser.o] Error 1
make[2]: Leaving directory `/tmp/slony1-1.2.12/src/slony_logshipper'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/slony1-1.2.12/src'

I've installed bison.

Anyone got any idea what I may be doing wrong?


Glyn Astill



  ___ 
Want ideas for reducing your carbon footprint? Visit Yahoo! For Good  
http://uk.promotions.yahoo.com/forgood/environment.html

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly