1 |
This is great work and is highly appreciated :) |
2 |
and you are right, right now we wouldn't like to be swamped with more |
3 |
bugs related to gcc3 since we are attempting to get a stable release out |
4 |
the door, hopefully that will change in the next month and Azarah |
5 |
woodchip et al. will bring their heads together and get things working |
6 |
with gcc3 ... if not, I'll try ;) |
7 |
|
8 |
|
9 |
|
10 |
> |
11 |
> If you plan to try to do the same thing as I have, I recommend you DO |
12 |
> NOT use the -funroll-loops optimization. |
13 |
Now this is interesting news, and |
14 |
|
15 |
|
16 |
|
17 |
> Most of this document speaks in programmer terms. |
18 |
> |
19 |
> XFree86 4.2.0 (r8) |
20 |
Bad news, I really thought they had taken care of gcc3 in the step |
21 |
between 4.1 and 4.2. I hope you have submitted this upstream to their |
22 |
bug database? |
23 |
|
24 |
|
25 |
|
26 |
> groff 1.17.2 (r1) |
27 |
> - When using the original groff (compiled in the system build), it |
28 |
> will complain about the library libstdc++-6.2-2.so.3 missing |
29 |
> after gcc 3.0.x is installed. |
30 |
|
31 |
Hmm, this could be related to you unmerging the old gcc2.95.3 |
32 |
completely, as the libraries for the c part of the libs differ quite a |
33 |
bit, which in turn breaks all c++ programs. |
34 |
|
35 |
Solution for this would be to keep the old gcc installed so that all |
36 |
programs that link to its c++ libraries will still work. |
37 |
|
38 |
The troff coredump is something that should be filed upstream, if not, |
39 |
we can look at RedHat's patches for this as they are likely to have the |
40 |
same problems with things.(scheluded for the workings of gcc3 |
41 |
compability systems) |
42 |
|
43 |
(never do work twice if you can steal the working patches from somone |
44 |
who gets paid to do it) |
45 |
|
46 |
|
47 |
|
48 |
> pcmcia-cs 3.1.33 (r2) |
49 |
this is a known bug thats due to be fixed, in the meantime |
50 |
sys-apps/pcmcia-cs-3.1.31-r4 |
51 |
is known to work with wireless and should work for you. |
52 |
|
53 |
|
54 |
|
55 |
> perl 5.6.1 (r3) |
56 |
Could you please file a bug about this? It might not be of greatest |
57 |
importance but I still think it needs to be fixed before 1.0 release. |
58 |
assign it to spider@g.o and I'll go from there. |
59 |
|
60 |
|
61 |
> openjade 1.3 (r2) |
62 |
Okies, This needs to be filed upstream at the openjade maintainers, also |
63 |
somethign we'll need to steal patches from RH/Mandrake for. Thanks for |
64 |
reporting. |
65 |
|
66 |
|
67 |
> util-linux 2.11l |
68 |
Could you file this as an enchancement bug? Would also be great if you |
69 |
got to make the ebuild, assign to me (spider@g.o) and I'll get at |
70 |
it after the freeze is done :) |
71 |
|
72 |
The international kernel patch lags behind quite a bit last I checked, |
73 |
and I'm not sure of how good it works with the different vm's (Shouldn't |
74 |
interfere) xfs changes (might well interfere) and preemptive kernels. |
75 |
something for our venerable kernel hackers to look at if it's likely to |
76 |
be included. |
77 |
|
78 |
|
79 |
|
80 |
> evolution 1.0.2 (r1) |
81 |
> - Need to apply my IMAP patch, see bug 1355 (patch included) |
82 |
Evolution 1.0.3 was released yesterday, I'll try and get it merged into |
83 |
portage (1.0.3) if my net resolves to working again. |
84 |
|
85 |
|
86 |
|
87 |
> lame 3.91 |
88 |
> - rtp.h has #ifdef 0, not #if 0 |
89 |
lame bug, should be filed upstream, but is noted for later. |
90 |
|
91 |
|
92 |
> screen |
93 |
app-misc/screen-3.9.11 |
94 |
app-misc/screen-3.9.9 |
95 |
|
96 |
> |
97 |
> avi-xmms 1.2.2 (r2) |
98 |
This should be removed from portage as the functionality now depends on |
99 |
USE="avi" for a patch to the main xmms that uses avifile 0.60 |
100 |
|
101 |
if you still have it, "emerge rsync --clean" will make sure it |
102 |
dissapears |
103 |
|
104 |
|
105 |
|
106 |
> gtkmm-addons (0.5.3) |
107 |
Probably this is "stale" now as gtk+ 2.0 is out the door but its also a |
108 |
upstream bug, but thanks for noted incompability. |
109 |
|
110 |
|
111 |
|
112 |
|
113 |
> If you have any questions, comments, or need more detail about |
114 |
> anything I've mentioned above, please let me know. I hope this is |
115 |
> helpful. I'm not finished, theres still a few loose ends to tie up, |
116 |
> however I'm getting there. MOST of my system is up and running :) |
117 |
|
118 |
|
119 |
This is great news and has been something me and others have been |
120 |
looking for, thanks for the update on the state of things, much |
121 |
welcomed. I'm looking forwards to see what happens next on this front. |
122 |
|
123 |
thanks again, |
124 |
|
125 |
|
126 |
//Spider |
127 |
|
128 |
-- |
129 |
begin happy99.exe |
130 |
This is a .signature virus! Please copy me into your .signature! |
131 |
See Microsoft KB Article Q265230 for more information. |
132 |
end |