Re: [orca-list] Orca master error in updating a minute ago

[Didier Spaier <didier slint fr>]

Hi Milton,

Check that the binary packages listed in this page be installed:
https://packages.ubuntu.com/source/focal/at-spi2-atk

Caveat: I am not an Ubuntu user. However if I understand well you need
at least libatk-bridge2.0-dev that ships atk-bridge-2.0.pc and a symlink
to the share library, and libatk-bridge2.0-0 that ships the shared
library.

Having also libatk-adaptor won't hurt.

<rant>Why this distribution does not ships the shared library and the
.pc file in the same package is beyond my understanding</rant>

Cheers,
Didier

Le 11/06/2020 à 21:01, Milton via orca-list a écrit :
> Hi all,
>
> I use Ubuntu 20.04 with Orca master 3.37.3pre.
>
> After I did git pull and .autogen.sh I met with an error, I paste below. What can I do to solve it? Thanks 
> in advance.
>
> Milton
>
>
> milton@milton:~/orca$ ./autogen.sh
> **Warning**: I am going to run `configure' with no arguments.
> If you wish to pass any to it, please specify them on the
> `./autogen.sh' command line.
>
> autoreconf: Entering directory `.'
> autoreconf: running: autopoint --force
> autopoint: using AM_GNU_GETTEXT_REQUIRE_VERSION instead of AM_GNU_GETTEXT_VERSION
> autoreconf: running: aclocal --force --warnings=no-portability -I m4 ${ACLOCAL_FLAGS}
> autoreconf: configure.ac: tracing
> autoreconf: configure.ac: not using Libtool
> autoreconf: running: /usr/bin/autoconf --force --warnings=no-portability
> autoreconf: configure.ac: not using Autoheader
> autoreconf: running: automake --add-missing --copy --force-missing --warnings=no-portability
> autoreconf: Leaving directory `.'
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking whether UID '1000' is supported by ustar format... yes
> checking whether GID '1000' is supported by ustar format... yes
> checking how to create a ustar tar archive... gnutar
> checking whether to enable maintainer-specific portions of Makefiles... yes
> checking for a sed that does not truncate output... /usr/bin/sed
> checking whether NLS is requested... yes
> checking for msgfmt... /usr/bin/msgfmt
> checking for gmsgfmt... /usr/bin/msgfmt
> checking for xgettext... /usr/bin/xgettext
> checking for msgmerge... /usr/bin/msgmerge
> checking whether make supports the include directive... yes (GNU style)
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking whether gcc understands -c and -o together... yes
> checking dependency style of gcc... none
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for shared library run path origin... done
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /usr/bin/grep
> checking for egrep... /usr/bin/grep -E
> checking for CFPreferencesCopyAppValue... no
> checking for CFLocaleCopyCurrent... no
> checking for GNU gettext in libc... yes
> checking whether to use NLS... yes
> checking where the gettext function comes from... libc
> checking whether ln -s works... yes
> checking for itstool... itstool
> checking for xmllint... xmllint
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for PYGOBJECT... yes
> checking for ATSPI2... yes
> checking for ATKBRIDGE... no
> configure: error: Package requirements (atk-bridge-2.0 >= 2.26) were not met:
>
> Package 'atk', required by 'atk-bridge-2.0', not found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables ATKBRIDGE_CFLAGS
> and ATKBRIDGE_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> milton@milton:~/orca$
>
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> https://mail.gnome.org/mailman/listinfo/orca-list
> Orca wiki: https://wiki.gnome.org/Projects/Orca
> Orca documentation: https://help.gnome.org/users/orca/stable/
> GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html