LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 12-03-2006, 06:29 PM   #1
easuter
Member
 
Registered: Dec 2005
Location: Portugal
Distribution: Slackware64 13.0, Slackware64 13.1
Posts: 538

Rep: Reputation: 62
GNOME 2.16.2 build


Hi there,

I want to build a distro-specific GNOME package for VectorLinux 5.8, but i'm not sure where to start.
Since one of the distro's strong points is speed and being light-weight, I am more interested in building a very basic GNOME package, with the essential stuff first and the extras built separately and available for download later from the repo.

What would the best approach be for this kind of thing? Can I simply download the basic tarballs from the source tree and prefix them to /opt/gnome-2.16.2/ for example? Which are the most basic one to get GNOME up and running?
Also, is HAL required? and is PolicyKit a must have as well? (from what i gather its not even finished!)

Thanks in advance!
 
Old 12-03-2006, 09:09 PM   #2
weibullguy
ReliaFree Maintainer
 
Registered: Aug 2004
Location: Kalamazoo, Michigan
Distribution: Slackware 14.2
Posts: 2,815
Blog Entries: 1

Rep: Reputation: 261Reputation: 261Reputation: 261
No, AFAIR, HAL isn't required to build GNOME. But if you choose to build HAL, PolicyKit is a required dependency. Here are some instructions that you can use to help you build GNOME Core and GNOME Core Desktop. There is also a short discussion about installation strategies for GNOME (i.e., /usr vs. /opt branches). Good luck and have fun!
 
Old 12-04-2006, 02:57 AM   #3
easuter
Member
 
Registered: Dec 2005
Location: Portugal
Distribution: Slackware64 13.0, Slackware64 13.1
Posts: 538

Original Poster
Rep: Reputation: 62
Great, thanks!
 
Old 12-05-2006, 09:23 AM   #4
easuter
Member
 
Registered: Dec 2005
Location: Portugal
Distribution: Slackware64 13.0, Slackware64 13.1
Posts: 538

Original Poster
Rep: Reputation: 62
Well, I am able to compile the listed packages in core until "Shared-MIME-Info", but when I try to compile the gnome virtual fielsystem, i get this error:

Code:
No package 'gconf-2.0' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
I have the package prefix set to /opt/gnome-2.16.2 and have followed all the procedures indicated in that wiki page you gave to make sure that /opt/gnome-2.16.2/lib is in the ldconfig path.

so after running ldconfig, shouldn't the gconf libs be found?
 
Old 12-05-2006, 11:01 AM   #5
weibullguy
ReliaFree Maintainer
 
Registered: Aug 2004
Location: Kalamazoo, Michigan
Distribution: Slackware 14.2
Posts: 2,815
Blog Entries: 1

Rep: Reputation: 261Reputation: 261Reputation: 261
Yup, but that's not what the configure script is looking for. The configure script is looking for gconf-2.0.pc which should be installed in /opt/gnome-2.16.2/lib/pkgconfig on your system. ldconfig only looks for dynamic libraries. Run ldconfig -v and you will see what I mean.

Did you create the bash startup scripts in the Wiki? You would need to have a /etc/profile script that recurses into /etc/profile.d looking for *.sh files. If it doesn't then the /etc/profile.d/30-gnome.sh script wasn't executed and your env variables don't include any of the GNOME directories.

This is the line that needs to be executed to prevent this failure.
Code:
export PKG_CONFIG_PATH="${PKG_CONFIG_PATH}${PKG_CONFIG_PATH+:}/opt/gnome/lib/pkgconfig"
Make sure all the lines in the script beginning with the word 'export' are executed in your shell. You can execute them manually each time you enter a shell or automatically. How to do it automatically depends on how Vector Linux initializes env variables.
 
Old 12-05-2006, 12:13 PM   #6
easuter
Member
 
Registered: Dec 2005
Location: Portugal
Distribution: Slackware64 13.0, Slackware64 13.1
Posts: 538

Original Poster
Rep: Reputation: 62
Excellent! Thanks again!
 
Old 12-05-2006, 04:31 PM   #7
easuter
Member
 
Registered: Dec 2005
Location: Portugal
Distribution: Slackware64 13.0, Slackware64 13.1
Posts: 538

Original Poster
Rep: Reputation: 62
Well, i got stuck on the last core packge: libgnomeui.
It turns out that several packages on my system needed upgrading, and they were,'t the light players either:

GLib
GTK+2
Pango
Cairo

I was stupid enough to try and build and upgrade Glib and gtk+2 while i was still logged into my xfce session, so needless to say it didn't work.

Can i for example prefix the newer Glib, GTK+, Pango and cairo packages to /opt/gnome-2.16.2?
They will probably also be detected, since i have /opt/gnome-2.16.2/lib to be searched by ldconfig. Or might this create any other problems?
 
Old 12-05-2006, 05:24 PM   #8
weibullguy
ReliaFree Maintainer
 
Registered: Aug 2004
Location: Kalamazoo, Michigan
Distribution: Slackware 14.2
Posts: 2,815
Blog Entries: 1

Rep: Reputation: 261Reputation: 261Reputation: 261
I'm going with "this might create any other problems." As you stated, those are fairly important packages, not just to GNOME. Throwing them around willy-nilly isn't a wise idea and I'd recommend --prefix=/usr. Remember, the only package management you're using is your brain. Don't get impatient trying to install GNOME or you'll find yourself installing VectorLinux because everything will be hopelessly borked.

Without looking at the Makefile for those packages, I am guessing that they use 'install' rather than 'cp' to install their files. This should be safe even with things loaded into memory. Consider how often these packages have been upgraded by yum, apt, portage, etc. with the use in their GUI. If you're concerned, though, just jot down the build instructions and build from the CLI. None of the packages you mention have onerous procedures. There are instructions for all of these in the same Wiki.

Last edited by weibullguy; 12-05-2006 at 05:26 PM.
 
Old 12-06-2006, 09:51 AM   #9
easuter
Member
 
Registered: Dec 2005
Location: Portugal
Distribution: Slackware64 13.0, Slackware64 13.1
Posts: 538

Original Poster
Rep: Reputation: 62
Well, I'm going to have a word with the VectorLinux devs, and see if they have extra info on how they optimize their packages, because all i've been able to do so ar is wreck my system almost beyond repair.

Thanks again for the help!
 
Old 12-08-2006, 03:48 PM   #10
easuter
Member
 
Registered: Dec 2005
Location: Portugal
Distribution: Slackware64 13.0, Slackware64 13.1
Posts: 538

Original Poster
Rep: Reputation: 62
I finaly did get the GLIB2 and GTK+2 sources to build properly.
All the core components are made, now have started with the desktop packages.
However, I'm stuck once again, but this time on the GNOME Doc-Utils source.
I configure the source wih the flags indicated from that website. It compiles just fine, with no errors along the way, but make install fails!

here is the error i get:

Code:
make[4]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt/docbook/omf'
make[3]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt/docbook/omf'
Making install in utils
make[3]: Entering directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt/docbook/utils'
make[4]: Entering directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt/docbook/utils'
make[4]: Nothing to be done for `install-exec-am'.
/bin/sh ../../../mkinstalldirs /opt/gnome-2.16.2/share/xml/gnome/xslt/docbook/utils
 /usr/bin/ginstall -c -m 644 chunks.xsl /opt/gnome-2.16.2/share/xml/gnome/xslt/docbook/utils/chunks.xsl
 /usr/bin/ginstall -c -m 644 credits.xsl /opt/gnome-2.16.2/share/xml/gnome/xslt/docbook/utils/credits.xsl
 /usr/bin/ginstall -c -m 644 ids.xsl /opt/gnome-2.16.2/share/xml/gnome/xslt/docbook/utils/ids.xsl
make[4]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt/docbook/utils'
make[3]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt/docbook/utils'
make[3]: Entering directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt/docbook'
make[4]: Entering directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt/docbook'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt/docbook'
make[3]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt/docbook'
make[2]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt/docbook'
Making install in xsldoc
make[2]: Entering directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt/xsldoc'
make[3]: Entering directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt/xsldoc'
make[3]: Nothing to be done for `install-exec-am'.
/bin/sh ../../mkinstalldirs /opt/gnome-2.16.2/share/xml/gnome/xslt/xsldoc
 /usr/bin/ginstall -c -m 644 xsldoc.xsl /opt/gnome-2.16.2/share/xml/gnome/xslt/xsldoc/xsldoc.xsl
