public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: bmr@zenmonkey.org (Brian M. Rzycki)
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] problems with rpm ebuild?
Date: Tue, 11 Jun 2002 09:00:16 -0500	[thread overview]
Message-ID: <20020611140016.GA23538@bmr.zenmonkey.org> (raw)

Is anyone else seeing this problem?  I've been unable to build the
latest version of rpm (rpm-4.0.4-r2) on three seperate machines.  Two are x86
machines with the same compiler flags (686 optimized binaries) and my
TiBook with ppc optimizations.  Both break in the same way. Here's what
I do:
emerge rsync && emerge rpm

Rpm compiles for quite a while and eventually hits a brick wall with the
following output:

------(snip)------
dbconfig.c: In function `prDbiOpenFlags':
dbconfig.c:531: `POPT_BIT_SET' undeclared (first use in this function)
make[2]: *** [dbconfig.lo] Error 1
make[2]: Leaving directory `/var/tmp/portage/rpm-4.0.4-r2/work/rpm-4.0.4/rpmdb'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/rpm-4.0.4-r2/work/rpm-4.0.4'
make: *** [all-recursive-am] Error 2

!!! ERROR: the make command did not complete successfully.
!!! ("make")
!!! Since this is a critical task, ebuild will be stopped.

!!! emerge aborting on  /usr/portage/app-arch/rpm/rpm-4.0.4-r2.ebuild .
------(snip)------

It seems to be a bad release of rpm.  Maybe it should be masked off?  This
is very frustrating because kdeadmin and kde both depend on rpm to build.
Thanks.

-Brian Rzycki


                 reply	other threads:[~2002-06-11 14:00 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=20020611140016.GA23538@bmr.zenmonkey.org \
    --to=bmr@zenmonkey.org \
    --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