Richard Zidlicky writes:
> On Tue, Oct 29, 2002 at 06:10:57PM +0100, Yann Dirson wrote:
> > On Mon, Oct 21, 2002 at 09:43:05PM +0200, Matthias Klose wrote:
> > > Yann Dirson writes:
> > > > I have several packages (e2fsprogs, bigloo) that fail to build on
> > > > m68k, apparently due to one or more
On Tue, Oct 29, 2002 at 06:10:57PM +0100, Yann Dirson wrote:
> On Mon, Oct 21, 2002 at 09:43:05PM +0200, Matthias Klose wrote:
> > Yann Dirson writes:
> > > I have several packages (e2fsprogs, bigloo) that fail to build on
> > > m68k, apparently due to one or more gcc bug(s). Maybe that's the same
On Mon, Oct 21, 2002 at 09:43:05PM +0200, Matthias Klose wrote:
> Yann Dirson writes:
> > I have several packages (e2fsprogs, bigloo) that fail to build on
> > m68k, apparently due to one or more gcc bug(s). Maybe that's the same
> > as #146006, and #89023, but I can't tell that myself.
> >
> > M
Yann Dirson writes:
> I have several packages (e2fsprogs, bigloo) that fail to build on
> m68k, apparently due to one or more gcc bug(s). Maybe that's the same
> as #146006, and #89023, but I can't tell that myself.
>
> Madkiss suggested forcing the use of gcc-3.2. But if this compiler is
> offi
> Is there a way to determine the amount of free memory (including free
> swap)?
Absolutely; take a look at mach/mach.defs:vm_statistics and
.
pgpa45jjrq7pm.pgp
Description: PGP signature
5 matches
Mail list logo