[ icewm-Bugs-2930715 ] IceWM fails to build when XRandr is disabled

"SourceForge.net" <[email protected]> Tue, 12 Jan 2010 17:48:00 +0000
Newsgroups gmane.comp.window-managers.icewm.devel
Message-ID <[email protected]>
Bugs item #2930715, was opened at 2010-01-12 17:26
Message generated for change (Settings changed) made by captnmark
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100031&aid=2930715&group_id=31

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: icewm-1.3
Group: crash
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: IceWM fails to build when XRandr is disabled

Initial Comment:
Hello,

IceWM 1.3.5 (and 1.3.6pre3) fails to build when --disable-xrandr has been used.

The build fails with the following linker error (this is for 1.3.5):

 CXX      yimage_imlib.o
 CXX      yimage_xpm.o
 CXX      ytooltip.o
 LD       icewm
wmmgr.o(.text+0xa89): In function
`YWindowManager::handleConfigure(XConfigureEvent const&)':
/home/simon/i/icewm-1.3.5/src/wmmgr.cc:621: undefined reference to
`YWindowManager::UpdateScreenSize(_XEvent*)'
collect2: ld returned 1 exit status
make[1]: *** [icewm] Error 1
make[1]: Leaving directory `/home/simon/i/icewm-1.3.5/src'
make: *** [base] Error 2

The configure command was:

./configure --disable-xrandr --enable-menus-gnome2

The problem is that YWindowManager::UpdateScreenSize() is called
unconditionally in src/wmmgr.cc, but whether the subroutine is
included is dependant on XRandr been enabled.

----------------------------------------------------------------------

>Comment By: Marko Macek (captnmark)
Date: 2010-01-12 18:47

Message:
fixed in icewm-1-3-BRANCH

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100031&aid=2930715&group_id=31

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev