This is what is reported in bug 23843. # emerge tightvnc (or emerge vnc) builds, althought it reports: bufio.c: In function `BufFileRawFill': bufio.c:76: warning: cast from pointer to integer of different size bufio.c: In function `BufFileRawSkip': bufio.c:102: warning: cast from pointer to integer of different size bufio.c:109: warning: cast from pointer to integer of different size bufio.c: In function `BufFileRawClose': bufio.c:125: warning: cast from pointer to integer of different size bufio.c: In function `BufFileOpenRead': bufio.c:137: warning: cast to pointer from integer of different size bufio.c: In function `BufFileRawFlush': bufio.c:152: warning: cast from pointer to integer of different size bufio.c: In function `BufFileOpenWrite': bufio.c:167: warning: cast to pointer from integer of different size and fserve.c: In function `fs_free_fpe': fserve.c:455: error: structure has no member named `fds_bits' fserve.c:455: error: structure has no member named `fds_bits' fserve.c:455: error: structure has no member named `fds_bits' fserve.c:455: error: structure has no member named `fds_bits' fserve.c:455: error: structure has no member named `fds_bits' fserve.c:455: error: structure has no member named `fds_bits' fserve.c:455: error: structure has no member named `fds_bits' fserve.c:455: error: structure has no member named `fds_bits' fserve.c: In function `fs_block_handler': fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' fserve.c:1185: error: structure has no member named `fds_bits' make[3]: *** [fserve.o] Error 1 However it does not produce /usr/bin/Xvnc, which is required to run a vnc server. Reproducible: Always Steps to Reproduce: 1. emerge tightvnc 2. updatedb 3. locate Xvnc Actual Results: /usr/share/man/man1/Xvnc.1.gz but no /usr/bin/Xvnc Expected Results: Produce Xnvc in /usr/bin Portage 2.0.51.22-r1 (default-linux/amd64/2005.0, gcc-3.4.3, glibc-2.3.5-r0, 2.6.11-gentoo-r11 x86_64) ================================================================= System uname: 2.6.11-gentoo-r11 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.6.12 dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.9 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="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -pipe -O2" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /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="-march=k8 -pipe -O2" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X acpi alsa arts berkdb bitmap-fonts crypt curl fam font-server fortran gdbm gif gpm gtk ipv6 jp2 jpeg kde lzw lzw-tiff mad motif mp3 ncurses nls ogg opengl oss pam perl png python qt readline sdl ssl tcpd tiff truetype truetype-fonts type1-fonts usb userlocales vorbis xml2 xpm xrandr xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
(In reply to comment #0) > This is what is reported in bug 23843. # emerge tightvnc (or emerge vnc) builds, > althought it reports: > However it does not produce /usr/bin/Xvnc, which is required to run a vnc server. I'd say not really possible: cd Xvnc && ./configure || die "Configure failed." so the summary seems to be incorrect. What does `equery f tightvnc | grep Xvnc` say? Also, please attach a complete emerge log; run `emerge tightvnc &> emerge.log` and attach the output.
Created attachment 63060 [details] Output of emerge tightvnc
# equery f tightvnc|grep Xvnc /usr/share/man/man1/Xvnc.1.gz
Thanks. You forgot to reopen.
Created attachment 68360 [details] Emerge log I get the same issue, with a different fail point. cougar kovu # equery f tightvnc | grep Xvnc /usr/share/man/man1/Xvnc.1.gz Emerge log also attached from my attempt (if it helps).
Is there a known workaround? I, too have encountered this but, and see exactly the same problems.
I have found that using the USE flag of "server" helped me get the Xvnc binary created and installed. This was true for me for tightvnc and realvnc (aka vnc). Try re-emerging like this USE="server" emerge tightvnc
>USE="server" emerge tightvnc I have solved my problems otherwise and have not needed vnc anymore, but just tried and this did not help to create a binary Xvnc.
tightvnc has no USE flag "server" it will not solve the problem.
This bug happens on x86 as well as on amd64 for tightvnc-1.2.9-r1. The difference is that 1.3_alpha5 (which has sever USEflag) is masked on amd64.
tightvnc-1.3_alpha5-gcc34.patch applied on 1.2.9-r1 solves the compile problem, however Xvnc segfaults on amd64 (see bug 82583).
tightvnc-1.3_alpha7 works with an additional patch applied, should show in portage in ~ 2hours, sync and test that
on second thought, porting patches should see this fix in ~2 hours
