Summary: | sys-libs/ntdb-1.0-r1: sh: /.../ntdb-run-001-encode: No such file or directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Patrick Lauer <patrick> |
Component: | [OLD] Unspecified | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | DuPol, levertond, samba, vina, xmw |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 683926 | ||
Bug Blocks: | |||
Attachments: |
configure with --enable-developer to allow tests to be run
alternative: manually add the option DEVELOPER_MODE |
Description
Patrick Lauer
2015-06-28 01:30:34 UTC
Created attachment 460196 [details]
configure with --enable-developer to allow tests to be run
Only if the option DEVELOPER_MODE is set in $BUILD_DIR/bin/c4che/default.cache.py
then the build script $BUILD_DIR/wscript does compile the files that are necessary
for running the tests.
One way to set this option is by adding the parameter --enable-developer during
configure (see attached file ntdb-1.0-r2.ebuild). But apart from some additional
warnings that will be emited at build time, the code will also be built with
-fno-common and -g.
This leads to binaries that are twice as large on my system (abi_x86_64.amd64).
Fortunately, no further files will be added to the package.
Created attachment 460198 [details]
alternative: manually add the option DEVELOPER_MODE
Instead, I propose to just manually add the option DEVELOPER_MODE to
$BUILD_DIR/bin/c4che/default.cache.py (see attached file ntdb-1.0-r3.ebuild),
as this just allows the tests to be run without changing the compile options.
same error on ppc and ppc64 sys-libs/ntdb s about to get treecleaned. |