Jump to content
  • 0
hellomynameisphil

Failure to build libappindicator

Question

3 answers to this question

Recommended Posts

  • 0

I make a tentative; but i'm on stable:

ci74771ht ~ # USE="-introspection" emerge -1 libappindicator
Calculating dependencies... done!
[ebuild  N    ~] dev-libs/libindicator-12.10.1-r300  USE="{-test}"
[ebuild  N     ] dev-libs/json-glib-1.0.2-r1  USE="-debug -introspection" ABI_X86="(64) -32 (-x32)"
[ebuild  N    ~] dev-libs/libdbusmenu-12.10.2  USE="gtk -debug -introspection" PYTHON_TARGETS="python2_7"
[ebuild  N    ~] dev-libs/libappindicator-12.10.0  USE="-introspection"

The following keyword changes are necessary to proceed:
 (see "package.accept_keywords" in the portage(5) man page for more details)
# required by dev-libs/libappindicator-12.10.0
# required by libappindicator (argument)
=dev-libs/libdbusmenu-12.10.2 ~amd64
# required by dev-libs/libappindicator-12.10.0
# required by libappindicator (argument)
=dev-libs/libindicator-12.10.1-r300 ~amd64
# required by libappindicator (argument)
=dev-libs/libappindicator-12.10.0 ~amd64

Use --autounmask-write to write changes to config files (honoring
CONFIG_PROTECT). Carefully examine the list of proposed changes,
paying special attention to mask or keyword changes that may expose
experimental or unstable packages.
ci74771ht ~ # USE="-introspection" emerge -1 libappindicator --autounmask-write
Calculating dependencies... done!
[ebuild  N    ~] dev-libs/libindicator-12.10.1-r300  USE="{-test}"
[ebuild  N     ] dev-libs/json-glib-1.0.2-r1  USE="-debug -introspection" ABI_X86="(64) -32 (-x32)"
[ebuild  N    ~] dev-libs/libdbusmenu-12.10.2  USE="gtk -debug -introspection" PYTHON_TARGETS="python2_7"
[ebuild  N    ~] dev-libs/libappindicator-12.10.0  USE="-introspection"

The following keyword changes are necessary to proceed:
 (see "package.accept_keywords" in the portage(5) man page for more details)
# required by dev-libs/libappindicator-12.10.0
# required by libappindicator (argument)
=dev-libs/libdbusmenu-12.10.2 ~amd64
# required by dev-libs/libappindicator-12.10.0
# required by libappindicator (argument)
=dev-libs/libindicator-12.10.1-r300 ~amd64
# required by libappindicator (argument)
=dev-libs/libappindicator-12.10.0 ~amd64

Autounmask changes successfully written.

 * IMPORTANT: config file '/etc/portage/package.accept_keywords' needs updating.
 * See the CONFIGURATION FILES section of the emerge
 * man page to learn how to update config files.
ci74771ht ~ # etc-update
Scanning Configuration files...
The following is the list of files which need updating, each
configuration file is followed by a list of possible replacement files.
1) /etc/portage/package.accept_keywords (1)
Please select a file to edit by entering the corresponding number.
              (don't use -3, -5, -7 or -9 if you're unsure what to do)
              (-1 to exit) (-3 to auto merge all files)
                           (-5 to auto-merge AND not use 'mv -i')
                           (-7 to discard all updates)
                           (-9 to discard all updates AND not use 'rm -i'): -5
Replacing /etc/portage/package.accept_keywords with /etc/portage/._cfg0000_package.accept_keywords
Exiting: Nothing left to do; exiting. :)

with my System ("Stable branch") :

>>> Installing (1 of 1) dev-libs/libappindicator-12.10.0
 * Removing /usr/lib/systemd/
 * Removing /lib/systemd/
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.

 * GNU info directory index is up-to-date.

I don't knw if can be of your interesting this experiment. now I do a login in Freenode #funtoo; howevere the ebuid is the same either for "Stable" than "Curent" versions.

 

Ciao :)

Share this post


Link to post
Share on other sites
  • 0

# USE="-introspection" emerge -1 libappindicator

[snip]

="/bin/sh ../libtool"  --include=GObject-2.0 --include=Gtk-3.0   --library=libappindicator3.la  --cflags-begin -I/usr/include/libindicator3-0.4 -I/usr/include/libdbusmenu-gtk3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-3.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/pango-1.0  -I/usr/include/freetype2 -I/usr/include/harfbuzz -I/usr/include/gio-unix-2.0/ -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include   -I. -I../src --cflags-end  app-indicator.c app-indicator.h libappindicator3.la --output AppIndicator3-0.1.gir
Couldn't find include 'Gtk-3.0.gir' (search path: ['.', '/usr/local/share/gir-1.0', '/usr/share/gir-1.0', '/usr/share/gir-1.0', '/usr/share/gir-1.0', '/usr/share/gir-1.0'])
make[2]: *** [AppIndicator3-0.1.gir] Error 1
make[2]: Leaving directory `/var/tmp/portage/dev-libs/libappindicator-12.10.0/work/libappindicator-12.10.0/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/dev-libs/libappindicator-12.10.0/work/libappindicator-12.10.0'
make: *** [all] Error 2
 * ERROR: dev-libs/libappindicator-12.10.0 failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of `emerge --info '=dev-libs/libappindicator-12.10.0'`,
 * the complete build log and the output of `emerge -pqv '=dev-libs/libappindicator-12.10.0'`.
 * The complete build log is located at '/var/tmp/portage/dev-libs/libappindicator-12.10.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/libappindicator-12.10.0/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-libs/libappindicator-12.10.0/work/libappindicator-12.10.0'
 * S: '/var/tmp/portage/dev-libs/libappindicator-12.10.0/work/libappindicator-12.10.0'

>>> Failed to emerge dev-libs/libappindicator-12.10.0, Log file:

>>>  '/var/tmp/portage/dev-libs/libappindicator-12.10.0/temp/build.log'

 * Messages for package dev-libs/libappindicator-12.10.0:

 * ERROR: dev-libs/libappindicator-12.10.0 failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of `emerge --info '=dev-libs/libappindicator-12.10.0'`,
 * the complete build log and the output of `emerge -pqv '=dev-libs/libappindicator-12.10.0'`.
 * The complete build log is located at '/var/tmp/portage/dev-libs/libappindicator-12.10.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/libappindicator-12.10.0/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-libs/libappindicator-12.10.0/work/libappindicator-12.10.0'
 * S: '/var/tmp/portage/dev-libs/libappindicator-12.10.0/work/libappindicator-12.10.0'
 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...