Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 264142 - [gnome-overlay] gnome-base/gnome-keyring-2.26.0 Fails build
Summary: [gnome-overlay] gnome-base/gnome-keyring-2.26.0 Fails build
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: gnome2.26
  Show dependency tree
 
Reported: 2009-03-29 04:54 UTC by Joshua Doll
Modified: 2009-05-19 07:22 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log (build.log,140.80 KB, text/plain)
2009-03-29 04:55 UTC, Joshua Doll
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joshua Doll 2009-03-29 04:54:46 UTC
gnome-base/gnome-keyring-2.26.0 Fails to install, appears to be running tests even with tests off. 

Reproducible: Always




nietzsche gnome-base # emerge --info
Portage 2.2_rc28 (default/linux/amd64/2008.0, gcc-4.1.2, glibc-2.8_p20080602-r1, 2.6.29-gentoo x86_64)
=================================================================
System uname: Linux-2.6.29-gentoo-x86_64-Intel-R-_Core-TM-2_CPU_6420_@_2.13GHz-with-glibc2.2.5
Timestamp of tree: Sat, 28 Mar 2009 18:30:01 +0000
ccache version 2.4 [enabled]
app-shells/bash:     3.2_p39
dev-java/java-config: 2.1.7
dev-lang/python:     2.5.2-r7
dev-util/ccache:     2.4-r7
sys-apps/baselayout: 2.0.0
sys-apps/openrc:     0.4.3-r1
sys-apps/sandbox:    1.2.18.1-r2
sys-devel/autoconf:  2.13, 2.63
sys-devel/automake:  1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.2
sys-devel/binutils:  2.18-r3
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool:   2.2.6a
virtual/os-headers:  2.6.27-r2
ACCEPT_KEYWORDS="amd64"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=nocona -O2 -pipe -msse -msse2 -msse3 -fomit-frame-pointer"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c /etc/udev/rules.d"
CXXFLAGS="-march=nocona -O2 -pipe -msse -msse2 -msse3 -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="ccache distlocks fixpackages metadata-transfer nostrip parallel-fetch preserve-libs protect-owned sandbox sfperms strict test unmerge-orphans userfetch userpriv usersandbox"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo"
LANG="en_US.UTF-8"
LDFLAGS="-Wl,-O1"
LINGUAS="en en_US"
MAKEOPTS="-j3 --load-average "
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/portage/local/layman/desktop-effects /usr/portage/local/layman/vmware /usr/portage/local/layman/qting-edge /usr/portage/local/layman/genscripts /usr/portage/local/layman/kde-testing /usr/portage/local/layman/mozilla /usr/portage/local/layman/gnome /usr/portage/local/overlay"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X a52 aac acl acpi alsa amd64 ao avahi bash-completion berkdb bluetooth branding bzip2 cairo cd cdda cddb cdparanoia cdr cli cpudetection cracklib crypt css cups dbus device-mapper directfb doc dri dvd dvdr dvdread dvi encode esd exif fam fame ffmpeg flac fontconfig foomaticdb fortran gcdmaster gdbm gif gimp glitz gnome gnome-keyring gphoto2 gpm gstreamer gtk hal iconv id3tag ieee1394 imagemagick ipod iptc isdnlog ithreads joystick jpeg jpeg2k kdeprefix lame libnotify libvisual lm_sensors mad matroska midi mmx mozilla mp3 mp4 mpeg mudflap multilib musepack musicbrainz nautilus ncurses network nfs nls nptl nptlonly nsplugin nvidia offensive ogg opengl openmp oss pam pango pcre pdf perl png portage ppds pppd python qt3support qt4 quicktime rar raw readline reflection rtc session smp spell spl srt sse sse2 ssl ssse3 startup-notification svg sysfs taglib tcpd theora threads tiff truetype twolame type1 unicode usb vcd vim-syntax visualization vorbis wxwindows x264 xcb xcomposite xine xmp xorg xpm xscreensaver xulrunner xv xvid xvmc zlib" ALSA_CARDS="hda-intel" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="mouse keyboard evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en en_US" USERLAND="GNU" VIDEO_CARDS="nvidia i810 nv vesa"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LC_ALL, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS



