1 |
On Tuesday 29 November 2005 04:35 pm, Wagoner, Darryl wrote: |
2 |
> Greetings, |
3 |
> |
4 |
> I am new to Gentoo and AMD64 |
5 |
> |
6 |
> I am running a duel 248 AMD Opteron processor system with 2 gig of ram. |
7 |
> |
8 |
> Linux ds9 2.6.14-gentoo-r2 #1 SMP Tue Nov 29 14:14:33 EST 2005 x86_64 |
9 |
> AMD |
10 |
> Opteron(tm) Processor 248 AuthenticAMD GNU/Linux |
11 |
> |
12 |
> make.conf: |
13 |
> CFLAGS="-O2 -march=k8 -pipe" |
14 |
> CHOST="x86_64-pc-linux-gnu" |
15 |
> CXXFLAGS="${CFLAGS}" |
16 |
> MAKEOPTS="-j3" |
17 |
> USE="x86 X gtk gnome qt kde dvd alsa cdr" |
18 |
> |
19 |
> When I try to emerge tightvnc I get the following error. Any |
20 |
> suggestions? |
21 |
> |
22 |
> Thanks |
23 |
> |
24 |
> |
25 |
> |
26 |
> |
27 |
> rm -f WaitFor.o |
28 |
> gcc -c -O2 -march=k8 -pipe -fsigned-char -I. -I../include |
29 |
> -I../../.././/expor |
30 |
> s/include/X11 -I../../.././/include/extensions -I../../.././/lib/Xau |
31 |
> -I../lbx |
32 |
> I../../.././ -I../../.././/exports/include -Dlinux -D__x86_64__ |
33 |
> -D_POSI |
34 |
> _SOURCE -D_BSD_SOURCE -D_SVID_SOURCE |
35 |
> -DX_LOCALE |
36 |
> -D_REENTRANT -DSHAPE |
37 |
> -DGCCUSESGAS -DSTATIC_COLOR -DAVOID_GLYPHBLT -DPIXPRIV -DNDEBUG |
38 |
> -DUSE_LIB |
39 |
> RAP=1 -DFUNCPROTO=15 -DNARROWPROTO -DXSERV_t -DTRANS_SERVER -DUNIXCONN |
40 |
> -DTCPCO |
41 |
> N -DINTERNAL_MALLOC -DHASXDMAUTH -DDDXOSINIT -DSERVER_LOCK |
42 |
> -DDDXOSFATALERROR |
43 |
> DDDXTIME -DPART_NET -DUSE_RGB_TXT -DMITMISC -DXTEST |
44 |
> -D |
45 |
> SYNC -DXCMISC -DMITSHM -DBIGREQS WaitFor.c |
46 |
> WaitFor.c: In function `WaitForSomething': |
47 |
> WaitFor.c:174: error: structure has no member named `fds_bits' |
48 |
> WaitFor.c:174: error: structure has no member named `fds_bits' |
49 |
> WaitFor.c:174: error: structure has no member named `fds_bits' |
50 |
> WaitFor.c:174: error: structure has no member named `fds_bits' |
51 |
> WaitFor.c:174: error: structure has no member named `fds_bits' |
52 |
> WaitFor.c:174: error: structure has no member named `fds_bits' |
53 |
> WaitFor.c:174: error: structure has no member named `fds_bits' |
54 |
> WaitFor.c:174: error: structure has no member named `fds_bits' |
55 |
> WaitFor.c:176: error: structure has no member named `fds_bits' |
56 |
> WaitFor.c:176: error: structure has no member named `fds_bits' |
57 |
> WaitFor.c:176: error: structure has no member named `fds_bits' |
58 |
> WaitFor.c:176: error: structure has no member named `fds_bits' |
59 |
> WaitFor.c:176: error: structure has no member named `fds_bits' |
60 |
> WaitFor.c:176: error: structure has no member named `fds_bits' |
61 |
> WaitFor.c:176: error: structure has no member named `fds_bits' |
62 |
> WaitFor.c:176: error: structure has no member named `fds_bits' |
63 |
> WaitFor.c:176: error: structure has no member named `fds_bits' |
64 |
> WaitFor.c:176: error: structure has no member named `fds_bits' |
65 |
> WaitFor.c:176: error: structure has no member named `fds_bits' |
66 |
> WaitFor.c:176: error: structure has no member named `fds_bits' |
67 |
> WaitFor.c:176: error: structure has no member named `fds_bits' |
68 |
> WaitFor.c:176: error: structure has no member named `fds_bits' |
69 |
> WaitFor.c:176: error: structure has no member named `fds_bits' |
70 |
> WaitFor.c:176: error: structure has no member named `fds_bits' |
71 |
> WaitFor.c:316: error: structure has no member named `fds_bits' |
72 |
> WaitFor.c:316: error: structure has no member named `fds_bits' |
73 |
> WaitFor.c:316: error: structure has no member named `fds_bits' |
74 |
> WaitFor.c:316: error: structure has no member named `fds_bits' |
75 |
> WaitFor.c:316: error: structure has no member named `fds_bits' |
76 |
> WaitFor.c:316: error: structure has no member named `fds_bits' |
77 |
> WaitFor.c:316: error: structure has no member named `fds_bits' |
78 |
> WaitFor.c:316: error: structure has no member named `fds_bits' |
79 |
> WaitFor.c:316: error: structure has no member named `fds_bits' |
80 |
> WaitFor.c:316: error: structure has no member named `fds_bits' |
81 |
> WaitFor.c:316: error: structure has no member named `fds_bits' |
82 |
> WaitFor.c:316: error: structure has no member named `fds_bits' |
83 |
> WaitFor.c:316: error: structure has no member named `fds_bits' |
84 |
> WaitFor.c:316: error: structure has no member named `fds_bits' |
85 |
> WaitFor.c:316: error: structure has no member named `fds_bits' |
86 |
> WaitFor.c:316: error: structure has no member named `fds_bits' |
87 |
> WaitFor.c:332: error: structure has no member named `fds_bits' |
88 |
> WaitFor.c:332: error: structure has no member named `fds_bits' |
89 |
> WaitFor.c:332: error: structure has no member named `fds_bits' |
90 |
> WaitFor.c:332: error: structure has no member named `fds_bits' |
91 |
> WaitFor.c:332: error: structure has no member named `fds_bits' |
92 |
> WaitFor.c:332: error: structure has no member named `fds_bits' |
93 |
> WaitFor.c:332: error: structure has no member named `fds_bits' |
94 |
> WaitFor.c:332: error: structure has no member named `fds_bits' |
95 |
> WaitFor.c:332: error: structure has no member named `fds_bits' |
96 |
> WaitFor.c:332: error: structure has no member named `fds_bits' |
97 |
> WaitFor.c:332: error: structure has no member named `fds_bits' |
98 |
> WaitFor.c:332: error: structure has no member named `fds_bits' |
99 |
> WaitFor.c:332: error: structure has no member named `fds_bits' |
100 |
> WaitFor.c:332: error: structure has no member named `fds_bits' |
101 |
> WaitFor.c:332: error: structure has no member named `fds_bits' |
102 |
> WaitFor.c:332: error: structure has no member named `fds_bits' |
103 |
> WaitFor.c:354: error: structure has no member named `fds_bits' |
104 |
> WaitFor.c:354: error: structure has no member named `fds_bits' |
105 |
> WaitFor.c:354: error: structure has no member named `fds_bits' |
106 |
> WaitFor.c:354: error: structure has no member named `fds_bits' |
107 |
> WaitFor.c:354: error: structure has no member named `fds_bits' |
108 |
> WaitFor.c:354: error: structure has no member named `fds_bits' |
109 |
> WaitFor.c:354: error: structure has no member named `fds_bits' |
110 |
> WaitFor.c:354: error: structure has no member named `fds_bits' |
111 |
> WaitFor.c:381: error: structure has no member named `fds_bits' |
112 |
> WaitFor.c:381: error: structure has no member named `fds_bits' |
113 |
> WaitFor.c:381: error: structure has no member named `fds_bits' |
114 |
> WaitFor.c:381: error: structure has no member named `fds_bits' |
115 |
> WaitFor.c:381: error: structure has no member named `fds_bits' |
116 |
> WaitFor.c:381: error: structure has no member named `fds_bits' |
117 |
> WaitFor.c:381: error: structure has no member named `fds_bits' |
118 |
> WaitFor.c:381: error: structure has no member named `fds_bits' |
119 |
> WaitFor.c:384: error: structure has no member named `fds_bits' |
120 |
> WaitFor.c:384: error: structure has no member named `fds_bits' |
121 |
> WaitFor.c:384: error: structure has no member named `fds_bits' |
122 |
> WaitFor.c:384: error: structure has no member named `fds_bits' |
123 |
> WaitFor.c:384: error: structure has no member named `fds_bits' |
124 |
> WaitFor.c:384: error: structure has no member named `fds_bits' |
125 |
> WaitFor.c:384: error: structure has no member named `fds_bits' |
126 |
> WaitFor.c:384: error: structure has no member named `fds_bits' |
127 |
> WaitFor.c:384: error: structure has no member named `fds_bits' |
128 |
> WaitFor.c:384: error: structure has no member named `fds_bits' |
129 |
> WaitFor.c:384: error: structure has no member named `fds_bits' |
130 |
> WaitFor.c:384: error: structure has no member named `fds_bits' |
131 |
> WaitFor.c:384: error: structure has no member named `fds_bits' |
132 |
> |
133 |
> -- |
134 |
> Darryl Wagoner |
135 |
> Office: 603-891-3068 |
136 |
|
137 |
|
138 |
I have an AMD64 (single CPU) system running a Gentoo 64-bit system. I had no |
139 |
problems emerging tightvnc, but I did have problems running it due to some |
140 |
bug with tightvnc code on amd64 hardware (os independent). |
141 |
|
142 |
This was a couple of months ago and it is very possibly resolved now. What I |
143 |
did was install realvnc (emerge vnc) instead. |
144 |
|
145 |
Also, I used USE="server" for vnc/tightvnc to make sure it compiles then |
146 |
installs the Xvnc binary - http://forums.gentoo.org/viewtopic-t-121110.html |
147 |
-- |
148 |
gentoo-amd64@g.o mailing list |