Bug 202830 - dev-libs/xerces-c-2.8.0 tries to use /usr/bin/true
|
Bug#:
202830
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: cpp@gentoo.org
|
Reported By: mikachu@gmail.com
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: dev-libs/xerces-c-2.8.0 tries to use /usr/bin/true
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2007-12-19 23:25 0000
|
>>> Unpacking xerces-c-src_2_8_0.tar.gz to /neko/tmp/portage/dev-libs/xerces-c-2.8.0/work
* Applying xerces-c-2.8.0-64bit_cast.patch ...
[ ok ]
* Applying xerces-c-2.8.0-icu_ressource_fix.patch ...
[ ok ]
>>> Source unpacked.
>>> Compiling source in /neko/tmp/portage/dev-libs/xerces-c-2.8.0/work/xerces-c-src_2_8_0 ...
./runConfigure: line 800: /usr/bin/true: No such file or directory
*
* ERROR: dev-libs/xerces-c-2.8.0 failed.
* Call stack:
* ebuild.sh, line 46: Called src_compile
* environment, line 2642: Called die
* The specific snippet of code:
* ./runConfigure -p ${target} -c "$(tc-getCC)" -x "$(tc-getCXX)"
${myconf} -m ${mloader} -n ${netaccessor} -t ${transcoder} -r ${thread} -b
${bitstobuild} > configure.vars || diefunc "$FUNCNAME" "$LINENO" "$?"
"runConfigure failed";
* The die message:
* runConfigure failed
*
* If you need support, post the topmost build error, and the call stack if
relevant.
* A complete build log is located at
'/neko/tmp/portage/dev-libs/xerces-c-2.8.0/temp/build.log'.
* The ebuild environment file is located at
'/neko/tmp/portage/dev-libs/xerces-c-2.8.0/temp/environment'.
*
After symlinking /bin/true into /usr/bin/ the package installed successfully.
Apparently the ebuild is responsible for this:
src_unpack() {
unpack ${A}
cd "${S}"
sed -i \
-e 's|sh ./configure.*|/usr/bin/true|' \
src/xercesc/runConfigure || die "sed failed"
Should we modify the ebuild? It emerged fine on amd64 but its a
problem on x86
Ive removed the true part from the ebuild and it seems to compile,
not sure what that does though
@Billy: It's not an arch-issue. Seems that I had a stalled symlink from
/usr/bin/true to /bin/true and it seems you have that one too on one of your
machines.
Removing the part results in ./configure being run twice, not really usefull
but it doesn't hurt either.
Anyway, should be solved now. Thanks.
*** Bug 202923 has been marked as a duplicate of this bug. ***
*** Bug 202923 has been marked as a duplicate of this bug. ***