Re: [orca-list] broken accesibility (was help building at-spi)



>Date: Sun, 10 Jan 2010 17:23:39 -0500
>From: William Walker Sun COM
>Subject: Re: [orca-list] broken accesibility (was help building at-spi)
>To: aerospace1028 hotmail com
>CC: orca-list gnome org
>
>Hi:
>
>If you already have the 2.22 packages on your machine, rebuilding/installing them is, at best, going to give you the same thing you already have and, at worst, screw your machine up if you do something incorrectly. :-(  So, if you cannot upgrade to a more recent version >of Ubuntu (I'd highly recommend this since 2.22 is quite old and the Orca you will be using has nowhere near the functionality of Orca 2.28.x), I guess I'd recommend you refresh/reinstall the 2.22 packages from the Ubuntu servers.
>
I realize that the 2.22 branch is antiquated, but it's what I'm using for now.  I *will* be upgrading to lucid in the spring and attempt to keep up with the semi-anual version changes.  But for the moment, Ubuntu Hardy provided a good training ground for getting aclamated to linux.

I know there's not much difference between 2.22.1 and 2.22.3, but I did manage earlier in the summer to get 2.22.3 to successfully build.  After ai accidently broke my system and re-installed, I wanted to make sure I could still get everythin up and running (in prepperation for the future switch to lucid).


>For general GIT usage, you might take a look at http://live.gnome.org/Git/Developers
>
>In looking at that page, it appears as though the "git checkout" commands you are using will not give you the results you expect.  Instead of:
>
>git checkout -b origin/gnome-2-22
>
>You need to do:
>
>git checkout -b gnome-2-22 origin/gnome-2-22
>
Thanks.  That seems to have worked.  i now have the correct 2.22.3 edition of orca.  I'll double check the orca wiki and add this in if fneeded.

Either I misrecorded my notes from last summer, or I got lucky and ended up with orca2.22.3 when first I attempted to build from git:-)

>Note also that just running autogen.sh by itself is not going to be enough.  You'll need to use --prefix, --libexecdir, and --sysconfdir options to get things to install to the proper locations.  Hardy is quite old and I cannot remember the exact places it put things, so I can >only guess that you might want:
>
>./autogen.sh --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib/at-spi
>
Sorry, I have been using the prefix and libexecdir flags with autogen.sh.  I added in the sysconfdir flag just to be safe.  I had meant I was running autogen.sh with the correct flags as recommended on the orca wiki.  Sorry for the ambiguity.

Thanks for all the help:-)

Hotmail: Powerful Free email with security by Microsoft. Get it now.


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