| 1 |
Is anyone else seeing this problem? I've been unable to build the |
| 2 |
latest version of rpm (rpm-4.0.4-r2) on three seperate machines. Two are x86 |
| 3 |
machines with the same compiler flags (686 optimized binaries) and my |
| 4 |
TiBook with ppc optimizations. Both break in the same way. Here's what |
| 5 |
I do: |
| 6 |
emerge rsync && emerge rpm |
| 7 |
|
| 8 |
Rpm compiles for quite a while and eventually hits a brick wall with the |
| 9 |
following output: |
| 10 |
|
| 11 |
------(snip)------ |
| 12 |
dbconfig.c: In function `prDbiOpenFlags': |
| 13 |
dbconfig.c:531: `POPT_BIT_SET' undeclared (first use in this function) |
| 14 |
make[2]: *** [dbconfig.lo] Error 1 |
| 15 |
make[2]: Leaving directory `/var/tmp/portage/rpm-4.0.4-r2/work/rpm-4.0.4/rpmdb' |
| 16 |
make[1]: *** [all-recursive] Error 1 |
| 17 |
make[1]: Leaving directory `/var/tmp/portage/rpm-4.0.4-r2/work/rpm-4.0.4' |
| 18 |
make: *** [all-recursive-am] Error 2 |
| 19 |
|
| 20 |
!!! ERROR: the make command did not complete successfully. |
| 21 |
!!! ("make") |
| 22 |
!!! Since this is a critical task, ebuild will be stopped. |
| 23 |
|
| 24 |
!!! emerge aborting on /usr/portage/app-arch/rpm/rpm-4.0.4-r2.ebuild . |
| 25 |
------(snip)------ |
| 26 |
|
| 27 |
It seems to be a bad release of rpm. Maybe it should be masked off? This |
| 28 |
is very frustrating because kdeadmin and kde both depend on rpm to build. |
| 29 |
Thanks. |
| 30 |
|
| 31 |
-Brian Rzycki |
Archives