Summary: | [gnome-overlay] gnome-base/gnome-keyring-2.26.0 Fails build | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Joshua Doll <joshua.doll> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kanelxake, magowiz |
Priority: | High | ||
Version: | 2008.0 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 263083 | ||
Attachments: | build.log |
Description
Joshua Doll
2009-03-29 04:54:46 UTC
Created attachment 186623 [details]
build.log
It also uses -Werror which shouldn't be done in release code. (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. > (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 (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] (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. (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. This should not be happening with the gnome-keyring in-tree, can someone verify? (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. Closing fixed then.. |