make[3]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt/xsldoc'
make[2]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt/xsldoc'
make[2]: Entering directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt'
make[3]: Entering directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt'
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt'
make[2]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt'
make[1]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xslt'
Making install in xml2po
make[1]: Entering directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xml2po'
Making install in modes
make[2]: Entering directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xml2po/modes'
make[3]: Entering directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xml2po/modes'
make[3]: Nothing to be done for `install-exec-am'.
/bin/sh ../../mkinstalldirs /opt/gnome-2.16.2/share/xml2po
 /usr/bin/ginstall -c -m 644 docbook.py /opt/gnome-2.16.2/share/xml2po/docbook.py
 /usr/bin/ginstall -c -m 644 empty.py /opt/gnome-2.16.2/share/xml2po/empty.py
 /usr/bin/ginstall -c -m 644 gs.py /opt/gnome-2.16.2/share/xml2po/gs.py
 /usr/bin/ginstall -c -m 644 ubuntu.py /opt/gnome-2.16.2/share/xml2po/ubuntu.py
make[3]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xml2po/modes'
make[2]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xml2po/modes'
Making install in examples
make[2]: Entering directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xml2po/examples'
make[3]: Entering directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xml2po/examples'
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xml2po/examples'
make[2]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xml2po/examples'
make[2]: Entering directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xml2po'
make[3]: Entering directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xml2po'
/bin/sh ../mkinstalldirs /opt/gnome-2.16.2/bin
 /usr/bin/ginstall -c xml2po /opt/gnome-2.16.2/bin/xml2po
/bin/sh ../mkinstalldirs /opt/gnome-2.16.2/share/man//man1
 /usr/bin/ginstall -c -m 644 ./xml2po.1 /opt/gnome-2.16.2/share/man//man1/xml2po.1
/bin/sh ../mkinstalldirs /opt/gnome-2.16.2/lib/pkgconfig
 /usr/bin/ginstall -c -m 644 xml2po.pc /opt/gnome-2.16.2/lib/pkgconfig/xml2po.pc
make[3]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xml2po'
make[2]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xml2po'
make[1]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/xml2po'
Making install in doc
make[1]: Entering directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/doc'
Making install in gnome-doc-make
make[2]: Entering directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/doc/gnome-doc-make'
make[3]: Entering directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/doc/gnome-doc-make'
make[3]: Nothing to be done for `install-exec-am'.
/bin/sh ../../mkinstalldirs /opt/gnome-2.16.2/share/gnome/help/gnome-doc-make/C
/usr/bin/ginstall -c -m 644 C/legal.xml /opt/gnome-2.16.2/share/gnome/help/gnome-doc-make/C/legal.xml
/usr/bin/ginstall -c -m 644 C/make-ref.xml /opt/gnome-2.16.2/share/gnome/help/gnome-doc-make/C/make-ref.xml
/usr/bin/ginstall -c -m 644 C/gnome-doc-make.xml /opt/gnome-2.16.2/share/gnome/help/gnome-doc-make/C/gnome-doc-make.xml
/bin/sh ../../mkinstalldirs /opt/gnome-2.16.2/share/omf/gnome-doc-make
/usr/bin/ginstall -c -m 644 gnome-doc-make-C.omf /opt/gnome-2.16.2/share/omf/gnome-doc-make/gnome-doc-make-C.omf
/bin/sh: line 1: scrollkeeper-config: command not found
scrollkeeper-update -p  -o /opt/gnome-2.16.2/share/omf/gnome-doc-make
/bin/sh: line 2: scrollkeeper-config: command not found
/bin/sh: line 2: scrollkeeper-update: command not found
make[3]: *** [install-doc-omf] Error 127
make[3]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/doc/gnome-doc-make'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/doc/gnome-doc-make'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/doc'
make: *** [install-recursive] Error 1
What could it be?


EDIT:

I now also did make check to see what was wrong, and got this:

