I wrote:
> What *does* seem feasible is to back-port just the single change we
> actually need, by copying the two relevant macros into one of our
> config/ source files for the configure script. I've tested that in
> 8.3 and it seems to work --- at least, the generated configure script
> changes in the expected way. This also seems like a reasonably sane
> thing to back-port to 8.2. So I'll go ahead and commit those things
> and see if anchovy likes it.
So the upshot is that that fixed the 8.3 build, but anchovy is still
failing on 8.2, with some different errors:
/usr/bin/ld.gold: /tmp/ccn7RPJJ.ltrans0.ltrans.o: in function
base_yyparse:y.tab.c:12777: error: undefined reference to 'filtered_base_yylex'
/usr/bin/ld.gold: /tmp/ccn7RPJJ.ltrans0.ltrans.o: in function
base_yyparse:gram.y:494: error: undefined reference to 'parsetree'
/usr/bin/ld.gold: /tmp/ccn7RPJJ.ltrans7.ltrans.o: in function
parseTypeString:parse_type.c:445: error: undefined reference to 'raw_parser'
/usr/bin/ld.gold: /tmp/ccn7RPJJ.ltrans19.ltrans.o: in function
simplify_function.128434.2836:postgres.c:544: error: undefined reference to
'raw_parser'
/usr/bin/ld.gold: /tmp/ccn7RPJJ.ltrans19.ltrans.o: in function
pg_parse_and_rewrite:postgres.c:544: error: undefined reference to 'raw_parser'
/usr/bin/ld.gold: /tmp/ccn7RPJJ.ltrans19.ltrans.o: in function
fmgr_sql_validator:postgres.c:544: error: undefined reference to 'raw_parser'
collect2: ld returned 1 exit status
I went so far as to install Arch Linux here, but I cannot duplicate
the above. (Although I wonder whether my machine is really doing
link-time optimization, since it doesn't generate any compiler warning
messages during the link step, as anchovy is doing.)
But these errors seem like they should be impossible anyway,
since there is nothing platform-specific about our uses of any of the
mentioned functions. I wonder if there is something messed up with
anchovy's copy of REL8_2_STABLE. Marti, could I trouble you to
blow away and recreate that machine's 8.2 checkout, as well as any
compiler cache directories?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
