The recent update of libixp from 0.4 to 0.5 completely broke wmii.
The wmii built against libixp 0.4 dumps core when run with libixp 0.5
installed (maybe the shlib version should have been bumped when
updating the port?)
In any case, wmii as currently in our ports tree does not build now:
cc -c -o fs.o -O2 -fno-strict-aliasing -pipe -march=pentium-m -march=pentium-m -std=c99 -pipe -Wall -Wno-parentheses -Wno-missing-braces -Wno-switch -Wno-comment -Wno-sign-compare -Wno-uninitialized -Wno-unused-parameter -Wimplicit -Wreturn-type -Wtrigraphs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -DIXPlint -I. -I../../include -I/usr/local/include -I/usr/include -I/usr/local/include -DVERSION="3.6" fs.c
cmd/wmii/fs.c:175: error: 'Fcall' has no member named 'offset'
cmd/wmii/fs.c:178: error: 'Fcall' has no member named 'offset'
cmd/wmii/fs.c:179: error: 'Fcall' has no member named 'count'
cmd/wmii/fs.c:180: error: 'Fcall' has no member named 'count'
cmd/wmii/fs.c:181: error: 'Fcall' has no member named 'data'
cmd/wmii/fs.c:182: error: 'Fcall' has no member named 'data'
cmd/wmii/fs.c:182: error: 'Fcall' has no member named 'offset'
cmd/wmii/fs.c:183: error: 'Fcall' has no member named 'count'
cmd/wmii/fs.c:191: error: 'Fcall' has no member named 'offset'
Back out the libixp update and revert back to libixp 0.4 until wmii can be
fixed to build with libixp 0.5.
How-To-Repeat: 1) install x11-wm/wmii with a ports tree from 2009-03-02
2) verify that wmii works
3) update ports tree to after 2009-03-03 and update libixp to 0.5
4) verify that wmii dumps core
1) on current ports tree: build x11-wm/wmii and see that it fails as outlined
Over to maintainer (via the GNATS Auto Assign Tool)
tabthorpe 2009-03-07 21:07:27 UTC
FreeBSD ports repository
- Fix build after libixp update
- Bump PORTREVISION
PR: ports/132374 (based on)
Submitted by: Sofian Brabez (patch)
Approved by: portmgr (pav)
Revision Changes Path
1.17 +3 -1 ports/x11-wm/wmii/Makefile
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "email@example.com"