public inbox for gentoo-osx@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grobian <grobian@gentoo.org>
To: gentoo-osx@lists.gentoo.org
Cc: Michael Haubenwallner <michael.haubenwallner@salomon.at>
Subject: Re: [gentoo-osx] PREFIX the next generation...
Date: Wed, 21 Dec 2005 14:26:29 +0100	[thread overview]
Message-ID: <20051221132629.GJ6329@gentoo.org> (raw)
In-Reply-To: <e36b84ee0512201609k787631d2o9b6072aa4dc426c1@mail.gmail.com>

On 20-12-2005 16:09:47 -0800, m h wrote:
> still chugging.  Upto 550Megs of memory for configure.... I guess I
> need to see what is really going on here...

I have my suspicions that configure is in a loop generating
configure.lineno.  It seems the configure.lineno is always super recent
if I kill it, and the growing memory behaviour would match with
configure for some daft reason going recursive on itself... :(

No clue why or how to fix it for now...
-- 
gentoo-osx@gentoo.org mailing list



  parent reply	other threads:[~2005-12-21 13:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-19 21:07 [gentoo-osx] PREFIX the next generation m h
2005-12-19 21:21 ` [gentoo-osx] " m h
2005-12-19 21:26   ` m h
2005-12-19 21:30     ` Grobian
2005-12-19 21:25 ` [gentoo-osx] " Grobian
2005-12-19 22:49   ` m h
2005-12-19 23:20     ` Kito
2005-12-20  1:33       ` m h
2005-12-20  6:32         ` Grobian
2005-12-20  9:23           ` Grobian
2005-12-20 20:11             ` m h
2005-12-20 20:53               ` Grobian
2005-12-20 23:00                 ` m h
2005-12-20 23:20                   ` m h
2005-12-21  0:09                     ` m h
2005-12-21 12:50                       ` Grobian
2005-12-22  6:57                         ` Brian Harring
2005-12-22  7:02                           ` Brian Harring
2005-12-22 10:35                             ` Grobian
2005-12-21 13:26                       ` Grobian [this message]
2005-12-20 22:18               ` Kito
2005-12-20 22:22                 ` Kito
2005-12-21  9:39     ` Michael Haubenwallner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051221132629.GJ6329@gentoo.org \
    --to=grobian@gentoo.org \
    --cc=gentoo-osx@lists.gentoo.org \
    --cc=michael.haubenwallner@salomon.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox