Re: [HACKERS] New psql compile problem.

On Sat, 6 Nov 1999, Bruce Momjian wrote:

> > make[2]: Entering directory `/export/home/pgsql/src/bin/psql'
> > make -C ../../interfaces/libpq libpq.a
> > make[3]: Entering directory `/export/home/pgsql/src/interfaces/libpq'
> > make[3]: `libpq.a' is up to date.
> > make[3]: Leaving directory `/export/home/pgsql/src/interfaces/libpq'
> > gcc -I../../interfaces/libpq -I../../include -I../../backend    -Wall 
> > -Wmissing-prototypes -g -O2 -DLOCK_MGR_DEBUG -DDEADLOCK_DEBUG   -c command.c -o 
> > command.o
> > gcc -I../../interfaces/libpq -I../../include -I../../backend    -Wall 
> > -Wmissing-prototypes -g -O2 -DLOCK_MGR_DEBUG -DDEADLOCK_DEBUG   -c common.c -o 
> > common.o
> > make[2]: *** No rule to make target `../../../doc/src/sgml/ref/*.sgml', needed 
> > by `sql_help.h'.  Stop.
> > make[2]: Leaving directory `/export/home/pgsql/src/bin/psql'
> 
> Do you have sgml files in that directory?  You should.

The intend was that the sql_help.h would be prepared before distribution,
so people that don't have docs or don't have Perl or other weird problems
don't get that sort of problem, because after all it *is* a hack. We
already do the same with the pre-bisoned parsers.

Perhaps there is still a problem if the docs are installed one second
later than the psql subtree. How do you handle that with the parsers? Do
it the same here.

-- 
Peter Eisentraut                  Sernanders vaeg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden