JimD wrote: > On Sat, 01 Apr 2006 20:32:27 -0600 > Jeremy Olexa <[EMAIL PROTECTED]> wrote: > > >>JimD wrote: >> >>>Thanks. I wonder why TightVNC is so broken on xorg 7.0? >> >>Help the devs and submit a bug report (if its not submitted >>already) ;) > > > I beat you to the punch : ) > > https://bugs.gentoo.org/show_bug.cgi?id=128456 > > Jim
Apologies for not looking into it deeper before. Fine the ebuild is; this is a common Portage problem. See http://bugs.gentoo.org/show_bug.cgi?id=112896 for more information. Those are the dependencies needed to build TightVNC. 1 DEPEND="|| ( ( x11-libs/libXaw 2 x11-proto/xextproto 3 >=x11-misc/imake-1 4 x11-misc/gccmakedep 5 app-text/rman 6 server? ( x11-libs/libXp 7 x11-proto/inputproto 8 x11-proto/kbproto 9 x11-proto/printproto 10 x11-proto/scrnsaverproto 11 ) 13 ) 14 virtual/x11 15 ) 16 ~media-libs/jpeg-6b 17 sys-libs/zlib 18 tcpd? ( >=sys-apps/tcp-wrappers-7.6-r2 ) 19 !net-misc/vnc" See in Line 1 the || ? That tells portage that to build TightVNC: 1). We need either the packages: x11-libs/libXaw >=x11-misc/imake-1 (imake version 1 or greater) x11-misc/gccmakedep app-text/rman and if the 'server' USE flag is set: x11-libs/libXp ... so on ... x11-proto/scrnsaverproto. 2). OR, OR, OR, OR!!, OR: virtual/x11 If you look in /usr/portage/virtual/x11, there are currently two ebuilds in that directory: x11-6.8 and x11-7.0 x11-6.8 depends on <=x11-base/xorg-x11-6.99, and x11-7.0 depends on all these: >=x11-base/xorg-x11-7 x11-apps/xdm x11-apps/xdpyinfo x11-apps/xrdb x11-apps/xsetroot x11-libs/libFS x11-libs/liboldX x11-libs/libXevie x11-libs/libXprintAppUtil x11-libs/libXTrap x11-libs/libXvMC x11-themes/gentoo-xcursors x11-themes/xcursor-themes" Chances are that if you've been a long xorg 7.0 user: 1). You had to type 'virtual/x11' in /etc/portage/profile/package.provided to stop Portage from blocking your emerge -uDN world with those annoying 'blocks' because something was preventing it from downgrading Xorg to the old 6.8.2 or 6.99. 2). You somehow ended up with virtual/x11 emerged in your system. Well, that's it. Portage sees in the ebuild that virtual/x11 is listed as a dependency, so are all the packages in virtual/x11. As soon as it sees it, it forgets about gccmakedep and those other dudes and keeps going and ends upu failing. But even if you had installed Xorg 7.0 by emerging virtual/x11-7.0, notice that gccmakedep isn't there, imake isn't there, and rman isn't there, so you would've ended up with the same thing. I checked virtual/x11-7.0 by doing `emerge -ep =virtual/x11-7.0 | grep gccmakedep` and got nothing. Same result for xorg-x11-7.0-r1 Well, heh. If there's an error somewhere, I'm sure someone will point it out. Just sharing, just sharing. -Luis -- gentoo-user@gentoo.org mailing list
