| View previous topic :: View next topic |
| Author |
Message |
Thistled
Guru
Joined: 06 Jan 2011
Posts: 572
Location: Scotland
|
 Posted: Tue Apr 12, 2011 8:13 am Post subject: |
 |
|
Okay, well I seem to have about 95% of it installed and running. I get stuck at Empathy-3.0.0.
It bricks because I can't get the new gnome-keyring-3.0.0 installed.
gnome-keyring-3.0.0 fails every time. (as does 3.0.0-r300)
| Code: | Making all in gcr
make[2]: Entering directory `/var/tmp/portage/gnome-base/gnome-keyring-3.0.0-r300/work/gnome-keyring-3.0.0/gcr'
Makefile:379: *** commands commence before first target. Stop. |
Any ideas?
_________________
Whatever you do, do it properly! |
|
| Back to top |
|
 |
Thistled
Guru
Joined: 06 Jan 2011
Posts: 572
Location: Scotland
|
| Posted: Tue Apr 12, 2011 12:33 pm Post subject: |
|
|
** UPDATE **
All working now, thanks to Gilles Dartiguelongue at the Gnome overlay.
The NEW gnome-keyring (using gtk3) now installs the appropriate gcr-3 file, and now empathy installs.
All done now.
Thanks Gilles!!
_________________
Whatever you do, do it properly! |
|
| Back to top |
|
|
ComaWhite
Tux's lil' helper
Joined: 07 Oct 2008
Posts: 125
|
| Posted: Tue Apr 12, 2011 10:01 pm Post subject: |
|
|
Anyone know how to get libgweather to compile?
| Quote: |
>>> Emerging (1 of 1) dev-libs/libgweather-3.0.0 from gnome
* libgweather-3.0.0.tar.bz2 RMD160 SHA1 SHA256 size  ... [ ok ]
* Package: dev-libs/libgweather-3.0.0
* Repository: gnome
* USE: amd64 elibc_glibc introspection kernel_linux multilib userland_GNU
* FEATURES: ccache nostrip preserve-libs sandbox splitdebug userpriv usersandbox
>>> Unpacking source...
>>> Unpacking libgweather-3.0.0.tar.bz2 to /var/tmp/portage/dev-libs/libgweather-3.0.0/work
>>> Source unpacked in /var/tmp/portage/dev-libs/libgweather-3.0.0/work
>>> Preparing source in /var/tmp/portage/dev-libs/libgweather-3.0.0/work/libgweather-3.0.0 ...
* Fixing OMF Makefiles ... [ ok ]
* Running elibtoolize in: libgweather-3.0.0/
* Applying portage-2.2.patch ...
* Applying sed-1.5.6.patch ...
* Applying as-needed-2.2.6.patch ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-libs/libgweather-3.0.0/work/libgweather-3.0.0 ...
* econf: updating libgweather-3.0.0/config.sub with /usr/share/gnuconfig/config.sub
* econf: updating libgweather-3.0.0/config.guess with /usr/share/gnuconfig/config.guess
./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --enable-locations-compression --disable-maintainer-mode --disable-all-translations-in-one-xml --disable-static --enable-introspection --disable-gtk-doc
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for Win32... no
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether NLS is requested... yes
checking for style of include used by make... GNU
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-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 x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking dependency style of x86_64-pc-linux-gnu-gcc... gcc3
checking for intltool >= 0.40.3... 0.41.1 found
checking for intltool-update... /usr/bin/intltool-update
checking for intltool-merge... /usr/bin/intltool-merge
checking for intltool-extract... /usr/bin/intltool-extract
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/gmsgfmt
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.12.3
checking for XML::Parser... ok
checking for x86_64-pc-linux-gnu-pkg-config... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.19... yes
checking for x86_64-pc-linux-gnu-gcc... (cached) x86_64-pc-linux-gnu-gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... (cached) yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... (cached) none needed
checking dependency style of x86_64-pc-linux-gnu-gcc... (cached) gcc3
checking whether x86_64-pc-linux-gnu-gcc and cc understand -c and -o together... yes
checking for library containing strerror... none required
checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for a sed that does not truncate output... /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by x86_64-pc-linux-gnu-gcc... /usr/x86_64-pc-linux-gnu/bin/ld
checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/x86_64-pc-linux-gnu/bin/ld option to reload object files... -r
checking for x86_64-pc-linux-gnu-objdump... x86_64-pc-linux-gnu-objdump
checking how to recognize dependent libraries... pass_all
checking for x86_64-pc-linux-gnu-ar... x86_64-pc-linux-gnu-ar
checking for x86_64-pc-linux-gnu-strip... x86_64-pc-linux-gnu-strip
checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib
checking command to parse /usr/bin/nm -B output from x86_64-pc-linux-gnu-gcc object... ok
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if x86_64-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
checking for x86_64-pc-linux-gnu-gcc option to produce PIC... -fPIC -DPIC
checking if x86_64-pc-linux-gnu-gcc PIC flag -fPIC -DPIC works... yes
checking if x86_64-pc-linux-gnu-gcc static flag -static works... yes
checking if x86_64-pc-linux-gnu-gcc supports -c -o file.o... yes
checking if x86_64-pc-linux-gnu-gcc supports -c -o file.o... (cached) yes
checking whether the x86_64-pc-linux-gnu-gcc linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for gconftool-2... /usr/bin/gconftool-2
checking what warning flags to pass to the C compiler... -Wall -Wmissing-prototypes
checking what language compliance flags to pass to the C compiler...
checking for more warnings... no
checking for GTK... yes
checking for LIBXML... yes
checking for LIBSOUP_GNOME... yes
checking for GCONF... yes
Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation
Using $(sysconfdir)/gconf/schemas as install directory for schema files
checking for x86_64-pc-linux-gnu-pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.16... yes
checking for GLIB - version >= 2.13.0... yes (version 2.28.5)
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for ngettext in libc... yes
checking for dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... (cached) /usr/bin/msgfmt
checking for dcgettext... yes
checking if msgfmt accepts -c... yes
checking for gmsgfmt... (cached) /usr/bin/gmsgfmt
checking for xgettext... (cached) /usr/bin/xgettext
checking for regexec... yes
checking for struct tm.tm_gmtoff... yes
checking for _NL_MEASUREMENT_MEASUREMENT... yes
checking for gtkdoc-check... no
checking for gtkdoc-rebase... /usr/bin/gtkdoc-rebase
checking for gtkdoc-mkpdf... no
checking whether to build gtk-doc documentation... no
checking for gobject-introspection... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating doc/Makefile
config.status: creating po/Makefile.in
config.status: creating po-locations/Makefile
config.status: creating libgweather/Makefile
config.status: creating libgweather/gweather-3.0.pc
config.status: creating libgweather/gweather-3.0-uninstalled.pc
config.status: creating data/Makefile
config.status: creating icons/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing default-1 commands
config.status: executing po/stamp-it commands
libgweather-3.0.0 configure summary:
Prefix: /usr
Source code location: .
Compiler: x86_64-pc-linux-gnu-gcc
Introspection support: yes
Locations.xml translations: one big file
Locations.xml compression: yes
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-libs/libgweather-3.0.0/work/libgweather-3.0.0 ...
make -j9
make all-recursive
make[1]: Entering directory `/var/tmp/portage/dev-libs/libgweather-3.0.0/work/libgweather-3.0.0'
Making all in libgweather
make[2]: Entering directory `/var/tmp/portage/dev-libs/libgweather-3.0.0/work/libgweather-3.0.0/libgweather'
make all-am
make[3]: Entering directory `/var/tmp/portage/dev-libs/libgweather-3.0.0/work/libgweather-3.0.0/libgweather'
CC libgweather_3_la-weather.lo
CC libgweather_3_la-weather-metar.lo
CC libgweather_3_la-weather-iwin.lo
CC libgweather_3_la-weather-met.lo
CC libgweather_3_la-weather-bom.lo
CC libgweather_3_la-weather-wx.lo
CC libgweather_3_la-weather-sun.lo
CC libgweather_3_la-weather-moon.lo
CC libgweather_3_la-gweather-enum-types.lo
CC libgweather_3_la-gweather-prefs.lo
CC libgweather_3_la-gweather-gconf.lo
CC libgweather_3_la-gweather-xml.lo
CC libgweather_3_la-gweather-location.lo
CC libgweather_3_la-gweather-timezone.lo
CC libgweather_3_la-location-entry.lo
CC libgweather_3_la-timezone-menu.lo
CC libgweather_3_la-parser.lo
CC test_metar-test_metar.o
CC test_locations.o
CC test_sun_moon-test_sun_moon.o
LC_ALL=C /usr/bin/intltool-merge -s -u -c ../po/.intltool-merge-cache ../po gweather.schemas.in gweather.schemas
Generating and caching the translation database
CCLD libgweather-3.la
Merging translations into gweather.schemas.
CCLD test_metar
GISCAN GWeather-3.0.gir
CCLD test_locations
CCLD test_sun_moon
<unknown>:: Warning: GWeather: Unknown namespace for identifier 'WeatherLocation'
weather.h:50: Warning: GWeather: symbol='WeatherLocation': Unknown namespace for identifier 'WeatherLocation'
weather.h:52: Warning: GWeather: symbol='weather_location_new': Unknown namespace for symbol 'weather_location_new'
weather.h:59: Warning: GWeather: symbol='weather_location_clone': Unknown namespace for symbol 'weather_location_clone'
weather.h:60: Warning: GWeather: symbol='weather_location_free': Unknown namespace for symbol 'weather_location_free'
weather.h:61: Warning: GWeather: symbol='weather_location_equal': Unknown namespace for symbol 'weather_location_equal'
weather.h:72: Warning: GWeather: symbol='WeatherForecastType': Unknown namespace for identifier 'WeatherForecastType'
weather.h:80: Warning: GWeather: symbol='TempUnit': Unknown namespace for identifier 'TempUnit'
weather.h:90: Warning: GWeather: symbol='SpeedUnit': Unknown namespace for identifier 'SpeedUnit'
weather.h:101: Warning: GWeather: symbol='PressureUnit': Unknown namespace for identifier 'PressureUnit'
weather.h:109: Warning: GWeather: symbol='DistanceUnit': Unknown namespace for identifier 'DistanceUnit'
<unknown>:: Warning: GWeather: Unknown namespace for identifier 'WeatherPrefs'
weather.h:123: Warning: GWeather: symbol='WeatherPrefs': Unknown namespace for identifier 'WeatherPrefs'
weather.h:129: Warning: GWeather: symbol='WeatherInfo': Unknown namespace for identifier 'WeatherInfo'
<unknown>:: Warning: GWeather: Unknown namespace for identifier 'WeatherInfoFunc'
weather.h:141: Warning: GWeather: symbol='weather_info_abort': Unknown namespace for symbol 'weather_info_abort'
weather.h:142: Warning: GWeather: symbol='weather_info_clone': Unknown namespace for symbol 'weather_info_clone'
weather.h:143: Warning: GWeather: symbol='weather_info_free': Unknown namespace for symbol 'weather_info_free'
weather.h:145: Warning: GWeather: symbol='weather_info_is_valid': Unknown namespace for symbol 'weather_info_is_valid'
weather.h:146: Warning: GWeather: symbol='weather_info_network_error': Unknown namespace for symbol 'weather_info_network_error'
weather.h:148: Warning: GWeather: symbol='weather_info_to_metric': Unknown namespace for symbol 'weather_info_to_metric'
weather.h:149: Warning: GWeather: symbol='weather_info_to_imperial': Unknown namespace for symbol 'weather_info_to_imperial'
weather.h:151: Warning: GWeather: symbol='weather_info_get_location': Unknown namespace for symbol 'weather_info_get_location'
weather.h:152: Warning: GWeather: symbol='weather_info_get_location_name': Unknown namespace for symbol 'weather_info_get_location_name'
weather.h:153: Warning: GWeather: symbol='weather_info_get_update': Unknown namespace for symbol 'weather_info_get_update'
weather.h:154: Warning: GWeather: symbol='weather_info_get_sky': Unknown namespace for symbol 'weather_info_get_sky'
weather.h:155: Warning: GWeather: symbol='weather_info_get_conditions': Unknown namespace for symbol 'weather_info_get_conditions'
weather.h:156: Warning: GWeather: symbol='weather_info_get_temp': Unknown namespace for symbol 'weather_info_get_temp'
weather.h:157: Warning: GWeather: symbol='weather_info_get_temp_min': Unknown namespace for symbol 'weather_info_get_temp_min'
weather.h:158: Warning: GWeather: symbol='weather_info_get_temp_max': Unknown namespace for symbol 'weather_info_get_temp_max'
weather.h:159: Warning: GWeather: symbol='weather_info_get_dew': Unknown namespace for symbol 'weather_info_get_dew'
weather.h:160: Warning: GWeather: symbol='weather_info_get_humidity': Unknown namespace for symbol 'weather_info_get_humidity'
weather.h:161: Warning: GWeather: symbol='weather_info_get_wind': Unknown namespace for symbol 'weather_info_get_wind'
weather.h:162: Warning: GWeather: symbol='weather_info_get_pressure': Unknown namespace for symbol 'weather_info_get_pressure'
weather.h:163: Warning: GWeather: symbol='weather_info_get_visibility': Unknown namespace for symbol 'weather_info_get_visibility'
weather.h:164: Warning: GWeather: symbol='weather_info_get_apparent': Unknown namespace for symbol 'weather_info_get_apparent'
weather.h:165: Warning: GWeather: symbol='weather_info_get_sunrise': Unknown namespace for symbol 'weather_info_get_sunrise'
weather.h:166: Warning: GWeather: symbol='weather_info_get_sunset': Unknown namespace for symbol 'weather_info_get_sunset'
weather.h:167: Warning: GWeather: symbol='weather_info_get_forecast': Unknown namespace for symbol 'weather_info_get_forecast'
weather.h:168: Warning: GWeather: symbol='weather_info_get_forecast_list': Unknown namespace for symbol 'weather_info_get_forecast_list'
weather.h:169: Warning: GWeather: symbol='weather_info_get_radar': Unknown namespace for symbol 'weather_info_get_radar'
weather.h:171: Warning: GWeather: symbol='weather_info_get_temp_summary': Unknown namespace for symbol 'weather_info_get_temp_summary'
weather.h:172: Warning: GWeather: symbol='weather_info_get_weather_summary': Unknown namespace for symbol 'weather_info_get_weather_summary'
weather.h:174: Warning: GWeather: symbol='weather_info_get_icon_name': Unknown namespace for symbol 'weather_info_get_icon_name'
weather.h:175: Warning: GWeather: symbol='weather_info_next_sun_event': Unknown namespace for symbol 'weather_info_next_sun_event'
weather.h:189: Warning: GWeather: symbol='WeatherWindDirection': Unknown namespace for identifier 'WeatherWindDirection'
weather.h:201: Warning: GWeather: symbol='WeatherSky': Unknown namespace for identifier 'WeatherSky'
weather.h:237: Warning: GWeather: symbol='WeatherConditionPhenomenon': Unknown namespace for identifier 'WeatherConditionPhenomenon'
weather.h:261: Warning: GWeather: symbol='WeatherConditionQualifier': Unknown namespace for identifier 'WeatherConditionQualifier'
<unknown>:: Warning: GWeather: Unknown namespace for identifier 'WeatherMoonPhase'
<unknown>:: Warning: GWeather: Unknown namespace for identifier 'WeatherMoonLatitude'
weather.h:265: Warning: GWeather: symbol='weather_info_get_value_update': Unknown namespace for symbol 'weather_info_get_value_update'
weather.h:266: Warning: GWeather: symbol='weather_info_get_value_sky': Unknown namespace for symbol 'weather_info_get_value_sky'
weather.h:267: Warning: GWeather: symbol='weather_info_get_value_conditions': Unknown namespace for symbol 'weather_info_get_value_conditions'
weather.h:268: Warning: GWeather: symbol='weather_info_get_value_temp': Unknown namespace for symbol 'weather_info_get_value_temp'
weather.h:269: Warning: GWeather: symbol='weather_info_get_value_temp_min': Unknown namespace for symbol 'weather_info_get_value_temp_min'
weather.h:270: Warning: GWeather: symbol='weather_info_get_value_temp_max': Unknown namespace for symbol 'weather_info_get_value_temp_max'
weather.h:271: Warning: GWeather: symbol='weather_info_get_value_dew': Unknown namespace for symbol 'weather_info_get_value_dew'
weather.h:272: Warning: GWeather: symbol='weather_info_get_value_apparent': Unknown namespace for symbol 'weather_info_get_value_apparent'
weather.h:273: Warning: GWeather: symbol='weather_info_get_value_wind': Unknown namespace for symbol 'weather_info_get_value_wind'
weather.h:274: Warning: GWeather: symbol='weather_info_get_value_pressure': Unknown namespace for symbol 'weather_info_get_value_pressure'
weather.h:275: Warning: GWeather: symbol='weather_info_get_value_visibility': Unknown namespace for symbol 'weather_info_get_value_visibility'
weather.h:276: Warning: GWeather: symbol='weather_info_get_value_sunrise': Unknown namespace for symbol 'weather_info_get_value_sunrise'
weather.h:277: Warning: GWeather: symbol='weather_info_get_value_sunset': Unknown namespace for symbol 'weather_info_get_value_sunset'
weather.h:278: Warning: GWeather: symbol='weather_info_get_value_moonphase': Unknown namespace for symbol 'weather_info_get_value_moonphase'
weather.h:279: Warning: GWeather: symbol='weather_info_get_upcoming_moonphases': Unknown namespace for symbol 'weather_info_get_upcoming_moonphases'
weather.h:44: Warning: GWeather: symbol='MOON_PHASES': Unknown namespace for symbol 'MOON_PHASES'
gweather-timezone.h:57: Warning: GWeather: symbol='TZ_TTINFO_ISDST_OFFSET': Unknown namespace for symbol 'TZ_TTINFO_ISDST_OFFSET'
(process:20717): GLib-GObject-CRITICAL **: gtype.c:2712: You forgot to call g_type_init()
(process:20717): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(process:20717): GLib-GObject-CRITICAL **: gtype.c:2712: You forgot to call g_type_init()
(process:20717): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(process:20717): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
Command '['/var/tmp/portage/dev-libs/libgweather-3.0.0/work/libgweather-3.0.0/libgweather/tmp-introspectwidiDm/GWeather-3.0', '--introspect-dump=/var/tmp/portage/dev-libs/libgweather-3.0.0/work/libgweather-3.0.0/libgweather/tmp-introspectwidiDm/types.txt,/var/tmp/portage/dev-libs/libgweather-3.0.0/work/libgweather-3.0.0/libgweather/tmp-introspectwidiDm/dump.xml']' returned non-zero exit status -11
make[3]: *** [GWeather-3.0.gir] Error 1
make[3]: Leaving directory `/var/tmp/portage/dev-libs/libgweather-3.0.0/work/libgweather-3.0.0/libgweather'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/var/tmp/portage/dev-libs/libgweather-3.0.0/work/libgweather-3.0.0/libgweather'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/dev-libs/libgweather-3.0.0/work/libgweather-3.0.0'
make: *** [all] Error 2
emake failed
* ERROR: dev-libs/libgweather-3.0.0 failed (compile phase):
* compile failure
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 3106: Called gnome2_src_compile
* environment, line 2394: Called die
* The specific snippet of code:
* emake || die "compile failure"
*
* If you need support, post the output of 'emerge --info =dev-libs/libgweather-3.0.0',
* the complete build log and the output of 'emerge -pqv =dev-libs/libgweather-3.0.0'.
* This ebuild used the following eclasses from overlays:
* /var/lib/layman/gnome/eclass/gnome2.eclass
* This ebuild is from an overlay named 'gnome': '/var/lib/layman/gnome/'
* The complete build log is located at '/var/tmp/portage/dev-libs/libgweather-3.0.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-libs/libgweather-3.0.0/temp/environment'.
* S: '/var/tmp/portage/dev-libs/libgweather-3.0.0/work/libgweather-3.0.0'
>>> Failed to emerge dev-libs/libgweather-3.0.0, Log file:
>>> '/var/tmp/portage/dev-libs/libgweather-3.0.0/temp/build.log'
* Messages for package dev-libs/libgweather-3.0.0:
* ERROR: dev-libs/libgweather-3.0.0 failed (compile phase):
* compile failure
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 3106: Called gnome2_src_compile
* environment, line 2394: Called die
* The specific snippet of code:
* emake || die "compile failure"
*
* If you need support, post the output of 'emerge --info =dev-libs/libgweather-3.0.0',
* the complete build log and the output of 'emerge -pqv =dev-libs/libgweather-3.0.0'.
* This ebuild used the following eclasses from overlays:
* /var/lib/layman/gnome/eclass/gnome2.eclass
* This ebuild is from an overlay named 'gnome': '/var/lib/layman/gnome/'
* The complete build log is located at '/var/tmp/portage/dev-libs/libgweather-3.0.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-libs/libgweather-3.0.0/temp/environment'.
* S: '/var/tmp/portage/dev-libs/libgweather-3.0.0/work/libgweather-3.0.0'
|
|
|
| Back to top |
|
|
Thistled
Guru
Joined: 06 Jan 2011
Posts: 572
Location: Scotland
|
| Posted: Wed Apr 13, 2011 8:50 am Post subject: |
|
|
| mostermand wrote: | | Quote: | I want to try gnome 3 from the gnome repository, and I'm receiving the following error when emerging gtk+-9999:
<<<<<
* GIT NEW clone -->
* repository: git://git.gnome.org
Cloning into bare repository /usr/portage/distfiles/git-src/gtk+...
fatal: Unable to look up (port 9418) (Name or service not known)
>>>>> |
Manually setting setting EGIT_REPO_URI=git://git.gnome.org/<package> worked for me. |
Is there any chance you could explain how to do this in simple terms.
Where, for example, do I set EGIT_REPO.
I'm new to this, I'm used to portage doing all of this, but in this instance it wont do it.
Any help would be appreciated.
_________________
Whatever you do, do it properly! |
|
| Back to top |
|
|
Thistled
Guru
Joined: 06 Jan 2011
Posts: 572
Location: Scotland
|
| Posted: Wed Apr 13, 2011 9:07 am Post subject: |
|
|
@ComaWhite
I would suggest you get the latest glib and gobject-introspection then try again.
_________________
Whatever you do, do it properly! |
|
| Back to top |
|
|
cau
n00b
Joined: 10 Apr 2011
Posts: 3
|
| Posted: Wed Apr 13, 2011 10:59 am Post subject: |
|
|
@Thistled
Go to "/var/lib/layman/gnome" and you will find all the ebuilds for the gnome overlay. Edit the ebuild and add "EGIT_REPO_URI=git://git.gnome.org/<package>" |
|
| Back to top |
|
|
rajackar
n00b
Joined: 09 Nov 2010
Posts: 15
|
| Posted: Wed Apr 13, 2011 3:38 pm Post subject: |
|
|
| Thistled wrote: | ** UPDATE **
All working now, thanks to Gilles Dartiguelongue at the Gnome overlay.
The NEW gnome-keyring (using gtk3) now installs the appropriate gcr-3 file, and now empathy installs.
All done now.
Thanks Gilles!! |
Can you let me know what you did to fix it?
I stil l can't emerge gnome-keyring-3.0.0-r300
I think this is the error:
Makefile:379: *** recipe commences before first target. Stop. |
|
| Back to top |
|
|
Thistled
Guru
Joined: 06 Jan 2011
Posts: 572
Location: Scotland
|
| Posted: Thu Apr 14, 2011 7:20 pm Post subject: |
|
|
Apologies for the delay, I have been looking through my logs to see what I have done.
Make sure you have the Gnu C Compiler (GCC) at version 4.5.2
The specific version of the keyring you are trying to compile, should be successful with that version of GCC.
Check the Gentoo GCC upgrade guide for details on what you have to do, but fear not, it's not a big job.
http://www.gentoo.org/doc/en/gcc-upgrading.xml
_________________
Whatever you do, do it properly! |
|
| Back to top |
|
|
Thistled
Guru
Joined: 06 Jan 2011
Posts: 572
Location: Scotland
|
| Posted: Thu Apr 14, 2011 7:24 pm Post subject: |
|
|
| cau wrote: | @Thistled
Go to "/var/lib/layman/gnome" and you will find all the ebuilds for the gnome overlay. Edit the ebuild and add "EGIT_REPO_URI=git://git.gnome.org/<package>" |
Cheers Cau, I noticed that from another post and it worked a treat. Cheers.
_________________
Whatever you do, do it properly! |
|
| Back to top |
|
|
monsm
Guru
Joined: 26 Sep 2007
Posts: 467
Location: London, UK
|
| Posted: Thu Apr 14, 2011 7:48 pm Post subject: |
|
|
Hi,
As I type I have only 10 more packages to go, so almost there.
One problem. I got a compile failure for evolution-3.0.0. It complained about something in libebook (I think), which I think is in evolution-data-server. I have successfully emerged v 3.0.0 of that one. So what is going on with evolution?
Anyone else found this problem and a solution to it?
Mons |
|
| Back to top |
|
|
Thistled
Guru
Joined: 06 Jan 2011
Posts: 572
Location: Scotland
|
| Posted: Thu Apr 14, 2011 8:02 pm Post subject: |
|
|
| monsm wrote: | Hi,
As I type I have only 10 more packages to go, so almost there.
One problem. I got a compile failure for evolution-3.0.0. It complained about something in libebook (I think), which I think is in evolution-data-server. I have successfully emerged v 3.0.0 of that one. So what is going on with evolution?
Anyone else found this problem and a solution to it?
Mons |
You are right about "libebook", that comes from EDS (Evolution Data Server)
Try adding this to /etc/portage/package.use
| Code: | | gnome-extra/evolution-data-server gnome-keyring |
Then try to emerge it with the --newuse flag.
You SHOULD be able to continue with the evolution install.
I'm just about to double check my logs, but it seems like that what fixed it for me.
_________________
Whatever you do, do it properly! |
|
| Back to top |
|
|
rajackar
n00b
Joined: 09 Nov 2010
Posts: 15
|
| Posted: Sat Apr 16, 2011 1:05 pm Post subject: |
|
|
| Thistled wrote: | Apologies for the delay, I have been looking through my logs to see what I have done.
Make sure you have the Gnu C Compiler (GCC) at version 4.5.2
The specific version of the keyring you are trying to compile, should be successful with that version of GCC.
Check the Gentoo GCC upgrade guide for details on what you have to do, but fear not, it's not a big job.
http://www.gentoo.org/doc/en/gcc-upgrading.xml |
Hmm, it's kind of weird. I'm using this version and I'm still getting the exact same error you posted earlier while compiling gnome-keyring.
Is there anything else you might have done to fix this? |
|
| Back to top |
|
|
Thistled
Guru
Joined: 06 Jan 2011
Posts: 572
Location: Scotland
|
| Posted: Sat Apr 16, 2011 4:46 pm Post subject: |
|
|
@rajackbar
Did you follow the gcc guide. i.e. use the gcc-config command afterwards?
This will ensure the new keyring is compiled with the new GCC.
After adding the gnome-keyring flag to E-D-S in /etc/portage/package.use ,
did you try...
| Code: | | emerge --newuse -v world |
?
If the above is still unsatisfactory, the try re-emerging in this order
| Code: | gnome-extra/evolution-data-server-3.0.0
dev-libs/libgcrypt-1.5.0_beta1-r1
gnome-base/gnome-session-3.0.0
gnome-base/gnome-settings-daemon-3.0.0.1
gnome-base/libgnome-keyring-3.0.0
gnome-base/gnome-keyring-3.0.0-r300 |
I'm going to have another look at the logs again. It's about 2 1/2 days worth.
If it jumps out at me, I'll update.
_________________
Whatever you do, do it properly! |
|
| Back to top |
|
|
rajackar
n00b
Joined: 09 Nov 2010
Posts: 15
|
| Posted: Sat Apr 16, 2011 5:41 pm Post subject: |
|
|
Thanks for the help!
I Followed the upgrade guide and gcc-config -l outputs: [1] x86_64-pc-linux-gnu-4.5.2 *
I tried emerging in the order you suggested but e-d-s and libgnome-keyring won't emerge as the report gnome-keyring as a dependency.
I'm kinda new to all this so it might be something obvious that I'm oblivious to. |
|
| Back to top |
|
|
Thistled
Guru
Joined: 06 Jan 2011
Posts: 572
Location: Scotland
|
| Posted: Sat Apr 16, 2011 5:48 pm Post subject: |
|
|
What happens when you...
| Code: | | emerge --newuse -v world |
_________________
Whatever you do, do it properly! |
|
| Back to top |
|
|
rajackar
n00b
Joined: 09 Nov 2010
Posts: 15
|
| Posted: Sat Apr 16, 2011 5:57 pm Post subject: |
|
|
| Code: | Olivier-gentoo ~ # emerge --newuse -v world
These are the packages that would be merged, in order:
Calculating dependencies... done!
Total: 0 packages, Size of downloads: 0 kB
>>> Jobs: 0 of 0 complete Load avg: 0.25, 0.48, 0.60
>>> Auto-cleaning packages...
>>> No outdated packages were found on your system.
|
That looks ok right?
By the way, I haven't unmerged the older gcc yet because I'm not sure of the version. Is there any way to check if the 4.5.2 version is actually used? |
|
| Back to top |
|
|
Thistled
Guru
Joined: 06 Jan 2011
Posts: 572
Location: Scotland
|
| Posted: Sat Apr 16, 2011 6:21 pm Post subject: |
|
|
That is looking good for emerge --newuse world.
According to my logs, I could only get gnome-keyring to build once I had updated evolution-data-server. That was not possible until I emerged GCC-4.5.2
The problem for me was my system was missing "gcr3" and gnome-keyring would fail to build until I had the package gcr-3 installed.
I was having build issues with a few other packages, and that was fixed by using (updating) to gcc-4.5.2
I am going to have a look at different build logs now and see if I can discover what one actually created the 'gcr-3' package, as that is what gnome-keyring needs.
Stick around man, I'll try my best to nail this for ya.
_________________
Whatever you do, do it properly! |
|
| Back to top |
|
|
Thistled
Guru
Joined: 06 Jan 2011
Posts: 572
Location: Scotland
|
| Posted: Sat Apr 16, 2011 6:32 pm Post subject: |
|
|
At the top of the page it seems as if I mention the gnome-keyring builds using the new gtk3 use flag.
So, try this..
go to /etc/portage/package.use and add the following line to look like this...
| Code: | | gnome-base/gnome-keyring gtk3 |
then
| Code: | | emerge --newuse evolution-data-server gnome-keyring |
_________________
Whatever you do, do it properly! |
|
| Back to top |
|
|
Thistled
Guru
Joined: 06 Jan 2011
Posts: 572
Location: Scotland
|
| Posted: Sat Apr 16, 2011 7:37 pm Post subject: |
|
|
Here's the part of the log that tells me updating the GCC to 4.5.2 nails it. (as you have already done)
| Code: | 1302605644: Started emerge on: Apr 12, 2011 11:54:04
1302605644: *** emerge --deep --update --verbose system
1302605654: >>> emerge (1 of 6) app-shells/bash-4.2_p8 to /
1302605654: === (1 of 6) Cleaning (app-shells/bash-4.2_p8::/mnt/nfs_portage/app-shells/bash/bash-4.2_p8.ebuild)
1302605694: === (1 of 6) Compiling/Merging (app-shells/bash-4.2_p8::/mnt/nfs_portage/app-shells/bash/bash-4.2_p8.ebuild)
1302605772: === (1 of 6) Merging (app-shells/bash-4.2_p8::/mnt/nfs_portage/app-shells/bash/bash-4.2_p8.ebuild)
1302605775: >>> AUTOCLEAN: app-shells/bash:0
1302605775: === Unmerging... (app-shells/bash-4.1_p9)
1302605776: >>> unmerge success: app-shells/bash-4.1_p9
1302605777: === (1 of 6) Post-Build Cleaning (app-shells/bash-4.2_p8::/mnt/nfs_portage/app-shells/bash/bash-4.2_p8.ebuild)
1302605777: ::: completed emerge (1 of 6) app-shells/bash-4.2_p8 to /
1302605777: >>> emerge (2 of 6) dev-libs/mpc-0.8.2 to /
1302605777: === (2 of 6) Cleaning (dev-libs/mpc-0.8.2::/mnt/nfs_portage/dev-libs/mpc/mpc-0.8.2.ebuild)
1302605778: === (2 of 6) Compiling/Merging (dev-libs/mpc-0.8.2::/mnt/nfs_portage/dev-libs/mpc/mpc-0.8.2.ebuild)
1302605799: === (2 of 6) Merging (dev-libs/mpc-0.8.2::/mnt/nfs_portage/dev-libs/mpc/mpc-0.8.2.ebuild)
1302605801: >>> AUTOCLEAN: dev-libs/mpc:0
1302605802: === (2 of 6) Post-Build Cleaning (dev-libs/mpc-0.8.2::/mnt/nfs_portage/dev-libs/mpc/mpc-0.8.2.ebuild)
1302605802: ::: completed emerge (2 of 6) dev-libs/mpc-0.8.2 to /
1302605802: >>> emerge (3 of 6) sys-apps/sandbox-2.5 to /
1302605802: === (3 of 6) Cleaning (sys-apps/sandbox-2.5::/mnt/nfs_portage/sys-apps/sandbox/sandbox-2.5.ebuild)
1302605802: === (3 of 6) Compiling/Merging (sys-apps/sandbox-2.5::/mnt/nfs_portage/sys-apps/sandbox/sandbox-2.5.ebuild)
1302605829: === (3 of 6) Merging (sys-apps/sandbox-2.5::/mnt/nfs_portage/sys-apps/sandbox/sandbox-2.5.ebuild)
1302605831: >>> AUTOCLEAN: sys-apps/sandbox:0
1302605831: === Unmerging... (sys-apps/sandbox-2.4)
1302605832: >>> unmerge success: sys-apps/sandbox-2.4
1302605833: === (3 of 6) Post-Build Cleaning (sys-apps/sandbox-2.5::/mnt/nfs_portage/sys-apps/sandbox/sandbox-2.5.ebuild)
1302605833: ::: completed emerge (3 of 6) sys-apps/sandbox-2.5 to /
1302605833: >>> emerge (4 of 6) sys-devel/make-3.82 to /
1302605833: === (4 of 6) Cleaning (sys-devel/make-3.82::/mnt/nfs_portage/sys-devel/make/make-3.82.ebuild)
1302605833: === (4 of 6) Compiling/Merging (sys-devel/make-3.82::/mnt/nfs_portage/sys-devel/make/make-3.82.ebuild)
1302605854: === (4 of 6) Merging (sys-devel/make-3.82::/mnt/nfs_portage/sys-devel/make/make-3.82.ebuild)
1302605855: >>> AUTOCLEAN: sys-devel/make:0
1302605855: === Unmerging... (sys-devel/make-3.81-r2)
1302605856: >>> unmerge success: sys-devel/make-3.81-r2
1302605857: === (4 of 6) Post-Build Cleaning (sys-devel/make-3.82::/mnt/nfs_portage/sys-devel/make/make-3.82.ebuild)
1302605857: ::: completed emerge (4 of 6) sys-devel/make-3.82 to /
1302605857: >>> emerge (5 of 6) sys-devel/gcc-4.5.2 to /
1302605918: === (5 of 6) Cleaning (sys-devel/gcc-4.5.2::/mnt/nfs_portage/sys-devel/gcc/gcc-4.5.2.ebuild)
1302605920: === (5 of 6) Compiling/Merging (sys-devel/gcc-4.5.2::/mnt/nfs_portage/sys-devel/gcc/gcc-4.5.2.ebuild)
1302610011: === (5 of 6) Merging (sys-devel/gcc-4.5.2::/mnt/nfs_portage/sys-devel/gcc/gcc-4.5.2.ebuild)
1302610035: >>> AUTOCLEAN: sys-devel/gcc:4.5
1302610089: === (5 of 6) Post-Build Cleaning (sys-devel/gcc-4.5.2::/mnt/nfs_portage/sys-devel/gcc/gcc-4.5.2.ebuild)
1302610089: ::: completed emerge (5 of 6) sys-devel/gcc-4.5.2 to /
1302610089: >>> emerge (6 of 6) gnome-base/gnome-keyring-3.0.0-r300 to /
1302610089: === (6 of 6) Cleaning (gnome-base/gnome-keyring-3.0.0-r300::/var/lib/layman/gnome/gnome-base/gnome-keyring/gnome-keyring-3.0.0-r300.ebuild)
1302610092: === (6 of 6) Compiling/Merging (gnome-base/gnome-keyring-3.0.0-r300::/var/lib/layman/gnome/gnome-base/gnome-keyring/gnome-keyring-3.0.0-r300.ebuild)
1302610129: *** Finished. Cleaning up...
1302610129: *** exiting unsuccessfully with status '1'.
1302610141: *** terminating.
1302610287: Started emerge on: Apr 12, 2011 13:11:27
1302610287: *** emerge gnome-keyring
1302610303: >>> emerge (1 of 1) gnome-base/gnome-keyring-3.0.0 to /
1302610303: === (1 of 1) Cleaning (gnome-base/gnome-keyring-3.0.0::/var/lib/layman/gnome/gnome-base/gnome-keyring/gnome-keyring-3.0.0.ebuild)
1302610305: === (1 of 1) Compiling/Merging (gnome-base/gnome-keyring-3.0.0::/var/lib/layman/gnome/gnome-base/gnome-keyring/gnome-keyring-3.0.0.ebuild)
1302610337: *** Finished. Cleaning up...
1302610337: *** exiting unsuccessfully with status '1'.
1302610337: *** terminating.
1302610620: Started emerge on: Apr 12, 2011 13:17:00
1302610620: *** emerge gnome-keyring
1302610625: >>> emerge (1 of 1) gnome-base/gnome-keyring-3.0.0 to /
1302610625: === (1 of 1) Cleaning (gnome-base/gnome-keyring-3.0.0::/var/lib/layman/gnome/gnome-base/gnome-keyring/gnome-keyring-3.0.0.ebuild)
1302610625: === (1 of 1) Compiling/Merging (gnome-base/gnome-keyring-3.0.0::/var/lib/layman/gnome/gnome-base/gnome-keyring/gnome-keyring-3.0.0.ebuild)
1302610718: === (1 of 1) Merging (gnome-base/gnome-keyring-3.0.0::/var/lib/layman/gnome/gnome-base/gnome-keyring/gnome-keyring-3.0.0.ebuild)
1302610721: >>> AUTOCLEAN: gnome-base/gnome-keyring:0
1302610721: === Unmerging... (gnome-base/gnome-keyring-3.0.0)
1302610729: >>> unmerge success: gnome-base/gnome-keyring-3.0.0
1302610731: === (1 of 1) Post-Build Cleaning (gnome-base/gnome-keyring-3.0.0::/var/lib/layman/gnome/gnome-base/gnome-keyring/gnome-keyring-3.0.0.ebuild)
1302610731: ::: completed emerge (1 of 1) gnome-base/gnome-keyring-3.0.0 to /
1302610731: *** Finished. Cleaning up...
1302610731: *** exiting successfully.
1302610732: *** terminating. |
You can see, just after updating GCC it moves to the final package, gnome-keyring, but fails.
Portage told me at that point the system GCC was set to the previous version, (as it didn't see any need to update it) so I manually updated it using gcc-config, after which gnome-keyring successfully builds.
Seeing how you have updated the GCC, it is generally a good idea to update your toolchain.
This will ensure your "system" is compiled using the same hymn sheet, so to speak. This is generally a good idea, and advisable.
Incidentally, the package list above contains the following (take note of package versions)
| Code: | app-shells/bash-4.2_p8
dev-libs/mpc-0.8.2
sys-apps/sandbox-2.5
sys-devel/make-3.82
sys-devel/gcc-4.5.2
gnome-base/gnome-keyring-3.0.0-r300 |
Let me know how you get on.
_________________
Whatever you do, do it properly! |
|
| Back to top |
|
|
rajackar
n00b
Joined: 09 Nov 2010
Posts: 15
|
| Posted: Sun Apr 17, 2011 9:48 pm Post subject: |
|
|
Well, it took some time but "emerge -e system" finished with only schroedinger failing.
I still have to look in to that.
Sadly gnome-keyring still fails.
I'm really at a loss here.
Will it help if I post my build log? |
|
| Back to top |
|
|
gnot
n00b
Joined: 02 May 2008
Posts: 20
|
| Posted: Mon Apr 18, 2011 5:05 am Post subject: |
|
|
| rajackar wrote: | Well, it took some time but "emerge -e system" finished with only schroedinger failing.
I still have to look in to that.
Sadly gnome-keyring still fails.
I'm really at a loss here.
Will it help if I post my build log? |
may I have a look at your build log,  |
|
| Back to top |
|
|
rajackar
n00b
Joined: 09 Nov 2010
Posts: 15
|
|
| Back to top |
|
|
Thistled
Guru
Joined: 06 Jan 2011
Posts: 572
Location: Scotland
|
| Posted: Mon Apr 18, 2011 11:27 am Post subject: |
|
|
You have not done anything stupid. It's happened to a few people (who have dared to venture into the 3 territory - lol). It's a problem with the build.
Incidentally, your build log is a carbon copy of mine. Always borking at the gcr-3 bit.
https://bugs.gentoo.org/show_bug.cgi?id=363075
Your problem is highlighted in the above bug.
Gilles fixed the problem in the gnome-overlay.
So I think you need to pull in gnome-keyring again from the gnome-overlay.
That is what I did also.
So, to make sure your gnome-overlay is the latest.
then
| Code: | | emerge =gnome-base/gnome-keyring-3.0.0-r300 |
Fingers crossed you might nail it this time.
_________________
Whatever you do, do it properly! |
|
| Back to top |
|
|
rajackar
n00b
Joined: 09 Nov 2010
Posts: 15
|
| Posted: Mon Apr 18, 2011 11:39 am Post subject: |
|
|
That finally did it
Thanks a lot for your time in helping me out!!
I can finally go back to emerging the rest of gnome 3
Hope that goes without more problems. |
|
| Back to top |
|
|
Thistled
Guru
Joined: 06 Jan 2011
Posts: 572
Location: Scotland
|
| Posted: Mon Apr 18, 2011 11:49 am Post subject: |
|
|
Man, relief!
Well done mate, apologies if I threw you off a bit with all the gcc / e-d-s stuff.
I spent days toying with all sorts of use flags and re-emerging, was quite a test.
Phew, glad you got there.
Just shout if there are any more probs.
_________________
Whatever you do, do it properly! |
|
| Back to top |
|
|
|
Unsupported Software
