public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: Enabling debug info in Wine?
Date: Fri, 7 Mar 2008 18:54:20 +0000 (UTC)	[thread overview]
Message-ID: <pan.2008.03.07.18.54.19@cox.net> (raw)
In-Reply-To: 5bdc1c8b0803070921xbc44366we4b3d6b3d9615bfd@mail.gmail.com

"Mark Knecht" <markknecht@gmail.com> posted
5bdc1c8b0803070921xbc44366we4b3d6b3d9615bfd@mail.gmail.com, excerpted
below, on  Fri, 07 Mar 2008 09:21:51 -0800:

> I'm not finding confcache or anything that's the obvious right choice on
> that one. I'll emerge ccache though.

Yeah... confcache was an experiment that has been shelved for the time 
being.  It was designed to cache the results of various config tests 
repeated for many/most ebuilds, only dumping the cache and letting them 
retest from scratch when required (if something in the build system, say 
gcc or whatever, changed).  The problem was that a number of packages put 
bad data in the cache/database, but compiled fine themselves, thereby 
leaving the bad data to be found by the next package that tried a test 
with the same data.  Since this might be the first package after or the 
100th, it was difficult to figure out where the bad data was coming from 
in ordered to fix it.  The result was basically packages failing because 
they got a bad config, with no easy way to trace it, so they just masked 
confcache.

Advanced users can still use it if they want, using package.unmask (they 
may need to find an ebuild too, as I'm not sure whether it's still in 
portage but masked, or not even there now, but it's available in the 
archives if necessary), but they have to be prepared to manually dump the 
confcache database and try again if problems appear.  I ran it for 
awhile, but after my upgrade to dual dual-cores, decided the machine was 
fast enough at running the configs that it wasn't worth the hassle any 
more, so I turned off the feature and unmerged the confcache package.

For people who'd prefer to have portage "just work" with the least 
hassle, even if it takes a bit longer on some packages, confcache is 
definitely something you want to leave alone, at least for now.  Maybe 
someday...

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@lists.gentoo.org mailing list



  reply	other threads:[~2008-03-07 18:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07 16:09 [gentoo-amd64] Enabling debug info in Wine? Mark Knecht
2008-03-07 16:47 ` [gentoo-amd64] " Mark Knecht
2008-03-07 16:59   ` Chris Brennan
2008-03-07 17:21     ` Mark Knecht
2008-03-07 18:54       ` Duncan [this message]
2008-03-07 19:03         ` Mark Knecht
2008-03-07 19:05           ` Mark Knecht
2008-03-08  1:15             ` Duncan
2008-03-08  5:06               ` Duncan
2008-03-08 18:40                 ` Mark Knecht
2008-03-09  0:15                   ` Duncan

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=pan.2008.03.07.18.54.19@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@lists.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