Summary: | app-backup/bacula-5.0.3-r1 fails with USE="static" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | David Abbott <dabbott> |
Component: | [OLD] Unspecified | Assignee: | Thomas Beierlein <tomjbe> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | binki, tomka |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 341471 | ||
Attachments: |
build log
config log |
Description
David Abbott (RETIRED)
2010-10-21 09:42:57 UTC
Created attachment 251423 [details]
build log
Created attachment 251425 [details]
config log
Thanks for pointing that out David. Good catch. Just checked: It does also not work on (mostly) stable version 5.0.2-r2. (In reply to comment #0) > > configure: error: Libtool is enabled, not compatible with static tools, > please rerun configure with --disable-libtool > Since bacula-5.*.* upstream forces a complete static link to a lot of libs - even complete glibc. I just emailed to gentoo-dev about this, but I think the only option would be to mask the static use-flag, right? (In reply to comment #4) > I just emailed to gentoo-dev about this, but I think the only option would be > to mask the static use-flag, right? > I have not quite decided how to proceed. a) There seems to be not so much scenarios where you would need that feature. That means mask (or better drop) the flag would be good. b) A static linked file daemon may make sense for restoring a backup during disaster recovery. So we could restrict USE=static to work only for USE=bacula-clientonly. But there may be need for a lot of additional libs as a static version (e.g. openssl, readline, ...). (In reply to comment #5) > (In reply to comment #4) > > I just emailed to gentoo-dev about this, but I think the only option would be > > to mask the static use-flag, right? > > > I have not quite decided how to proceed. > > a) There seems to be not so much scenarios where you would need that feature. > That means mask (or better drop) the flag would be good. > > b) A static linked file daemon may make sense for restoring a backup during > disaster recovery. So we could restrict USE=static to work only for > USE=bacula-clientonly. But there may be need for a lot of additional libs as a > static version (e.g. openssl, readline, ...). (b) Seems to be not so much of a problem to me. glibc, readline, openssl, and any other package without a 'static-libs' use flag installs both the .a and the .so. It should be fine if we make sure to depend on the 'static-libs' use flag for libs that support it (I have not checked if this applies to any of the bacula deps) (In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #4) > > > I just emailed to gentoo-dev about this, but I think the only option would be > > > to mask the static use-flag, right? > > > > > I have not quite decided how to proceed. > > > > a) There seems to be not so much scenarios where you would need that feature. > > That means mask (or better drop) the flag would be good. > > > > b) A static linked file daemon may make sense for restoring a backup during > > disaster recovery. So we could restrict USE=static to work only for > > USE=bacula-clientonly. But there may be need for a lot of additional libs as a > > static version (e.g. openssl, readline, ...). > > (b) Seems to be not so much of a problem to me. glibc, readline, openssl, and > any other package without a 'static-libs' use flag installs both the .a and the > .so. It should be fine if we make sure to depend on the 'static-libs' use flag > for libs that support it (I have not checked if this applies to any of the > bacula deps) > OK, I will look for it next days. (In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #4) > > > I just emailed to gentoo-dev about this, but I think the only option would be > > > to mask the static use-flag, right? > > > > > I have not quite decided how to proceed. > > > > a) There seems to be not so much scenarios where you would need that feature. > > That means mask (or better drop) the flag would be good. > > > > b) A static linked file daemon may make sense for restoring a backup during > > disaster recovery. So we could restrict USE=static to work only for > > USE=bacula-clientonly. But there may be need for a lot of additional libs as a > > static version (e.g. openssl, readline, ...). > > (b) Seems to be not so much of a problem to me. glibc, readline, openssl, and > any other package without a 'static-libs' use flag installs both the .a and the > .so. It should be fine if we make sure to depend on the 'static-libs' use flag > for libs that support it (I have not checked if this applies to any of the > bacula deps) > Fixed in n new revision. USE=static is only supported if USE=bacula-clientonly. +*bacula-5.0.3-r2 (29 Dec 2010) + + 29 Dec 2010; Thomas Beierlein <tomjbe@gentoo.org> +bacula-5.0.3-r2.ebuild, + +files/5.0.3/bacula-5.0.3-fix-static.patch: + Fix USE=static - only supported for bacula-clientonly now. bug #341983. + Thanks dabbott@gentoo.org for reporting + |