Re: [orca-list] How to Get and Use Orca Master



Hello, Mike.

Thanks for the response.

I got the right packages from the Git repository and everything compiles with make except for at-spi2-atk.

Below is what results:

make  all-recursive
make[1]: Entering directory `/home/bob/at-spi2-atk'
Making all in dbind
make[2]: Entering directory `/home/bob/at-spi2-atk/dbind'
/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -DG_LOG_DOMAIN=\"dbind\" -I.. -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -Werror-implicit-function-declaration -MT dbind-any.lo -MD -MP -MF .deps/dbind-any.Tpo -c -o dbind-any.lo dbind-any.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -DG_LOG_DOMAIN=\"dbind\" -I.. -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 -Werror-implicit-function-declaration -MT dbind-any.lo -MD -MP -MF .deps/dbind-any.Tpo -c dbind-any.c -fPIC -DPIC -o .libs/dbind-any.o
mv -f .deps/dbind-any.Tpo .deps/dbind-any.Plo
/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -Werror-implicit-function-declaration -o libdbind.la dbind.lo dbind-any.lo -ldbus-1 -lpthread -lrt -lglib-2.0
libtool: link: rm -fr  .libs/libdbind.a .libs/libdbind.la
libtool: link: ar cru .libs/libdbind.a .libs/dbind.o .libs/dbind-any.o
libtool: link: ranlib .libs/libdbind.a
libtool: link: ( cd ".libs" && rm -f "libdbind.la" && ln -s "../libdbind.la" "libdbind.la" )
make[2]: Leaving directory `/home/bob/at-spi2-atk/dbind'
Making all in droute
make[2]: Entering directory `/home/bob/at-spi2-atk/droute'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/bob/at-spi2-atk/droute'
Making all in atk-adaptor
make[2]: Entering directory `/home/bob/at-spi2-atk/atk-adaptor'
Making all in adaptors
make[3]: Entering directory `/home/bob/at-spi2-atk/atk-adaptor/adaptors'
/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread -I/usr/include/atk-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/at-spi-2.0 -I../.. -I../../atk-adaptor -g -O2 -Werror-implicit-function-declaration -MT libatk_bridge_adaptors_la-accessible-adaptor.lo -MD -MP -MF .deps/libatk_bridge_adaptors_la-accessible-adaptor.Tpo -c -o libatk_bridge_adaptors_la-accessible-adaptor.lo `test -f 'accessible-adaptor.c' || echo './'`accessible-adaptor.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread -I/usr/include/atk-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/at-spi-2.0 -I../.. -I../../atk-adaptor -g -O2 -Werror-implicit-function-declaration -MT libatk_bridge_adaptors_la-accessible-adaptor.lo -MD -MP -MF .deps/libatk_bridge_adaptors_la-accessible-adaptor.Tpo -c accessible-adaptor.c -fPIC -DPIC -o .libs/libatk_bridge_adaptors_la-accessible-adaptor.o accessible-adaptor.c:25:21: fatal error: atk/atk.h: No such file or directory
compilation terminated.
make[3]: *** [libatk_bridge_adaptors_la-accessible-adaptor.lo] Error 1
make[3]: Leaving directory `/home/bob/at-spi2-atk/atk-adaptor/adaptors'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/bob/at-spi2-atk/atk-adaptor'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/bob/at-spi2-atk'
make: *** [all] Error 2

I'm not quite sure where to go next, but it seems like I'm getting there. :)

On 01/07/2012 03:33 PM, Mike Gorse wrote:
It's now split into at-spi2-core, at-spi2-atk, and pyatspi2. If you're building from git, then you should clone and install all of those modules.

-Mike G-

On Sat, 7 Jan 2012, Robert Cole wrote:

Hello, everyone.

I'm sorry for the many questions here, but I just want to lesses as much as possible any risk of messing things up on my system. I just have a few more questions. ATK compiled and installed just fine. Now I ma getting ready to build at-spi. On the Wiki, I am here:

"The following commands provide the sequence of steps you need to follow to download AT-SPI sources from the git repository, build them, and then install them. Punctuation matters with these commands and you should type them exactly as written, with the exception of <<directoryholdingatspiregistry>>. Instead of <<directoryholdingatspiregistry>>, you need to specify the directory where the at-spi-registryd command is installed on your operating system."

I am curious, though. Is at-spi2 in use now? I do not have a directory at /usr/lib/at-spi. I ran the locate command to find the at-spi-registryd file, and it shows up under /usr/lib/at-spi2-core. Now, do I still get at-spi from the GNOME Git repository, or do I need to get something like at-spi2? Or is the at-spi2 code found under at-spi in the Git repository?

I am sorry for all of the dumb questions, but as I said I just want to make sure that everything goes as smoothly as possible.

I'll wait for an answer before continuing on with this one.

Thanks for all of the help so far.
_______________________________________________
orca-list mailing list
orca-list gnome org
http://mail.gnome.org/mailman/listinfo/orca-list
Visit http://live.gnome.org/Orca for more information on Orca.
The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
Log bugs and feature requests at http://bugzilla.gnome.org
Find out how to help at http://live.gnome.org/Orca/HowCanIHelp





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]