From: "Ben Rockwood" <BRockwood@homestead-inc.com>
To: <docbook-tools-discuss@sources.redhat.com>
Subject: Jade Installation Frustrations
Date: Fri, 20 Dec 2002 19:23:00 -0000 [thread overview]
Message-ID: <9B9B61FC5C65A94EAFC1950F2E58FCF8090DD0@postal.ksi.homestead-corp.com> (raw)
Hello.
I appologies if this is a common question, but I haven't seen an answer in the FAQ(s), archives, or on any site.
I've been wanting to play with DocBook for awhile now. I don't run a standard distro (LFS) so I am forced to install all the tools "by hand". DocBook/SGML tools and especially DTD are a massive pain to install. There doesn't seem to be any clear explanations as to how to do it either. Most docs simply says "download the zip and put it in an appropriate directory". There doesn't seem to be, in my eyes, a clear layout scheme. Or possibly I just don't understand it, which is why it seems so foreign.
But, despite this, my major headache has been Jade (and OpenJade).
I just pulled (again) Jade from the ftp site (here on sources.redhat.com)
and tried building it. I used both the "jade.tgz" and the "jade-1.2.1.tgz".
Every time, and on every machine I've ever tried to build these guys on I've
run into problems. I've never seen it compile correctly, and I must assume this is a "just me" problem, yet I see this problem on every Linux box I've tried (LFS and several RedHat boxen) as well as Solaris.
Can someone please explain to me the state of Jade, and why I might be having these problems? Is it just me?
benr.
Here's an example of the failure:
(snip)
mv -f assert.o assert.lo
c++ -ansi -O2 -fno-implicit-templates -I. -I./../include -I./../generic -DSTDC_HEADERS=1 -DHAVE_LIMITS_H=1 -Dconst
= -Dinline= -DHAVE_ST_BLKSIZE=1 -DSP_HAVE_BOOL=1 -DSP_HAVE_LOCALE=1 -DSP_ANSI_CLASS_INST=1 -DSP_MULTI_BYTE=1 -c -f
PIC -DPIC CharsetInfo.cxx
In file included from ../include/CharsetInfo.h:11,
from CharsetInfo.cxx:8:
../include/Vector.h: In instantiation of `Vector<RangeMapRange<WideChar, UnivChar> >':
../include/RangeMap.h:27: instantiated from `RangeMap<WideChar, UnivChar>'
../include/UnivCharsetDesc.h:73: instantiated from here
../include/Vector.h:50: `Vector<T>::operator[] (unsigned int) [with T =
RangeMapRange<WideChar, UnivChar>]' has already been declared in
`Vector<RangeMapRange<WideChar, UnivChar> >'
../include/Vector.h:52: `Vector<T>::begin () [with T =
RangeMapRange<WideChar, UnivChar>]' has already been declared in
`Vector<RangeMapRange<WideChar, UnivChar> >'
../include/Vector.h:54: `Vector<T>::back () [with T =
RangeMapRange<WideChar, UnivChar>]' has already been declared in
`Vector<RangeMapRange<WideChar, UnivChar> >'
In file included from ../include/CharsetInfo.h:11,
from CharsetInfo.cxx:8:
../include/Vector.h: In instantiation of `Vector<ISetRange<WideChar> >':
../include/ISet.h:25: instantiated from `ISet<WideChar>'
../include/UnivCharsetDesc.h:131: instantiated from here
../include/Vector.h:50: `Vector<T>::operator[] (unsigned int) [with T =
ISetRange<WideChar>]' has already been declared in
`Vector<ISetRange<WideChar> >'
../include/Vector.h:52: `Vector<T>::begin () [with T =
ISetRange<WideChar>]' has already been declared in
`Vector<ISetRange<WideChar> >'
../include/Vector.h:54: `Vector<T>::back () [with T =
ISetRange<WideChar>]' has already been declared in
`Vector<ISetRange<WideChar> >'
../include/Vector.h: In instantiation of `Vector<ISetRange<Char> >':
../include/ISet.h:25: instantiated from `ISet<Char>'
CharsetInfo.cxx:105: instantiated from here
../include/Vector.h:50: `Vector<T>::operator[] (unsigned int) [with T =
ISetRange<Char>]' has already been declared in `Vector<ISetRange<Char>
>'
../include/Vector.h:52: `Vector<T>::begin () [with T =
ISetRange<Char>]' has already been declared in `Vector<ISetRange<Char>
>'
../include/Vector.h:54: `Vector<T>::back () [with T = ISetRange<Char>]'
has already been declared in `Vector<ISetRange<Char> >'
../include/StringOf.h: In instantiation of `String<Char>':
CharsetInfo.cxx:129: instantiated from here
../include/StringOf.h:38: `String<T>::operator[] (unsigned int) [with T
= Char]' has already been declared in `String<Char>'
../include/StringOf.h:40: `String<T>::begin () [with T = Char]' has
already been declared in `String<Char>'
make[2]: *** [CharsetInfo.lo] Error 1
make[2]: Leaving directory `/home/benr/docbook/new/jade-1.2.1/lib'
make[1]: *** [lib] Error 2
make[1]: Leaving directory `/home/benr/docbook/new/jade-1.2.1'
make: *** [all] Error 2
[benr@nexus jade-1.2.1]
WARNING: multiple messages have this Message-ID
From: "Ben Rockwood" <BRockwood@homestead-inc.com>
To: <docbook-tools-discuss@sources.redhat.com>
Subject: Jade Installation Frustrations
Date: Tue, 02 Apr 2002 14:47:00 -0000 [thread overview]
Message-ID: <9B9B61FC5C65A94EAFC1950F2E58FCF8090DD0@postal.ksi.homestead-corp.com> (raw)
Message-ID: <20020402144700.yhVsJrdblCR2LhZUBsnloYLCdiKtvbrCIOwI9PE-PuU@z> (raw)
Hello.
I appologies if this is a common question, but I haven't seen an answer in the FAQ(s), archives, or on any site.
I've been wanting to play with DocBook for awhile now. I don't run a standard distro (LFS) so I am forced to install all the tools "by hand". DocBook/SGML tools and especially DTD are a massive pain to install. There doesn't seem to be any clear explanations as to how to do it either. Most docs simply says "download the zip and put it in an appropriate directory". There doesn't seem to be, in my eyes, a clear layout scheme. Or possibly I just don't understand it, which is why it seems so foreign.
But, despite this, my major headache has been Jade (and OpenJade).
I just pulled (again) Jade from the ftp site (here on sources.redhat.com)
and tried building it. I used both the "jade.tgz" and the "jade-1.2.1.tgz".
Every time, and on every machine I've ever tried to build these guys on I've
run into problems. I've never seen it compile correctly, and I must assume this is a "just me" problem, yet I see this problem on every Linux box I've tried (LFS and several RedHat boxen) as well as Solaris.
Can someone please explain to me the state of Jade, and why I might be having these problems? Is it just me?
benr.
Here's an example of the failure:
(snip)
mv -f assert.o assert.lo
c++ -ansi -O2 -fno-implicit-templates -I. -I./../include -I./../generic -DSTDC_HEADERS=1 -DHAVE_LIMITS_H=1 -Dconst
= -Dinline= -DHAVE_ST_BLKSIZE=1 -DSP_HAVE_BOOL=1 -DSP_HAVE_LOCALE=1 -DSP_ANSI_CLASS_INST=1 -DSP_MULTI_BYTE=1 -c -f
PIC -DPIC CharsetInfo.cxx
In file included from ../include/CharsetInfo.h:11,
from CharsetInfo.cxx:8:
../include/Vector.h: In instantiation of `Vector<RangeMapRange<WideChar, UnivChar> >':
../include/RangeMap.h:27: instantiated from `RangeMap<WideChar, UnivChar>'
../include/UnivCharsetDesc.h:73: instantiated from here
../include/Vector.h:50: `Vector<T>::operator[] (unsigned int) [with T =
RangeMapRange<WideChar, UnivChar>]' has already been declared in
`Vector<RangeMapRange<WideChar, UnivChar> >'
../include/Vector.h:52: `Vector<T>::begin () [with T =
RangeMapRange<WideChar, UnivChar>]' has already been declared in
`Vector<RangeMapRange<WideChar, UnivChar> >'
../include/Vector.h:54: `Vector<T>::back () [with T =
RangeMapRange<WideChar, UnivChar>]' has already been declared in
`Vector<RangeMapRange<WideChar, UnivChar> >'
In file included from ../include/CharsetInfo.h:11,
from CharsetInfo.cxx:8:
../include/Vector.h: In instantiation of `Vector<ISetRange<WideChar> >':
../include/ISet.h:25: instantiated from `ISet<WideChar>'
../include/UnivCharsetDesc.h:131: instantiated from here
../include/Vector.h:50: `Vector<T>::operator[] (unsigned int) [with T =
ISetRange<WideChar>]' has already been declared in
`Vector<ISetRange<WideChar> >'
../include/Vector.h:52: `Vector<T>::begin () [with T =
ISetRange<WideChar>]' has already been declared in
`Vector<ISetRange<WideChar> >'
../include/Vector.h:54: `Vector<T>::back () [with T =
ISetRange<WideChar>]' has already been declared in
`Vector<ISetRange<WideChar> >'
../include/Vector.h: In instantiation of `Vector<ISetRange<Char> >':
../include/ISet.h:25: instantiated from `ISet<Char>'
CharsetInfo.cxx:105: instantiated from here
../include/Vector.h:50: `Vector<T>::operator[] (unsigned int) [with T =
ISetRange<Char>]' has already been declared in `Vector<ISetRange<Char>
>'
../include/Vector.h:52: `Vector<T>::begin () [with T =
ISetRange<Char>]' has already been declared in `Vector<ISetRange<Char>
>'
../include/Vector.h:54: `Vector<T>::back () [with T = ISetRange<Char>]'
has already been declared in `Vector<ISetRange<Char> >'
../include/StringOf.h: In instantiation of `String<Char>':
CharsetInfo.cxx:129: instantiated from here
../include/StringOf.h:38: `String<T>::operator[] (unsigned int) [with T
= Char]' has already been declared in `String<Char>'
../include/StringOf.h:40: `String<T>::begin () [with T = Char]' has
already been declared in `String<Char>'
make[2]: *** [CharsetInfo.lo] Error 1
make[2]: Leaving directory `/home/benr/docbook/new/jade-1.2.1/lib'
make[1]: *** [lib] Error 2
make[1]: Leaving directory `/home/benr/docbook/new/jade-1.2.1'
make: *** [all] Error 2
[benr@nexus jade-1.2.1]
next reply other threads:[~2002-04-02 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 19:23 Ben Rockwood [this message]
2002-04-02 14:47 ` Ben Rockwood
2002-12-20 19:23 ` Éric Bischoff
2002-04-03 11:34 ` Éric Bischoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9B9B61FC5C65A94EAFC1950F2E58FCF8090DD0@postal.ksi.homestead-corp.com \
--to=brockwood@homestead-inc.com \
--cc=docbook-tools-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).