#21782 closed defect (fixed)
install kde fails at xorg-libXxf86vm
Reported by: | thedoobs@… | Owned by: | jeremyhu (Jeremy Huddleston Sequoia) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.8.1 |
Keywords: | Cc: | benjamin@…, singingwolfboy@…, jenakan@…, jp@…, martin@…, steven@…, sundell.software@…, jabial@…, demon_s@… | |
Port: | xorg-libXxf86vm |
Description (last modified by blb@…)
Installing kde on a new install of macports fails at xorg-libXxf86vm. Here is the debug output from "sudo port -d install kde":
(converted to attachment)
Attachments (1)
Change History (26)
comment:1 Changed 15 years ago by blb@…
Description: | modified (diff) |
---|
Changed 15 years ago by blb@…
Attachment: | 21782_debug.txt added |
---|
comment:2 Changed 15 years ago by blb@…
Owner: | changed from macports-tickets@… to jeremyhu@… |
---|
comment:11 Changed 15 years ago by sundell.software@…
/opt/local/include/X11/extensions/xf86vmstr.h:1:2: warning: #warning "xf86vmstr.h is obsolete and may be removed in the future." /opt/local/include/X11/extensions/xf86vmstr.h:2:2: warning: #warning "include <X11/extensions/xf86vmproto.h> for the protocol defines." XF86VMode.c:156: error: expected declaration specifiers or '...' before 'XF86VidModeGamma'
The 'XF86VidModeGamma' seems to not be defined in any of the headers installed at the point when this package is built. As http://article.gmane.org/gmane.comp.freedesktop.xorg.announce/748 points out, the header was moved in xf86vidmodeproto >= 2.2.99.1 and the one installed by macports is xorg-xf86vidmodeproto @2.3.
So editing the Portfile to make it install version 1.1.0 of libXxf86vm fixes it. Will need to test further to ensure that 1.1.0 doesn't bork anything.
comment:14 follow-up: 15 Changed 15 years ago by nwgarner@…
I got this to work by modifying the following lines in /opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/xorg-libXxf86vm/Portfile.
version 1.1.0 <...> checksums md5 b431ad7084e1055fef99a9115237edd8 \
sha1 f5ce7854f201d9c69dfcdd13123b51f497b69a47 \ rmd160 e618c5e67af23c7cb8e0258a627ee8dd2e2d35ec
I calculated those sums from the file at http://xorg.freedesktop.org/archive/individual/lib/ which is where 1.1.0 will be downloaded from.
comment:15 follow-up: 16 Changed 15 years ago by nwgarner@…
Fining formatting, I hope...
I got this to work by modifying the following lines in /opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/xorg-libXxf86vm/Portfile.
version 1.1.0 <...> checksums md5 b431ad7084e1055fef99a9115237edd8 \ sha1 f5ce7854f201d9c69dfcdd13123b51f497b69a47 \ rmd160 e618c5e67af23c7cb8e0258a627ee8dd2e2d35ec
I calculated those sums from the file at http://xorg.freedesktop.org/archive/individual/lib/ which is where 1.1.0 will be downloaded from.
comment:16 Changed 15 years ago by martin@…
Replying to nwgarner@…:
Fining formatting, I hope...
I got this to work by modifying the following lines in /opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/xorg-libXxf86vm/Portfile.
version 1.1.0 <...> checksums md5 b431ad7084e1055fef99a9115237edd8 \ sha1 f5ce7854f201d9c69dfcdd13123b51f497b69a47 \ rmd160 e618c5e67af23c7cb8e0258a627ee8dd2e2d35ecI calculated those sums from the file at http://xorg.freedesktop.org/archive/individual/lib/ which is where 1.1.0 will be downloaded from.
Thanks but next problem ....
Error: wine 1.0.1 is not compatible with Mac OS X 10.6 or later. Until wine 1.2 is released, please install wine-devel instead. Error: Target org.macports.fetch returned: incompatible Mac OS X version Error: Status 1 encountered during processing.
Question: Does wine-devel provide the wine application or do I have to build it?
PS this is snow-leopard.
comment:17 Changed 15 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Resolution: | → fixed |
---|---|
Status: | new → closed |
I pushed that version of the lib earlier... just do a selfupdate.
As for wine-devel, it has been working fine for me for some time. Just make sure you uninstall wine first in order to avoid conflict.
comment:18 Changed 15 years ago by martin@…
uninstalling shouldnt be a problem, have got it to build yet :-)
I assumed wine-devel was a development package.
Thanks
comment:19 Changed 15 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Yeah, anything *-devel is "beta" or "release-candidate" quality in general...
comment:20 follow-up: 21 Changed 15 years ago by martin@…
Sorry to be a pain but get ...
---> Extracting wine-devel Error: You cannot install wine-devel for the architecture(s) i386 because /opt/local/lib/libexpat.dylib does not contain the architecture i386.
I did a google but nothing obvious showed up.
Thanks
comment:21 Changed 15 years ago by jabial@…
Replying to martin@…:
Sorry to be a pain but get ...
---> Extracting wine-devel Error: You cannot install wine-devel for the architecture(s) i386 because /opt/local/lib/libexpat.dylib does not contain the architecture i386.
I did a google but nothing obvious showed up.
Thanks
Do sudo port uninstall -f expat sudo port install expat +universal and retry.
comment:22 Changed 15 years ago by martin@…
Thanks but same problem ...
---> Installing expat @2.0.1_0+universal ---> Activating expat @2.0.1_0+universal ---> Cleaning expat [08:38:57][~]$ sudo port install wine-devel ---> Computing dependencies for wine-devel ---> Extracting wine-devel Error: You cannot install wine-devel for the architecture(s) i386 because /opt/local/lib/libfontconfig.dylib does not contain the architecture i386. Error: Target org.macports.extract returned: incompatible architectures in dependencies
comment:23 follow-up: 24 Changed 15 years ago by jabial@…
No it's not the same problem, now it's with fontconfig. You just do with fontconfig what you just did with expat.
comment:24 Changed 15 years ago by martin@…
Replying to jabial@…:
No it's not the same problem, now it's with fontconfig. You just do with fontconfig what you just did with expat.
Yeah, penny dropped after I posted the message, Im now following a chain of these.
Thanks
comment:25 Changed 15 years ago by martin@…
PS I tried the install +universal without the uninstall and that seems to add the missing arch.
debug output from original description