After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 161073 - [docs] jadetex stuck in endless loop
[docs] jadetex stuck in endless loop
Status: RESOLVED NOTGNOME
Product: GStreamer
Classification: Platform
Component: documentation
git master
Other Linux
: Normal major
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-12-12 12:32 UTC by Loïc Minier
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description Loïc Minier 2004-12-12 12:32:05 UTC
When building gstreamer with jhbuild, the documentation build is stuck in:

make[4]: Leaving directory `/home/lool/cvs/gnome2/gstreamer/docs/pwg'
*** Generating PS output ***
cd build && docbook2ps -o .. pwg.xml
Using catalogs: /etc/sgml/catalog
Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
Working on: /home/lool/cvs/gnome2/gstreamer/docs/pwg/build/pwg.xml
jade:/usr/share/sgml/declaration/xml.dcl:31:27:W: characters in the document
character set with numbers exceeding 65535 not supported

It seems an endless loop, when I kill jadetex from another shell (^C wont kill
it), it outputs a fat list of pages it has generated.

Other people on IRC reported getting this as well.
Comment 1 Loïc Minier 2004-12-12 12:33:24 UTC
Quoting /usr/share/sgml/declaration/xml.dcl around line 31:
         DESCSET
                 0        9  UNUSED
                 9        2       9
                11        2  UNUSED
...
             65534        2  UNUSED -- FFFE and FFFF --
             65536  1048576   65536 -- 16 planes outside BMP --

(This last line is line 31.)
Comment 2 Loïc Minier 2004-12-12 13:25:09 UTC
It's seems the warning and xml.dcl are completely irrelevant.
Comment 3 Ronald Bultje 2004-12-17 00:57:05 UTC
Are you using debian? If so, is this debian-specific?
Comment 4 Loïc Minier 2004-12-17 07:12:35 UTC
I use Debian, and I wondered if it was Debian-specific too.  I asked about that
on IRC, someone with Debian had the same problem.

I can't tell whether people with other distros are seing that as well.
Comment 5 Ronald Bultje 2004-12-17 10:12:32 UTC
If you want to do something weird, take the redhat package, rebuild it for
debian and see if it's reproduceable. If not, file a bug to the debian jadetex
package.
Comment 6 Loïc Minier 2004-12-17 19:41:45 UTC
I tried really hard to bring rpm under Debian to work, but it's really deeply
borken (I can't configure topdir or builddir in .rpmrc without rpm barking that
it doesn't know about them and strange errors and debug output appears), so I
tried doing the rpm stuff myself (call me "rpm"), and as I understand rpm it's
something like:
%prep
%build
%install

%prep is defined as:
%prep
%setup -n gstreamer-%{version}

Can't do very much here, let's see %build:
%build
%configure \
  --enable-debug \
  --with-cachedir=%{_localstatedir}/cache/gstreamer-%{majorminor} \
  --disable-tests --disable-examples --disable-docs-build

I stopped here: redhat doesn't ship documentation neither, probably for the same
reason...
Comment 7 Ronald Bultje 2004-12-18 13:44:15 UTC
The bug is in jadetex. Commenting out the words "professional audio
applications." in pwg/advanced-types.xml (line 344) makes it build fine.
Probably an overflow in Debian's jadetex. Bug report submitted upstream by Jan.
Comment 8 Ronald Bultje 2004-12-18 15:45:41 UTC
Closing on request.