public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mikael Hallendal <micke@hallendal.net>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] KDE .ebuilds $DEBUG support
Date: Sat Aug 25 04:53:01 2001	[thread overview]
Message-ID: <998744023.29705.9.camel@zoidberg> (raw)
In-Reply-To: <20010825043502.XGDZ2471.femail11.sdc1.sfba.home.com@there>

Den 25 Aug 2001 00:40:21 -0500 skrev Don Davies:
> Hi, devs
> 
> Dan Armak:
> 
> I think this would be a nice addition to the KDE .ebuilds.  The QT .ebuild
> has a similar provision.  This should provide performance gains, as well
> as reduce the compilation time, as I understand from reading posts on
> http://dot.kde.org.

Hi!

I generally agree to this and think this is the way to go (the same for
gnome-stuff). The only problem with this is that it's hell for us to
help users when they have problem since they can't provide any
information about what went wrong, only that something did went wrong.

I had a problem with Gnumeric the other day which was that it segfaulted
on one of my computer but not on the other. It turned out to be a bug in
Gnumeric (now fixed) but the reason it segfaulted on one of my computers
was that I had built glib with --disable-debug on the machine where it
segfaulted.

This is a performance-gain for the user and a real debugging-loss for
us. :) Most other distributions build with --enable-debug ASAIK.

Regards,
  Mikael Hallendal

-- 
Mikael Hallendal              http://micke.hallendal.net/
Stockholm, Sweden             Cell: +46 (0)709 718 918







      parent reply	other threads:[~2001-08-25 10:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-24 22:36 [gentoo-dev] KDE .ebuilds $DEBUG support Don Davies
2001-08-25  2:13 ` Dan Armak
2001-08-25 10:41   ` tadpol
2001-08-25 16:44     ` Dan Armak
2001-08-25  4:53 ` Mikael Hallendal [this message]

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=998744023.29705.9.camel@zoidberg \
    --to=micke@hallendal.net \
    --cc=gentoo-dev@cvs.gentoo.org \
    /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