/etc/portage/env
nietzsche gnome-base # cat gnome-keyring 
CFLAGS="-march=nocona -O2 -pipe -msse -msse2 -msse3 "
CXXFLAGS="${CFLAGS}"
LDFLAGS="-Wl,--no-as-needed"
FEATURES="-test"
Comment 1 Joshua Doll 2009-03-29 04:55:26 UTC
Created attachment 186623 [details]
build.log
Comment 2 Serkan Kaba (RETIRED) gentoo-dev 2009-03-29 09:30:38 UTC
It also uses -Werror which shouldn't be done in release code.
Comment 3 Xake 2009-03-30 07:30:30 UTC
(In reply to comment #0)
> gnome-base/gnome-keyring-2.26.0 Fails to install, appears to be running tests
> even with tests off. 

No, it does not run the tests, it just tries to compile them (look in your log and you will see it failed during src_compile, and that the output from ./configure said it wanted to compile the tests).
Since you have FEATURES="test" turned on globally the USE="test" is being enabled. For gnome-keyring USE="test" tells the ebuilds to build tests so FEATURES="test" later kan run them.
So the ebuilds rightfully tries to build the tests, but fails (because of a -Werror) even before it comes around to the "running tests" part.

It may be a bug in portage when it tries to build with USE="test" even when in profile/env you have FEATURES="-test".


Still the -Werror part should be looked into if we should have that or not, since only the tests are built with it.
Comment 4 Joshua Doll 2009-03-30 17:16:42 UTC
(In reply to comment #3)
> (In reply to comment #0)
> > gnome-base/gnome-keyring-2.26.0 Fails to install, appears to be running tests
> > even with tests off. 
> 
> No, it does not run the tests, it just tries to compile them (look in your log
> and you will see it failed during src_compile, and that the output from
> ./configure said it wanted to compile the tests).
> Since you have FEATURES="test" turned on globally the USE="test" is being
> enabled. For gnome-keyring USE="test" tells the ebuilds to build tests so
> FEATURES="test" later kan run them.
> So the ebuilds rightfully tries to build the tests, but fails (because of a
> -Werror) even before it comes around to the "running tests" part.
> 
> It may be a bug in portage when it tries to build with USE="test" even when in
> profile/env you have FEATURES="-test".
> 
> 
> Still the -Werror part should be looked into if we should have that or not,
> since only the tests are built with it.
> 






(In reply to comment #3)
> (In reply to comment #0)
> > gnome-base/gnome-keyring-2.26.0 Fails to install, appears to be running tests
> > even with tests off. 
> 
> No, it does not run the tests, it just tries to compile them (look in your log
> and you will see it failed during src_compile, and that the output from
> ./configure said it wanted to compile the tests).
> Since you have FEATURES="test" turned on globally the USE="test" is being
> enabled. For gnome-keyring USE="test" tells the ebuilds to build tests so
> FEATURES="test" later kan run them.
> So the ebuilds rightfully tries to build the tests, but fails (because of a
> -Werror) even before it comes around to the "running tests" part.
> 
> It may be a bug in portage when it tries to build with USE="test" even when in
> profile/env you have FEATURES="-test".
> 
> 
> Still the -Werror part should be looked into if we should have that or not,
> since only the tests are built with it.
> 

gnome-base/gnome-keyring -test is a line in my /etc/portage/package.use. The build appears to fail in the same way.

x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. -I./.. -I./../.. -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12   -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include       -I../../gp11/ -DEXTERNAL_TEST -Wall 	-Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes 	-Wnested-externs -Wpointer-arith 	-Wcast-align -Wsign-compare 	-march=nocona -O2 -pipe -msse -msse2 -msse3  -Wno-strict-aliasing -Wno-sign-compare -Werror -MT run_auto_test-unit-test-gp11-crypto.o -MD -MP -MF .deps/run_auto_test-unit-test-gp11-crypto.Tpo -c -o run_auto_test-unit-test-gp11-crypto.o `test -f 'unit-test-gp11-crypto.c' || echo './'`unit-test-gp11-crypto.c
cc1: warnings being treated as errors
unit-test-gp11-object.c: In function ‘test_create_object’:
unit-test-gp11-object.c:104: warning: ‘last_handle’ may be used uninitialized in this function
make[4]: *** [run_auto_test-unit-test-gp11-object.o] Error 1
Comment 5 Joshua Doll 2009-03-30 17:26:13 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #0)
> > > gnome-base/gnome-keyring-2.26.0 Fails to install, appears to be running tests
> > > even with tests off. 
> > 
> > No, it does not run the tests, it just tries to compile them (look in your log
> > and you will see it failed during src_compile, and that the output from
> > ./configure said it wanted to compile the tests).
> > Since you have FEATURES="test" turned on globally the USE="test" is being
> > enabled. For gnome-keyring USE="test" tells the ebuilds to build tests so
> > FEATURES="test" later kan run them.
> > So the ebuilds rightfully tries to build the tests, but fails (because of a
> > -Werror) even before it comes around to the "running tests" part.
> > 
> > It may be a bug in portage when it tries to build with USE="test" even when in
> > profile/env you have FEATURES="-test".
> > 
> > 
> > Still the -Werror part should be looked into if we should have that or not,
> > since only the tests are built with it.
> > 
> 
> 
> 
> 
> 
> 
> (In reply to comment #3)
> > (In reply to comment #0)
> > > gnome-base/gnome-keyring-2.26.0 Fails to install, appears to be running tests
> > > even with tests off. 
> > 
> > No, it does not run the tests, it just tries to compile them (look in your log
> > and you will see it failed during src_compile, and that the output from
> > ./configure said it wanted to compile the tests).
> > Since you have FEATURES="test" turned on globally the USE="test" is being
> > enabled. For gnome-keyring USE="test" tells the ebuilds to build tests so
> > FEATURES="test" later kan run them.
> > So the ebuilds rightfully tries to build the tests, but fails (because of a
> > -Werror) even before it comes around to the "running tests" part.
> > 
> > It may be a bug in portage when it tries to build with USE="test" even when in
> > profile/env you have FEATURES="-test".
> > 
> > 
> > Still the -Werror part should be looked into if we should have that or not,
> > since only the tests are built with it.
> > 
> 
> gnome-base/gnome-keyring -test is a line in my /etc/portage/package.use. The
> build appears to fail in the same way.
> 
> x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. -I./..
> -I./../.. -D_REENTRANT -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0
> -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1
> -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12  
> -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include       -I../../gp11/
> -DEXTERNAL_TEST -Wall     -Wchar-subscripts -Wmissing-declarations
> -Wmissing-prototypes   -Wnested-externs -Wpointer-arith        -Wcast-align
> -Wsign-compare     -march=nocona -O2 -pipe -msse -msse2 -msse3 
> -Wno-strict-aliasing -Wno-sign-compare -Werror -MT
> run_auto_test-unit-test-gp11-crypto.o -MD -MP -MF
> .deps/run_auto_test-unit-test-gp11-crypto.Tpo -c -o
> run_auto_test-unit-test-gp11-crypto.o `test -f 'unit-test-gp11-crypto.c' ||
> echo './'`unit-test-gp11-crypto.c
> cc1: warnings being treated as errors
> unit-test-gp11-object.c: In function ‘test_create_object’:
> unit-test-gp11-object.c:104: warning: ‘last_handle’ may be used
> uninitialized in this function
> make[4]: *** [run_auto_test-unit-test-gp11-object.o] Error 1
> 

Portage appears to be ignoring the gnome-base/gnome-keyring -test in my package.use.

nietzsche ~ # emerge -av1 gnome-keyring

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild     U ] gnome-base/gnome-keyring-2.26.0 [2.22.3-r1] USE="doc hal pam test -debug -valgrind%" 0 kB [0=>1]





Comment 6 Xake 2009-03-30 17:29:35 UTC
(In reply to comment #4)
> 
> gnome-base/gnome-keyring -test is a line in my /etc/portage/package.use. The
> build appears to fail in the same way.
> 

Do a 'emerge -pv gnome-keyring' and I promise you it will tell you it wants to compile with USE="test".

This is because when portage decides what USE-flags to use the global FEATURES="test" sets USE="test" whatever your package.use tells you.
At this point it does not care about what you have about "test" in your /etc/portage at all.
When you are about to compile your package portage cares about your /etc/portage/profile/env and decides to go with FEATURES="-test", but as you can see the useflag is still USE="test" and thus you have a package compiled with USE="test" that will not run any tests.
Comment 7 Joshua Doll 2009-03-30 17:35:49 UTC
(In reply to comment #6)
> (In reply to comment #4)
> > 
> > gnome-base/gnome-keyring -test is a line in my /etc/portage/package.use. The
> > build appears to fail in the same way.
> > 
> 
> Do a 'emerge -pv gnome-keyring' and I promise you it will tell you it wants to
> compile with USE="test".
> 
> This is because when portage decides what USE-flags to use the global
> FEATURES="test" sets USE="test" whatever your package.use tells you.
> At this point it does not care about what you have about "test" in your
> /etc/portage at all.
> When you are about to compile your package portage cares about your
> /etc/portage/profile/env and decides to go with FEATURES="-test", but as you
> can see the useflag is still USE="test" and thus you have a package compiled
> with USE="test" that will not run any tests.
> 

Yeah I saw that. Still the package fails when compiling the tests that it shouldn't be building anyways. My preference would be for it to run the tests for the record.
Comment 8 Nirbheek Chauhan (RETIRED) gentoo-dev 2009-05-14 12:01:51 UTC
This should not be happening with the gnome-keyring in-tree, can someone verify?
Comment 9 Joshua Doll 2009-05-19 02:03:04 UTC
(In reply to comment #8)
> This should not be happening with the gnome-keyring in-tree, can someone
> verify?
> 

This doesn't appear to happen with the version of gnome-keyring-2.26.1-r1 in-tree. 
Comment 10 Nirbheek Chauhan (RETIRED) gentoo-dev 2009-05-19 07:22:45 UTC
Closing fixed then..