From kde-devel  Mon Feb 09 02:02:35 2004
From: Lauri Watts <lauri () kde ! org>
Date: Mon, 09 Feb 2004 02:02:35 +0000
To: kde-devel
Subject: Re: KDE_3_2_RELEASE doc problem
Message-Id: <200402090302.46017.lauri () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-devel&m=107629220118949
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============1966736810=="


--===============1966736810==
Content-Type: multipart/signed; protocol="application/pgp-signature";
	micalg=pgp-sha1; boundary="Boundary-02=_FpuJAjy+0sgu5ZR";
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


--Boundary-02=_FpuJAjy+0sgu5ZR
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Monday 09 February 2004 02.33, Thomas Schwarzgruber wrote:
> Am Sonntag, 8. Februar 2004 23:02 schrieb Joachim Eibl:
> > Why "/opt/kde_stable/bin/meinproc"? Shouldn't it use
> > "/opt/kdecvs/bin/meinproc" or similar?
> > meinproc comes as part of kdelibs.
> >
> > Joachim
>
> Because I decided to put kde_3_2_release into a seperate directory which i
> called kde_stable (actual cvs lies in kde_unstable)

So let's review the issues here.

To compile meinproc, you need bzip2.  If you don't have it, it will not=20
compile.   If meinproc does not compile *and is not found in the path* the=
=20
documentation will not be compiled - it will just be skipped.  If meinproc=
=20
exists, and is found, but it's an old version, it will fail - you must use =
at=20
least a version that can locate the DTD's being used. =20

I notice you are complaining about Kate's doc.  This is the first doc to be=
=20
compiled in kdebase, so it's natural, however, it's *not* the first documen=
t=20
to be compiled at all, that is kspell which is in kdelibs.  If that one is=
=20
not failing, then obviously a working copy of meinproc is being built for=20
you, things go wrong only after the kdelibs installation.

So - what do you have set as $KDEDIR? how about $KDEDIRS?  Does setting eit=
her=20
of those help?  Or unsetting them, if they are wrong.  This is probably the=
=20
number one cause of this problem - an incorrect KDEDIR setting kicks up an=
=20
incorrect version of meinproc, and chaos ensues.

What is set as the $PATH? =20

Do you have any other copies of meinproc on the system - what does `which=20
meinproc` say? What does locate have to say about it? Run a find over all t=
he=20
directories in your path, to be sure.

How about 'checkXML' - can you run it, and do you have more than one copy o=
f=20
it lying around?  If you do,=20

What version of libxml2 do you have installed?

I see you are running in a non-English locale? If so, does resetting LC_ALL=
 to=20
C during compile help?=20

And please, don't shout.  I don't know where you've been asking this questi=
on=20
for a year, but it hasn't been anywhere that I could see it.

Regards,
=2D-=20
Lauri Watts
KDE Documentation: http://i18n.kde.org/doc/
KDE on FreeBSD: http://freebsd.kde.org/

--Boundary-02=_FpuJAjy+0sgu5ZR
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQBAJupF/gUyA7PWnacRAkPjAJ0eFLUo8WkI3z2kaBGPeTMupFFunACeOoNb
mHF1h5EH1temtMKCrDrCGn0=
=9/6d
-----END PGP SIGNATURE-----

--Boundary-02=_FpuJAjy+0sgu5ZR--

--===============1966736810==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--===============1966736810==--