| Lists: | pgsql-hackers |
|---|
| From: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
|---|---|
| To: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | building postgres-A4.tex-pdf crushed |
| Date: | 2010-03-02 13:13:07 |
| Message-ID: | Pine.LNX.4.64.1003021611090.24655@sn.sai.msu.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
Hi there,
just to inform, that building of postgres-A4.tex-pdf (8.4) crushed on my
Ubuntu 9.10 machine. No problem with CVS HEAD.
openjade -D . -c /usr/share/sgml/docbook/stylesheet/dsssl/modular/catalog -d ./stylesheet.dsl -t tex -V tex-backend -i output-print -V texpdf-output -V '%paper-type%'=A4 -o postgres-A4.tex-pdf postgres.sgml
openjade:./stylesheet.dsl:502:2:E: flow object not accepted by port; only display flow objects accepted
make: *** [postgres-A4.tex-pdf] Segmentation fault (core dumped)
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83
| From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
|---|---|
| To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
| Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: building postgres-A4.tex-pdf crushed |
| Date: | 2010-03-02 13:36:56 |
| Message-ID: | 4B8D1478.2010204@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
Oleg Bartunov wrote:
> just to inform, that building of postgres-A4.tex-pdf (8.4) crushed on my
> Ubuntu 9.10 machine. No problem with CVS HEAD.
Alvaro and I are both having the opposite problem on Ubuntu 9.04: 8.4
works fine, but CVS HEAD dumps core:
http://archives.postgresql.org/message-id/20100215141242.GA2982@alvh.no-ip.org
I wonder if someone more familiar with doing git bisects than me might
track down the exact commit that swapped the behavior here. Since this
looks like an awful openjade bug regardless, not sure what we could do
about it; would be nice to know exactly how it happened though.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.us