Summary: | app-arch/rpm-4.4.1-r1 failed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Chris Smith <chris> |
Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | askwar, teidakankan, vapier, zmedico |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Chris Smith
2006-06-12 11:33:57 UTC
I had the same problem here with beecrypt-4.1.2-r1. However, it built fine with beecrypt-3.1.0-r2. (In reply to comment #1) > I had the same problem here with beecrypt-4.1.2-r1. However, it built fine with > beecrypt-3.1.0-r2. > In this case, I'd think, that it would be best, to make rpm conflict with beecrypt >3.1.0. Wouldn't this be the correct solution? (In reply to comment #2) > In this case, I'd think, that it would be best, to make rpm conflict with > beecrypt >3.1.0. Wouldn't this be the correct solution? Blockers are annoying. Maybe it's simpler to make the dependency more specific, such as =dev-libs/beecrypt-3.1*. Either that or fix rpm so that it builds with any version of beecrypt. (In reply to comment #3) > > Blockers are annoying. Agreed. > Maybe it's simpler to make the dependency more > specific, such as =dev-libs/beecrypt-3.1*. Either that or fix rpm so that it > builds with any version of beecrypt. Well, any chance to get this done "this century"? :) As you know, rpm compile fine with beecrypt 3.1.0, so it seems that it's not compatible with beecrypt 4.x. (In reply to comment #4) > Well, any chance to get this done "this century"? :) As you know, rpm compile > fine with beecrypt 3.1.0, so it seems that it's not compatible with beecrypt > 4.x. It's supposed to work with >=beecrypt-4.1.2, according to the following link: http://rpmfind.net//linux/RPM/fedora/updates/4/SRPMS/rpm-4.4.1-23.src.html Looking in rpmio_internal.h from the error message, I found this: #if HAVE_BEECRYPT_API_H #include <api.h> #else #include <beecrypt.api.h> #endif It seems that something is going wrong inside the configure script and preventing HAVE_BEECRYPT_API_H from being defined. Today I decided to remove beecrypt-4.1.2-r1 from my package.mask and try again. It worked! I built beecrypt-4.1.2-r1 and rpm-4.4.1-r1 built against it with no problems. Since the last try, I've stopped using confcache, but the OP doesn't have FEATURES=confcache so maybe that's not related... 4.4.6 should work fine |