Code:
db2omf.xml:587: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
db2omf.xml:613: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
db2omf.xml:613: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
db2omf.xml:639: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
db2omf.xml:639: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
db2omf.xml:665: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
db2omf.xml:665: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
db2omf.xml:691: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
db2omf.xml:691: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
db2omf.xml:717: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
db2omf.xml:717: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
db2omf.xml:743: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
db2omf.xml:743: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
db2omf.xml:769: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
db2omf.xml:769: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
gettext.xml:5: element varlistentry: validity error : No declaration for attribute xmlns:fxi of element varlistentry
gettext.xml:5: element varlistentry: validity error : No declaration for attribute xmlns:xi of element varlistentry
gettext.xml:17: element varlistentry: validity error : No declaration for attribute xmlns:fxi of element varlistentry
gettext.xml:17: element varlistentry: validity error : No declaration for attribute xmlns:xi of element varlistentry
gettext.xml:29: element varlistentry: validity error : No declaration for attribute xmlns:fxi of element varlistentry
gettext.xml:29: element varlistentry: validity error : No declaration for attribute xmlns:xi of element varlistentry
gettext.xml:41: element varlistentry: validity error : No declaration for attribute xmlns:fxi of element varlistentry
gettext.xml:41: element varlistentry: validity error : No declaration for attribute xmlns:xi of element varlistentry
gettext.xml:53: element varlistentry: validity error : No declaration for attribute xmlns:fxi of element varlistentry
gettext.xml:53: element varlistentry: validity error : No declaration for attribute xmlns:xi of element varlistentry
gettext.xml:68: element varlistentry: validity error : No declaration for attribute xmlns:fxi of element varlistentry
gettext.xml:68: element varlistentry: validity error : No declaration for attribute xmlns:xi of element varlistentry
gettext.xml:80: element varlistentry: validity error : No declaration for attribute xmlns:fxi of element varlistentry
gettext.xml:80: element varlistentry: validity error : No declaration for attribute xmlns:xi of element varlistentry
gettext.xml:92: element varlistentry: validity error : No declaration for attribute xmlns:fxi of element varlistentry
gettext.xml:92: element varlistentry: validity error : No declaration for attribute xmlns:xi of element varlistentry
gettext.xml:104: element varlistentry: validity error : No declaration for attribute xmlns:fxi of element varlistentry
gettext.xml:104: element varlistentry: validity error : No declaration for attribute xmlns:xi of element varlistentry
gettext.xml:116: element varlistentry: validity error : No declaration for attribute xmlns:fxi of element varlistentry
gettext.xml:116: element varlistentry: validity error : No declaration for attribute xmlns:xi of element varlistentry
gettext.xml:128: element varlistentry: validity error : No declaration for attribute xmlns:fxi of element varlistentry
gettext.xml:128: element varlistentry: validity error : No declaration for attribute xmlns:xi of element varlistentry
gettext.xml:140: element varlistentry: validity error : No declaration for attribute xmlns:fxi of element varlistentry
gettext.xml:140: element varlistentry: validity error : No declaration for attribute xmlns:xi of element varlistentry
gettext.xml:153: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
gettext.xml:153: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
gettext.xml:168: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
gettext.xml:168: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
gettext.xml:183: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
gettext.xml:183: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
gettext.xml:198: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
gettext.xml:198: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
gettext.xml:213: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
gettext.xml:213: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
gettext.xml:228: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
gettext.xml:228: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
gettext.xml:324: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
gettext.xml:324: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
gettext.xml:400: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
gettext.xml:400: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
gettext.xml:466: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
gettext.xml:466: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
gettext.xml:492: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
gettext.xml:492: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
gettext.xml:518: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
gettext.xml:518: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
gettext.xml:544: element refentry: validity error : No declaration for attribute xmlns:fxi of element refentry
gettext.xml:544: element refentry: validity error : No declaration for attribute xmlns:xi of element refentry
Document ./C/gnome-doc-xslt.xml does not validate
make[2]: *** [check-doc-docs] Error 3
make[2]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/doc/xslt'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gnome-doc-utils-0.8.0/doc'
make: *** [check-recursive] Error 1

Last edited by easuter; 12-08-2006 at 04:08 PM.
 
Old 12-08-2006, 07:03 PM   #11
easuter
Member
 
Registered: Dec 2005
Location: Portugal
Distribution: Slackware64 13.0, Slackware64 13.1
Posts: 538

Original Poster
Rep: Reputation: 62
Never mind that last post, i got it working by installing scrollkeeper.

But...now GAILrefuses to compile:

Code:
po" ".deps/gail.Plo"; \
        else rm -f ".deps/gail.Tpo"; exit 1; \
        fi
 gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -DVERSION=\"1.9.3\" -I/usr/include/atk-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/X11R6/include -I/usr/include/libpng12 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/libart-2.0 -O2 -mtune=i686 -march=i586 -Wall -MT gail.lo -MD -MP -MF .deps/gail.Tpo -c gail.c  -fPIC -DPIC -o .libs/gail.o
