Summary: | mail-mta/exim 4.72 fails to build with radius support | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gergely POLONKAI <polesz> |
Component: | [OLD] Server | Assignee: | Fabian Groffen <grobian> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | net-mail+disabled |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log from this particular emerge
build.log from this particular emerge - English |
Description
Gergely POLONKAI
2010-10-29 12:12:51 UTC
Created attachment 252471 [details]
build.log from this particular emerge
Attached my build.log from this emerge
Hi, can you please rerun your emerge with LANG=C LC_ALL=C emerge -v1 ... So everybody can understand the error messages. Thanks Created attachment 252483 [details]
build.log from this particular emerge - English
Sorry, I forgot about that...
In file included from call_radius.c:41: /usr/include/radiusclient.h:343: error: conflicting types for 'ENV' /usr/include/db.h:181: note: previous declaration of 'ENV' was here sys-libs/db and net-dialup/radiusclient own the header files in conflict. Apparently 4.7 versions of db added a typedef ENV, which radiusclient was already using. Although it really wasn't a great idea for either one to pollute the namespace by defining 'ENV', Berkeley db is by far the more widely used library, so it makes sense to resolve the conflict by renaming ENV in radiusclient. Unfortunately radiusclient doesn't seem to have an upstream, so this might serve as motivation for packages using radiusclient to switch to radiusclient-ng. Assigning to exim maintainers, who can either ditch radiusclient or bug the radiusclient maintainers to apply a conflict-resolving patch. *** This bug has been marked as a duplicate of bug 287426 *** since radiusclient-ng seems to be dead too, and merged and continuing in FreeRADIUS, probably *that* should be used. |