On Sun, Feb 24, 2008 at 10:48:42AM -0600, Stephen R Marenka wrote:
> On Sun, Feb 24, 2008 at 08:05:21AM +0100, Michael Schmitz wrote:
> > > On Mon, Feb 18, 2008 at 07:53:18AM +0100, Matthias Klose wrote:
> > > > gcj-4.3 failed to build on m68k trying to build interpret.cc, timing
> > > > out after
On Sun, Feb 24, 2008 at 08:05:21AM +0100, Michael Schmitz wrote:
> > On Mon, Feb 18, 2008 at 07:53:18AM +0100, Matthias Klose wrote:
> > > gcj-4.3 failed to build on m68k trying to build interpret.cc, timing
> > > out after 600 minutes. this is one of the problematic files taking a
> > > huge time
> On Mon, Feb 18, 2008 at 07:53:18AM +0100, Matthias Klose wrote:
> > gcj-4.3 failed to build on m68k trying to build interpret.cc, timing
> > out after 600 minutes. this is one of the problematic files taking a
> > huge time to build. please could somebody validate if there is still
> > progress,
On Mon, Feb 18, 2008 at 07:53:18AM +0100, Matthias Klose wrote:
> gcj-4.3 failed to build on m68k trying to build interpret.cc, timing
> out after 600 minutes. this is one of the problematic files taking a
> huge time to build. please could somebody validate if there is still
> progress, or if it's
gcj-4.3 failed to build on m68k trying to build interpret.cc, timing
out after 600 minutes. this is one of the problematic files taking a
huge time to build. please could somebody validate if there is still
progress, or if it's an infinite loop? Please try on a machine with at
least 256MB RAM.
--
5 matches
Mail list logo