gail.c: In function `gail_focus_notify':
gail.c:576: error: `ATK_ROLE_REDUNDANT_OBJECT' undeclared (first use in this function)
gail.c:576: error: (Each undeclared identifier is reported only once
gail.c:576: error: for each function it appears in.)
gail.c: In function `gail_focus_tracker':
gail.c:769: error: `ATK_ROLE_REDUNDANT_OBJECT' undeclared (first use in this function)
make[2]: *** [gail.lo] Error 1
make[2]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gail-1.9.3/gail'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_desktop/gail-1.9.3'
make: *** [all] Error 2
 
Old 12-09-2006, 12:54 PM   #12
easuter
Member
 
Registered: Dec 2005
Location: Portugal
Distribution: Slackware64 13.0, Slackware64 13.1
Posts: 538

Original Poster
Rep: Reputation: 62
Never mind that one either :P
I updated ATK to its latest version and it used the gail version from the gnome cvs, and it worked.

But now there is one I'm completely stuck on. I'm trying to compile the gnome Control Center, and when i did ./configure with the proper flags, i got a message saying that i needed HAL...so i use the --disable-hal flag to get arround that.

It starts compiling just fine, but after a few minutes i get this error:

Code:
In file included from /usr/include/dbus-1.0/dbus/dbus-glib-lowlevel.h:28,
                 from sound-properties-capplet.c:42:
/usr/include/dbus-1.0/dbus/dbus.h:30:2: #error "Please define DBUS_API_SUBJ ECT_TO_CHANGE to acknowledge your understanding that D-BUS hasn't reached 1 .0 and is subject to protocol and API churn. See the README for a full expl anation."
sound-properties-capplet.c:342: warning: 'remove_device' defined but not us ed
make[3]: *** [sound-properties-capplet.o] Error 1
make[3]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_ desktop/control-center-2.16.2/capplets/sound'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_ desktop/control-center-2.16.2/capplets'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/easuter/software/source/gnome/gnome_core_ desktop/control-center-2.16.2'
make: *** [all] Error 2
seems like a dbus related issue, but how do i diagnose whats wrong?
 
Old 12-10-2006, 12:55 PM   #13
easuter
Member
 
Registered: Dec 2005
Location: Portugal
Distribution: Slackware64 13.0, Slackware64 13.1
Posts: 538

Original Poster
Rep: Reputation: 62
Since someone else might at some stage have the same problem, I'll keep coming to this thread to report issues + fixes.

I did get Control-Center to compile...eventually.
Ironicaly, the fix came from the #kde freenode channel. i was just ignored in the #gnome channel

Anyway, to get arround that error, it is necessary to upgrade DBUS to 1.0.0 or above. Atention to users with existing DBUS installs: the DBUS tarballs provided at freedesktop no longer have the necessary glib, python and qt bindings included, they must be compiled separately.

Last edited by easuter; 12-10-2006 at 12:56 PM.
 
Old 12-13-2006, 09:01 AM   #14
weibullguy
ReliaFree Maintainer
 
Registered: Aug 2004
Location: Kalamazoo, Michigan
Distribution: Slackware 14.2
Posts: 2,815
Blog Entries: 1

Rep: Reputation: 261Reputation: 261Reputation: 261
All the issues you've had are addressed in the Wiki. Every GNOME package has a list of dependencies and most of the dependencies (all of the required ones) have wiki pages with build instructions. Here is a file that you can use to help you get packages built in an order that will prevent these kind of dependency errors.
 
Old 12-14-2006, 01:16 AM   #15
easuter
Member
 
Registered: Dec 2005
Location: Portugal
Distribution: Slackware64 13.0, Slackware64 13.1
Posts: 538

Original Poster
Rep: Reputation: 62
By the way, I was the one that added DBUS to the dependencies on Control-Center page, because it wasn't there before...
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
gnome 2.14 build problems with garnome openbysource Linux - Software 0 04-20-2006 04:47 AM
Gnome 2.12 build order lukebeales Linux - Software 3 09-13-2005 12:21 PM
problems installing gnome-build-0.1.1 ingerul Linux - Software 2 05-17-2005 07:14 AM
Best way to build GNOME 2.9.x jupitercore Linux - Software 0 11-03-2004 03:49 PM
Gnome Build Trouble... smudge Slackware 2 10-17-2003 04:21 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 12:22 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration