View previous topic :: View next topic |
Author |
Message |
TheFogger n00b
Joined: 25 Jun 2002 Posts: 14
|
Posted: Thu Oct 03, 2002 1:03 pm Post subject: Emerge KDE3.1 beta2 error |
|
|
Hi,
I get the following error when emerging kdebase from kde3.1 beta2:
I don't know what to make of it. I run Gentoo 1.3 with gcc 3.1.1. Can anybody help me?
Code: |
make[4]: Circular index.cache.bz2 <- index.cache.bz2 dependency dropped.
/usr/kde/3.1/bin/meinproc --check --cache index.cache.bz2 ./index.docbook
whatiskde.docbook:25: error: Entity 'MacOS' not defined
&MacOS; or &Windows; 95/NT. &kde; meets the requirement
^
whatiskde.docbook:130: error: chunk is not well balanced
^
whatiskde.docbook:1: validity error: ID what-is-kde already defined
<chapter id="what-is-kde">
^
whatiskde.docbook:7: validity error: ID whatiskde already defined
<anchor id="whatiskde"/>
^
whatiskde.docbook:9: validity error: ID what-is-kde-introduction already defined
<sect1 id="what-is-kde-introduction">
^
whatiskde.docbook:25: error: Entity 'MacOS' not defined
&MacOS; or &Windows; 95/NT. &kde; meets the requirement
^
whatiskde.docbook:130: error: chunk is not well balanced
^
index.docbook:66: error: Entity value required
&whatiskde;
^
make[3]: *** [index.cache.bz2] Error 1
make[3]: *** Waiting for unfinished jobs....
kdeprintingglossary.docbook:154: error: Entity 'MacOS' not defined
to &Microsoft; &Windows; and Apple &MacOS; clients. Based on IPP, it does
^
kdeprintingglossary.docbook:287: error: Entity 'MacOS' not defined
based OSes (like *BSD or &MacOS; X) will also find valuable information
^
kdeprintingglossary.docbook:1388: error: chunk is not well balanced
^
kdeprintingglossary.docbook:13: validity error: ID glossdiv-printing already defined
<glossdiv id="glossdiv-printing">
^
kdeprintingglossary.docbook:17: validity error: ID gloss-acl already defined
<glossentry id="gloss-acl">
^
kdeprintingglossary.docbook:29: validity error: ID gloss-appsocketprotocol already defined
<glossentry id="gloss-appsocketprotocol">
^
kdeprintingglossary.docbook:41: validity error: ID gloss-apsfilter already defined
<glossentry id="gloss-apsfilter">
^
kdeprintingglossary.docbook:73: validity error: ID gloss-authentication already defined
<glossentry id="gloss-authentication">
^
kdeprintingglossary.docbook:83: validity error: ID gloss-bidirectionalcommunication already defined
<glossentry id="gloss-bidirectionalcommunication">
^
kdeprintingglossary.docbook:99: validity error: ID gloss-bsdstyleprinting already defined
<glossentry id="gloss-bsdstyleprinting">
^
kdeprintingglossary.docbook:148: validity error: ID gloss-cups already defined
<glossentry id="gloss-cups">
^
kdeprintingglossary.docbook:154: error: Entity 'MacOS' not defined
to &Microsoft; &Windows; and Apple &MacOS; clients. Based on IPP, it does
^
kdeprintingglossary.docbook:287: error: Entity 'MacOS' not defined
based OSes (like *BSD or &MacOS; X) will also find valuable information
^
kdeprintingglossary.docbook:1388: error: chunk is not well balanced
^
index.docbook:13: error: Entity value required
&glossary-kdeprinting;
^
make[4]: *** [index.cache.bz2] Error 1
make[4]: Leaving directory `/var/tmp/portage/kdebase-3.1_beta2/work/kdebase-3.0.8/doc/khelpcenter/glossary'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/kdebase-3.1_beta2/work/kdebase-3.0.8/doc/khelpcenter'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/kdebase-3.1_beta2/work/kdebase-3.0.8/doc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/kdebase-3.1_beta2/work/kdebase-3.0.8'
make: *** [all] Error 2
!!! ERROR: The ebuild did not complete successfully.
!!! Function kde_src_compile, Line -6648, Exitcode 2
!!! died running emake, kde_src_compile:make |
_________________ M$ Wind0ze - that's immature open source spelling for you. |
|
Back to top |
|
|
aias4 n00b
Joined: 07 May 2002 Posts: 33 Location: Hartford, Connecticut
|
Posted: Thu Oct 03, 2002 1:58 pm Post subject: |
|
|
I don't know the answer. But does anybody test these ebuilds once they make them? seems like there are a lot of problems associated w/ merging kde... |
|
Back to top |
|
|
seang Tux's lil' helper
Joined: 18 Jun 2002 Posts: 88 Location: France
|
Posted: Fri Oct 04, 2002 6:06 am Post subject: |
|
|
Hi TheFogger
I get exactly the same problem Have you found a solution yet? I'm just about to start digging - offhand I have no idea what's up!!
About the only observation so far is before I started the ebuild yesterday, the dependencies demanded the download of at least 3 different versions of docbook (30 31 and 40, IIRC) which I remember thinking was odd (and this fault is clearly related to docbook...)
Hmmmm..... |
|
Back to top |
|
|
rac Bodhisattva
Joined: 30 May 2002 Posts: 6553 Location: Japanifornia
|
Posted: Fri Oct 04, 2002 6:21 am Post subject: |
|
|
aias4 wrote: | does anybody test these ebuilds once they make them? |
Sure, all the people that install them despite the fact that they're masked test them. Please remember, this is a discussion about a masked ebuild of an upstream beta. And KDE is a huge collection of software. _________________ For every higher wall, there is a taller ladder |
|
Back to top |
|
|
ebrostig Bodhisattva
Joined: 20 Jul 2002 Posts: 3152 Location: Orlando, Fl
|
Posted: Fri Oct 04, 2002 6:41 pm Post subject: |
|
|
The problem seen here is most likely due to an old docbook/sgml installation. Check what is installed by:
emerge -s dockbook
Update all of the packages that is installed where a newer version is available.
I didn't see this problem during compile, so I think it is version related.
Erik |
|
Back to top |
|
|
TheFogger n00b
Joined: 25 Jun 2002 Posts: 14
|
Posted: Sat Oct 05, 2002 2:37 pm Post subject: |
|
|
All the docbook related ebuilds are installed and up to date. I only updated one package from -r0 to -r2 but that didn't change anything. It's not too bad, I can wait until a final version of KDE 3.1 is released. _________________ M$ Wind0ze - that's immature open source spelling for you. |
|
Back to top |
|
|
seang Tux's lil' helper
Joined: 18 Jun 2002 Posts: 88 Location: France
|
Posted: Mon Oct 07, 2002 7:42 am Post subject: |
|
|
OK - I've "fixed" it!! Now there's no absolute certainty that you're identical, but I reckon there's a good chance.
First off, an admission: Rather than simply emerging -u kde, I first moved /usr/kde/3.1 to /usr/kde/3.1_beta1 and set up my envs to point to this. Hence my existing beta1 still works fine while I build beta2. The 'move' worked fine, and I then emerged arts and kdelibs with no issues, and they of course installed into /usr/kde/3.1/
It's then that the docbook stuff in emerge kdebase failed.
Question: did you also do some jiggery-pokery before emerging??
The 'cause' was that the 'new' meinproc which ended up in the beta2 tree was clearly wrong (interestingly it was exactly the same size as the beta1 version, but not byte for byte identical as per md5sum).
All I had to do to fix it was remerge kdelibs (well, actually, manually only do the bits required to build meinproc, as this 600MHz laptop is slooow) and all works fine (kdebase is now building OK).
The mystery to me is that between emerging kdelibs the first time, and rebuilding meinproc this time, nothing in the env (system or mine) has changed..., yet the beta2 build had probably picked up something lying around from beta1.
So I suggest:
1) Re-emerge the beta2 kdelibs (or just meinproc if you feel brave)
2) Try kdebase again
Good luck! |
|
Back to top |
|
|
ebrostig Bodhisattva
Joined: 20 Jul 2002 Posts: 3152 Location: Orlando, Fl
|
Posted: Mon Oct 07, 2002 10:35 pm Post subject: |
|
|
seang wrote: |
First off, an admission: Rather than simply emerging -u kde, I first moved /usr/kde/3.1 to /usr/kde/3.1_beta1 and set up my envs to point to this. Hence my existing beta1 still works fine while I build beta2. The 'move' worked fine, and I then emerged arts and kdelibs with no issues, and they of course installed into /usr/kde/3.1/
|
Ok, no need to do that I emerged Beta 2 while running Beta 1 without any problems. Due to a superslow production machine at work (400Mhz) there was no way I wanted to stay out of a GUI for 3 days
Bottom line is:
Don't mess with anything if you REALLY don't know what you are doing.
No need to move stuff around prior to emerging the new beta.
Erik |
|
Back to top |
|
|
seang Tux's lil' helper
Joined: 18 Jun 2002 Posts: 88 Location: France
|
Posted: Tue Oct 08, 2002 5:59 am Post subject: |
|
|
Quote: | Don't mess with anything if you REALLY don't know what you are doing.
|
But then I'd never do anything at all !!!
Actually you raise an interesting question: if I have (say) beta1 happily running in /usr/kde/3.1. You reckon that one can do the elements of the beta2 emerge without risking beta1 stopping?
I would have thought that if I do beta2 kdelibs (and of course arts) on top of beta1, exit KDE and then restart it, there would be a hugely high possibility of it not working!! Granted if one did ALL of beta2 while staying with beta1 running, then it's more safe.
So you really can do:
- all of beta1 running
- drop beta2 arts and libs on top
- exit kde
- restart kde
- have betaX start running
- continuing emerging kdebase et al
?? I'm dead impressed if that works. For me there would have to be complete binary compatibility for the libs in beta1 and beta2. Maybe that's it?
Interesting stuff, anyway (and I'm chuffed 'cos beta2 is running!) |
|
Back to top |
|
|
|