Bug 100362 – xscreensaver-4.22-r2 fails to compile

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Tim Redman 2005-07-26 07:08:20 UTC]

Some bad settings in my use flags uncovered this.  An error is produced during
the upgrade to xscreensaver-4.22-r2, when USE includes "motif" and "-gtk".  With
the reverse applied ("-motif" and "gtk"), the error is not raised.

This bug doesn't affect me, since my USE flags were set incorrectly to begin
with, but it might affect somebody who has their heart set on a MOTIF only system.




Reproducible: Always
Steps to Reproduce:
1. emerge x11-misc/xscreensaver-4.22-r2, with USE="motif -gtk"
2.
3.

Actual Results:  
i686-pc-linux-gnu-gcc -pedantic -Wall -Wstrict-prototypes -Wnested-externs
-std=c89 -U__STRICT_ANSI__ -L/usr/lib -o xscreensaver-command remote.o
xscreensaver-command.o  -L/usr/lib -lSM -lICE -lX11 -lXext
make[1]: *** No rule to make target `XScreenSaver_ad_Xm.h', needed by
`demo-Xm.o'.  Stop.
make[1]: Leaving directory
`/var/tmp/portage/xscreensaver-4.22-r2/work/xscreensaver-4.22/driver'
make: *** [default] Error 5


Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.3.5-20050130,
glibc-2.3.5-r0, 2.6.12-gentoo-r6 i686)
=================================================================
System uname: 2.6.12-gentoo-r6 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz
Gentoo Base System version 1.6.13
ccache version 2.3 [enabled]
dev-lang/python:     2.3.5
sys-apps/sandbox:    1.2.11
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.18-r1
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-Os -march=pentium4 -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-Os -march=pentium4 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://gentoo.osuosl.org/
ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo ftp://ftp.ussg.iu.edu/pub/linux/gentoo
http://open-systems.ufl.edu/mirrors/gentoo"
MAKEOPTS="-j6"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.davidandgoliathtees.com/gentoo-portage"
USE="x86 X alsa apache2 avi berkdb bitmap-fonts cdr chroot crypt cups curl dga
divx4linux dv dvd dvdr emboss encode faad fam flac foomaticdb gd gdbm gif
gimpprint gstreamer gtk gtk2 icq imagemagick imap imlib innodb java jpeg junit
kde lcms ldap lesstif libg++ libwww live mad maildir mmx mng motif mozilla
mozsvg mp3 mpeg msn mysql ncurses nptl nptlonly odbc ogg oggvorbis opengl oss
pam pdflib perl png ppds python qt quicktime radeon readline samba sdl sensord
softmmu spell sse ssl svg svga symlink tcltk tcpd tiff truetype truetype-fonts
type1-fonts userlocales v4l v4l2 visualization vorbis xml xml2 xmms xscreensaver
xv xvid zlib video_cards_radeon userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS

[Comment 1 Jonathan Smith (RETIRED) 2005-07-26 12:48:12 UTC]

using motif and not gtk is just stupid, since the motif "version" of
xscreensaver is woefully unmaintained. (not that i'm blaming you, just upstream ;-)

i'm considering dropping the gtk USE flag entirely, and simply requiring it. the
4.22-r3 version does just that, and is now being tested in ~arch

[Comment 2 Jonathan Smith (RETIRED) 2005-07-26 12:48:39 UTC]

btw, the motif flag is still there, and it should compile with or without that flag

[Comment 3 Tim Redman 2005-07-26 18:42:11 UTC]

Wouldn't hurt my feelings any.  I'm not even sure why my USE flags were set that
way.  It was only on one of seven machines that I maintain and/or use.

[Comment 4 Marcelo Goes (RETIRED) 2005-08-07 16:34:15 UTC]

Why is this bug marked fixed when it really is not?

I just got this error when updating xscreensaver to 4.22-r2, which is x86 stable.
If this cannot be properly fixed in -r2, you should at least block the user from
emerging with USE="+motif -gtk" and print out an error message.

[Comment 5 Jonathan Smith (RETIRED) 2005-08-08 06:33:01 UTC]

(In reply to comment #4)
> you should at least block the user from
> emerging with USE="+motif -gtk" and print out an error message.

there IS a nasty warning about doing just that, and -r3,-r4 don't let users
screw themselves

-r4 is going stable soon anyway

[Comment 6 Jakub Moc (RETIRED) 2005-08-13 11:31:33 UTC]

*** Bug 102387 has been marked as a duplicate of this bug. ***

[Comment 7 Jakub Moc (RETIRED) 2008-02-21 12:40:18 UTC]

*** Bug 210964 has been marked as a duplicate of this bug. ***