public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hobbs, Timothy" <thobbs@netegrity.com>
To: "'gentoo-dev@gentoo.org'" <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] galeon install fails again
Date: Fri, 7 Dec 2001 07:55:55 -0500	[thread overview]
Message-ID: <ADBD32FDF8D3D311913400508B8BFFA4013EDE46@maex01.security.com> (raw)

db1 and db3 are not compatible.
Check your USE var and optionally just emerge the db-1.85-r1.ebuild.

It looks like the dependancy tree is:
galeon needs mozilla
mozilla needs perl
perl needs either berkley db, both versions 1 and 3 or gdbm, depending on
your USE var. (berkdb | gdbm)

-tim

> -----Original Message-----
> From: Collins Richey [mailto:erichey2@attbi.com] 
> Sent: Friday, December 07, 2001 6:34 AM
> To: gentoo
> Subject: [gentoo-dev] galeon install fails again
> 
> 
> When will the galeon ebuild ever actually work?
> 
> galeon-1.0.ebuild results in 
> 
> /usr/bin/ld: cannot find -ldb1
> collect2: ld returned 1 exit status
> 
> I don't find any dependancy in the geleon ebuild for this.  I 
> have the db-3.2.3h-r4.ebuild merged.
> 
> What's missing?
> 
> --
> Collins Richey
> Denver Area - WWTLRD
> gentoo_rc6 k2.4.17-pre2+ext3+xfce+sylpheed+galeon
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org 
> http://lists.gentoo.org/mailman/listinfo/gento> o-dev
> 


             reply	other threads:[~2001-12-07 14:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07 12:55 Hobbs, Timothy [this message]
2001-12-08  1:56 ` [gentoo-dev] galeon install fails again Mikael Hallendal
  -- strict thread matches above, loose matches on Subject: below --
2001-12-07 11:33 Collins Richey
2001-12-08  1:58 ` Mikael Hallendal

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=ADBD32FDF8D3D311913400508B8BFFA4013EDE46@maex01.security.com \
    --to=thobbs@netegrity.com \
    --cc=gentoo-dev@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