After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 396858 - cannot emerge glib-2.14.4-r1 on gentoo
cannot emerge glib-2.14.4-r1 on gentoo
Status: RESOLVED DUPLICATE of bug 333977
Product: glib
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2007-01-15 13:15 UTC by bart
Modified: 2007-02-22 20:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description bart 2007-01-15 13:15:48 UTC
It is impossible to succesfully emerge glib-2.14.4-r1 on a gentoo installation which has the ``test'' feature set in portage. glib fails on run-collate-tests.sh

[...]
PASS: utf8-pointer
PASS: uri-test
PASS: run-markup-tests.sh
2d1
< GTK+
8a8
> GTK+
Test failed: unexpected error when using g_utf8_collate() on ./collate/collate-1.in
FAIL: run-collate-tests.sh
PASS: run-bookmark-test.sh
=====================================================================
1 of 50 tests failed
Please report to http://bugzilla.gnome.org/enter_bug.cgi?product=glib
=====================================================================
make[4]: *** [check-TESTS] Error 1
make[4]: Leaving directory `/var/tmp/portage/glib-2.12.4-r1/work/glib-2.12.4/tests'
make[3]: *** [check-am] Error 2
make[3]: Leaving directory `/var/tmp/portage/glib-2.12.4-r1/work/glib-2.12.4/tests'
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/glib-2.12.4-r1/work/glib-2.12.4/tests'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/glib-2.12.4-r1/work/glib-2.12.4'
make: *** [check] Error 2
Comment 1 Karsten Bräckelmann 2007-02-22 20:46:43 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

The reason this happens seems to be that you have not the en_US locale installed.


*** This bug has been marked as a duplicate of 333977 ***