..emh... it's not easy to recall what I could have done *exactly*.
Perhaps i forgot the --with-python or --with-perl switch first, then I
did ./configure again without doing a make distclean beforehand. I tried
to make this "error" again now, but the error did not reappear. I even
tried to misspell --with-perl (to my surprise this was not flagged as an
error) but again, the error did not reappear. So I give up on this one;
anyway my system now appears to work properly.
Sometimes it's really crazy: it's hard to get rid of these errors, but
it's even harder to get them back again...
thanks again for your support
>>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 15.12.2003 >>>
"Marcel Gsteiger" <Marcel(dot)Gsteiger(at)milprog(dot)ch> writes:
> I have deleted my source tree, untarred it again from the bzipped
> source and could compile it last night more than 100 times without
> serious errors.
Fascinating. It's good that the problem doesn't just appear and
disappear at random, but that still leaves us with not much to go on.
The only theory I can concoct is that you made some misstep in the
initial build attempt that caused the problem (but how?), and when you
did "make distclean" the problem was fixed. Can you recall any false
starts or configure changes that you made during the first attempt?
I'd be willing to write this off as an irreproducible glitch, were it
not that someone else reported the apparently-identical problem.
regards, tom lane
pgsql-ports by date
|Next:||From: Bruce Momjian||Date: 2003-12-16 00:46:50|
|Subject: Re: darwin x86|
|Previous:||From: Tom Lane||Date: 2003-12-15 14:40:00|
|Subject: Re: Antw: Re: Postgresql 7.4 fails to compile on Redhat Fedora Core 1 Linux |