Bug 113681 – ERROR: x11-misc/xscreensaver-4.22-r4 failed

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description lji 2005-11-26 22:20:33 UTC]

I got this error when I tried to update by
emerge --update --deep --newuse world

Reproducible: Always
Steps to Reproduce:
1.
2.
3.




i586-pc-linux-gnu-gcc -pedantic -Wall -Wstrict-prototypes -Wnested-externs
-std=c89 -U__STRICT_ANSI__ -L/usr/lib -o extrusion   extrusion.o
extrusion-helix2.o extrusion-helix3.o extrusion-helix4.o extrusion-joinoffset.o
extrusion-screw.o extrusion-taper.o extrusion-twistoid.o xpm-ximage.o
screenhack-gl.o xlock-gl.o fps.o ../xlockmore.o ../../utils/resources.o
../../utils/visual.o ../../utils/visual-gl.o ../../utils/usleep.o
../../utils/yarandom.o ../../utils/hsv.o ../../utils/colors.o rotator.o
trackball.o gltrackball.o  -L/usr/lib            -lXpm -Wl,--export-dynamic
-lgdk_pixbuf_xlib-2.0 -lgdk_pixbuf-2.0 -lm -lgobject-2.0 -lgmodule-2.0 -ldl
-lglib-2.0   -lGL -lGLU -lXxf86vm -lpthread  -lSM -lICE -lXt -lX11 -lXmu -lXext
 -lm  -L/usr/lib -lgle -lXpm -Wl,--export-dynamic -lgdk_pixbuf_xlib-2.0
-lgdk_pixbuf-2.0 -lm -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0   -lGL -lGLU
-lXxf86vm -lpthread  -lSM -lICE -lXt -lX11 -lXmu -lXext  -lm
make[1]: Leaving directory
`/var/tmp/portage/xscreensaver-4.22-r4/work/xscreensaver-4.22/hacks/glx'
make[1]: Entering directory
`/var/tmp/portage/xscreensaver-4.22-r4/work/xscreensaver-4.22/po'
make[1]: warning: jobserver unavailable: using -j1.  Add `+' to parent make rule.
make[1]: *** No rule to make target `zh.gmo', needed by `all-yes'.  Stop.
make[1]: Leaving directory
`/var/tmp/portage/xscreensaver-4.22-r4/work/xscreensaver-4.22/po'
make: *** [default] Error 5

!!! ERROR: x11-misc/xscreensaver-4.22-r4 failed.
!!! Function src_compile, Line 127, Exitcode 2
!!! emake failed
!!! If you need support, post the topmost build error, NOT this status message.

[Comment 1 Krzysztof Pawlik (RETIRED) 2005-11-27 03:03:29 UTC]

`emerge --info` ?

[Comment 2 Philippe Troin 2005-12-05 20:31:52 UTC]

Created attachment 74125 [details]
Emerge --info output.

I'm not the original submitter, but enclosed is my emerge --info output.
I can reproduce the bug.

I strongly suspect this is caused by zh in LINGUAS...

[Comment 3 Philippe Troin 2005-12-05 20:44:22 UTC]

(In reply to comment #2)
> I strongly suspect this is caused by zh in LINGUAS...

Confirmed, dropping zh from linguas did not give any errors.

[Comment 4 Philippe Troin 2005-12-05 21:09:03 UTC]

Bug is caused by this snippet from xscreensaver-4.22/aclocal.m4:

       AC_MSG_CHECKING(for catalogs to be installed)
       NEW_LINGUAS=
       for lang in ${LINGUAS=$ALL_LINGUAS}; do
         case "$ALL_LINGUAS" in
          *$lang*) NEW_LINGUAS="$NEW_LINGUAS $lang" ;;
         esac
       done
       LINGUAS=$NEW_LINGUAS
       AC_MSG_RESULT($LINGUAS)

ALL_LINGUAS contains zh_TW and zh_CN, but no zh.
WHen LINGUAS contains zh in the ebuild environment, *zh* matches zh_TW (or
zh_CN), and zh is added to CATALOGS.  This causes the failure.

aclocal.m4 is generated from various autoconf fragments.  This fragment comes
from gettext I believe.

Workaround: run autoreconf in the build sequence seems to fix the problem.
Or bug jwz to update his build environment (esp. gettext).

[Comment 5 Philippe Troin 2005-12-05 22:02:29 UTC]

Created attachment 74133 [details, diff]
Patch fix entering partially matching LINGUAS into CATALOGS

The enclosed patch fixes the problem.

[Comment 6 Philippe Troin 2005-12-05 22:03:16 UTC]

Created attachment 74134 [details]
Updated ebuild.

This updated ebuild adds the linguas patch on top of the rest.

[Comment 7 Krzysztof Pawlik (RETIRED) 2005-12-28 11:16:28 UTC]

Fixed in 4.23, which goes stable today.

[Comment 8 Philippe Troin 2006-02-15 19:25:18 UTC]

Confirmed closed on 4.23-r1 an amd64.

[Comment 9 Roby 2008-03-04 23:54:29 UTC]

This problem appears again for xscreensaver-5.05

[Comment 10 Samuli Suominen (RETIRED) 2008-03-26 13:30:25 UTC]

(In reply to comment #9)
> This problem appears again for xscreensaver-5.05
> 

You should have opened a new bug, but luckily I picked it up from my mailbox. The issue should be now fixed with 5.05, and it's going stable.