On Mon, 2009-06-15 at 09:07 +0200, Thomas Bächler wrote: > Baho Utot schrieb: > > I can do that....if you can stand all the bug reports :) > > > > My script just finished and it found another 400+ that didn't build, > > that will take some time to go through to find the ones that didn't > > build because of gcc-4.4.0 errors :) > > You could collect them in one bugreport instead of opening a separate > one for each. > > All of these packages have been built at some point, so it is likely > they worked with gcc 4.1, 4.2 or 4.3 (unless they are ancient and > haven't been rebuilt much longer than that). Most of them probably > worked with 4.3. > > Once we have to rebuild these packages, we fix them to compile with the > current compiler - which is very easy most of the time. If you are > building our whole repositories, you will probably find those problems > before we do. > That is exactly what I am doing. I am compiling the whole lot to run native on AMD. Core usually compiles just fine with little or no problems, extra has lots of problems from bad URL to PKGBUILD that are not standard to gcc problems.
