public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Chad M. Huneycutt" <chad.huneycutt@acm.org>
To: gentoo-dev <gentoo-dev@cvs.gentoo.org>
Subject: [gentoo-dev] Some bugs
Date: Wed Jul 18 19:14:02 2001	[thread overview]
Message-ID: <3B563352.6030909@acm.org> (raw)

Hi everyone,
   I have been lurking for a couple of months, but I finally got around 
to installing from the build CD this past weekend.  I thought I would go 
about my emerges a little skewed and see if I could shake out a few 
bugs, and I have managed to find a couple.  Overall, everything has gone 
amazingly smoothly. Great job!

Here are my bugs:
1. permissions on /etc/env.d/00basic are different than the other files 
in that directory
2. Instead of slowly installing, kdecore, kdelibs, etc.  I decided to 
just go for a big 'emerge koffice-2.1.1_beta3-r1.ebuild to see what 
would happen.  Everything compiled and installed (apparently fine) 
except for koffice itself.  So either the ebuild is busted or there is a 
missing dependence (or both).  I was not able to capture the output, but 
there were some missing symbols.  Maybe tonight I will let it run and 
catch the output
3. emerge mozilla-0.9.2.ebuild compiles and installs, but it will not 
run (segfaults)
4. bitchx-gtk seems to need a dependence on esound and gnome-libs 
(libzvt, in particular), but even after I emerge those it fails.  It 
always fails when trying to compile the esd test program.
5. It was solved earlier today on this list, but I was also having 
problems getting AA fonts in KDE.

That's all for now. Thanks,
   Chad (Bab5Freak on #gentoo)




                 reply	other threads:[~2001-07-19  1:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3B563352.6030909@acm.org \
    --to=chad.huneycutt@acm.org \
    --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