[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: alternative sgmltools?
On Thu, 23 Dec 1999, Gerard Beekmans wrote:
deletion...
> Ok, here's what happens when I use the sgml-tools downloaded from
> www.sgmltools.org (1.0.9)
deletion...
> Then compilation stops at compiling ParserState.cxx
> c++ -ansi -fno-implicit-templates -O2 -Wall -Wno-reorder
> -Wwrite-strings -Wpointer-arith -Wnested-externs -Woverloaded-virtual
> -Wbad-function-cast -I. -I./../include -I./../generic -DSTDC_HEADERS=1
> -DHAVE_LIMITS_H=1 -DHAVE_ST_BLKSIZE=1 -Dsig_atomic_t=int
> -DSP_HAVE_BOOL=1 -DSP_HAVE_LOCALE=1 -DSP_ANSI_CLASS_INST=1 -c
> ParserState.cxx
Somehow, I ended up without any "-W*" option. But the problem which
caused my compilation to quit was the "-Dsig_atomic_t=int" option. I
have forgotten exactly where I put the fix. I think that I added
"#include <signal.h> at line 1521 of
~/sgmltools-2.0.2/packages/cvs/jade/configure.
In any event, you want to eliminate the "-Dsig_atomic_t=int" option.
Maybe you can read "configure" scripts better than I or the guy who
wrote the script can.
I had another major problem. That was running out of virtual memory
when trying to compile ParserState.cxx. The fault is that the "make"
script runs "python" and then "make". I had six "make"s plus "python"
using up memory (from a "ps eax" readout). Again, a poorly written
script.
The developers apparently run on University or Corporate main frames
where memory is infinite (or nearly so). The whole organization of
SGML requires obscene amounts of ram and disk memory. All without
information about how to use SGML. I guess the LDP core team expects
us to invest in a library full of books. It also seems to be a means
to push Debian/Redhat versions of Linux.
Why *rpms?
Why cvs/* for users?
How does Python work?
What are the library calls in jade.lib?
vern
--
Vernon C. Hoxie vern@zebra.alphacdc.com
3975 W. 29th Ave. uucp: 303-455-2670
Denver, Colo., 80212 voice: 303-477-1780
I'm not cheap, but I am on special this week
--
To UNSUBSCRIBE, email to ldp-discuss-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org