Summary: | dev-tcltk/expect-5.45 - Library path has a leading colon, incorrect TCL_CC_SEARCH_FLAGS? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | david van rood <genewitch> |
Component: | [OLD] Development | Assignee: | TCL/TK Project <tcltk> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | oas, ppc, tomwij |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
config.log |
Description
david van rood
2013-01-02 13:53:22 UTC
[ebuild U ] dev-tcltk/expect-5.45 [5.44.1.15] USE="-debug -doc -threads (-X%*)" Please attach the entire build log to this bug report. Please attach the entire build log to this bug report. Created attachment 334044 [details]
build.log
I think the error lies in
> if test "${TCL_LD_SEARCH_FLAGS}" = '-L${LIB_RUNTIME_DIR}'; then
> LIB_RUNTIME_DIR=`echo ${LIB_RUNTIME_DIR} |sed -e 's/:/ -L/g'`
> fi
in "configure.in", which looks like an upstream hack; I wouldn't be surprised this is supposed to run as a fix and it is simply that test that fails. I don't directly see a problem in the Makefile.in, so it probably is a mistake in one of the configure files.
So, can you also attach the work/config.log besides the temp/build.log?
Created attachment 334054 [details]
config.log
TCL_CC_SEARCH_FLAGS=':/usr/lib64' <--- this? Oh yeah, seems the block of code I pasted was TCL_LD_SEARCH_FLAGS, but indeed, that TCL_CC_SEARCH_FLAGS seems interesting; perhaps the same kind of replace is missing for that variable? Since this should be enough information, assigned this to the maintainers of this package. Might be a sed-error in configure.in line 960 LIB_RUNTIME_DIR=`echo ${LIB_RUNTIME_DIR} |sed -e 's/:/ -L/g'` where the colon is kept and not substituted with that "-L"…? I'm to lazy to read the whole info pages of sed ;-) Error appears in x86 too. I think its a duplicate. Please reemerge tcl and expect. if it still exist, please reopen. *** This bug has been marked as a duplicate of bug 449134 *** |