On Tue, May 22, 2007 at 08:37:02PM +0200, Christian T. Steigies wrote:
> 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?
Not really. gcc-4.2 requires its patches to be updated; currently
(almost) all m68k-specific bits are commented out.
I'm working on this, and am making some progress, although the current
patch (debian/patches/m68k-split_shift.dpatch) is proving to be quite a
challenge (it touches gcc/config/m68k/m68k.md, which is uh, rather
daunting).
--
Shaw's Principle:
Build a system that even a fool can use, and only a fool will
want to use it.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
