GNOME Bugzilla – Bug 77833
1.99.10 - make install tries to install xml catalog in system directories regardless of prefix.
Last modified: 2004-12-22 21:47:04 UTC
I am building gnome2 on an OSF/1 4.0d box, however I dont have root permissions. I have my ROOTCATALOG env variable set to be under my home directory, and configured libglade with --prefix=$HOME ... however it tries to install the xml catalog into the system directories, which I dont have access to. I think that it should really use the prefix from building - or at least understand the environment variable (which I am under the impression is the correct one)
I think you should be able to set the XMLCATALOG environment variable to get this to work. Is ROOTCATALOG a standard for XML catalogs? I couldn't find any reference to it in the libxml2 sources. I use /etc/xml/catalog, as that is where libxml2 looks for the catalog. If this fixes your problem, then I will mark this report as NOTABUG.
well I sort of am grabbing names of environment variables from the air a bit (although if my memory is correct I got ROOTCATALOG out of the install scripts for the xml dtd?) - since it seems pretty predominant to use the system directories (unfortunate for me:P) I have added XMLCATALOG to my env as well - however it doesnt fix the matter. XMLCATALOG gets overwritten by the makefile - and configure doesnt know to do anything about setting it in the makefile based on the env variable, so it just leaves it as default in makefile.in. Or at least thats my take on the matter - my experience with makefile and configure is not great. If XMLCATALOG ends up fixing things that would be fine - yet another env variable isnt going to kill me.
The build should be set up to ignore errors when trying to add to the catalog (if it can't modify /etc/xml/catalog, then it should continue). The catalog entries are not required for normal operation of libglade -- they are only added so that developers can validate their glade files (DTD validation is not performed when libglade loads a glade file).
yes it ignores it - thats why I placed this as only minor severity. maybe enhancement is a better level. I manually ran the command myself so it doesnt bother me, just looking out for any future users in my category of limited access on their development machine.
Also found this... Perhaps there should be a --with-xml-catalog configure option? Setting XMLCATALOG does work, however.
Scratch that, it's a stupid idea (unless it was enabled somehow via gtkdocize, but that sounds like crack). I think this is NOTABUG. :-)
Okay, I copied over the macro used in gtk-doc, so passing --with-xml-catalog=FILENAME should change the catalog that it tries to install into.
*** Bug 134231 has been marked as a duplicate of this bug. ***