public inbox for
 help / color / mirror / Atom feed
From: Andy Wingo <>
Subject: Re: Compiling guile-gobject experiences
Date: Mon, 04 Aug 2003 16:25:00 -0000	[thread overview]
Message-ID: <20030804162116.GA1217@lark> (raw)
In-Reply-To: <>

On Sat, 02 Aug 2003, Andreas Rottmann wrote:

> I've just tried a rebuild of a new guile-gobject CVS checkout. The
> build takes extremly long (I've cancelled it, after my machine started
> heavy trashing). The problem is the generated guile-gnome-gw-gtk.c,
> which has 154075 lines (:-O). 

This happens for me too, but only on gcc-3.3. If you try make with
gcc-3.2 (and even better with CC='ccache gcc-3.2'), the problem isn't
near so bad.

And my machine is low-end, these days anyway: a celeron 600 with 192
megs of ram.

But I do agree that it's a problem. I think reducing the size of the
generated code is the best solution, personally.

I'm glad to hear that you're compiling the code :-) I'd be pleased to
have you on as a co-maintainer if you're still interested. My internet
connection is spotty, and I'm about to go on holiday in a couple weeks,
for the record.


Andy (another one ;)

  reply	other threads:[~2003-08-04 16:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-02 17:17 Andreas Rottmann
2003-08-04 16:25 ` Andy Wingo [this message]
2003-08-04 16:58   ` Andreas Rottmann
2003-08-07  8:09     ` Andy Wingo
2003-08-07 11:18       ` Andreas Rottmann
2003-09-12 23:02   ` Kevin Ryde
2003-09-13 12:43     ` Marius Vollmer
2003-09-19  0:19       ` Kevin Ryde
2003-09-14 19:47     ` Andreas Rottmann
2003-09-15 17:59       ` GOOPS slowness [was: Compiling guile-gobject experiences] Andreas Rottmann
2003-09-19  0:18       ` Compiling guile-gobject experiences Kevin Ryde

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:

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

  git send-email \
    --in-reply-to=20030804162116.GA1217@lark \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).