Summary: | x11-libs/vte-0.36.2: ../libtool: eval: line 1085: syntax error near unexpected token `|' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Craig Andrews <candrews> |
Component: | [OLD] Library | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | candrews |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
config.log |
Description
Craig Andrews
2014-06-05 01:58:09 UTC
Created attachment 378294 [details]
build.log
This is very similar to issue 459592 (which is also not yet fixed, but has a comment saying that adding eautoreconf would solve the problem) > checking command to parse /usr/bin/x86_64-pc-linux-gnu-nm -B output from x86_64-pc-linux-gnu-gcc object... failed
If it doesn't come down to '-flto', then most likely reason for this (and your other similar bugs) is the reported many times over the years problem with SystemRescueCD setting 'path'.
*** This bug has been marked as a duplicate of bug 463348 *** I have never used SystemRescueCD and I have lto disabled for this package and for the others I reported the libtool bug about (you can see in build.log that there is no lto). Attach config.log then - let's see the reason behind the failure. Created attachment 378326 [details]
config.log
Thanks for looking into this - I've attached config.log.
configure:6753: /usr/bin/x86_64-pc-linux-gnu-nm -B conftest.o \| sed -n -e 's/^.*[ ]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][ ]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p' | sed '/ __gnu_lto/d' \> conftest.nm configure:6756: $? = 0 cannot run sed -n -e 's/^.*[ ]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][ ]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p' | sed '/ __gnu_lto/d' ... I'd say the result is inconclusive. Take a look at _LT_CMD_GLOBAL_SYMBOLS part of libtool.m4 and try to figure out why does this part fail. |