On Wed, May 23, 2007 at 08:49:40AM +0200, Matthias Klose wrote: > Christian T. Steigies writes: > > Hi, > > I've been building gcc-4.2 on my mac for about a week now. The first try > > timed out, so I decided to continue the build manually. That failed last > > night, since my router had its daily crash and I did not run the build in a > > a screen session. When I continue the build again, I am afraid it will start > > all the tests again, which takes forever... I'd prefer not to do that on a > > slow mac. Is there a faster way to finish the build or should I just give > > the package back and let a faster buildd handle it? Maybe the current build > > stage is of use to somebody? I assume if it is running tests now, that the > > actual build has succeeded? > > you could finish building the binaries > > WITHOUT_CHECK=yes fakeroot debian/rules binary-arch
Thanks, I will try that. > It looks like the tests were just started, so it would not make much > sense to only run a part of the tests again, if you do want to have > complete test results. It took about 24h for those tests to run, and most of them timed out... Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
