Re: [BUGS] Conflicts with autoconf macroses

2003-12-04 Thread Peter Eisentraut
Olleg writes: > > because of this kind of name conflict. There is a contributed macro that > > automatically prefixes all macro names so they don't conflict. May be > > worth checking out. > > ??? Please explain. http://ac-archive.sourceforge.net/guidod/ax_prefix_config_h.html ---

Re: [BUGS] Conflicts with autoconf macroses

2003-12-04 Thread Olleg
Tom Lane wrote: Olleg <[EMAIL PROTECTED]> writes: It's bug, autoconf headers may not be included in "library headers". If you think it's a bug you'd better complain to the autoconf people. pg_config.h is generated entirely by autoconf tools. The most libraries use autoheader, but don't generate

Re: [BUGS] Conflicts with autoconf macroses

2003-12-04 Thread Olleg
Peter Eisentraut wrote: Tom Lane writes: Olleg <[EMAIL PROTECTED]> writes: It's bug, autoconf headers may not be included in "library headers". If you think it's a bug you'd better complain to the autoconf people. pg_config.h is generated entirely by autoconf tools. Admittedly, you're not suppos

Re: [BUGS] Conflicts with autoconf macroses

2003-12-03 Thread Peter Eisentraut
Tom Lane writes: > Olleg <[EMAIL PROTECTED]> writes: > > It's bug, autoconf headers may not be included in "library headers". > > If you think it's a bug you'd better complain to the autoconf people. > pg_config.h is generated entirely by autoconf tools. Admittedly, you're not supposed to install

Re: [BUGS] Conflicts with autoconf macroses

2003-12-03 Thread Tom Lane
Olleg <[EMAIL PROTECTED]> writes: > It's bug, autoconf headers may not be included in "library headers". If you think it's a bug you'd better complain to the autoconf people. pg_config.h is generated entirely by autoconf tools. regards, tom lane --