Summary: | bash-3.2 improperly parses # in backticks `...` | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Bob Reveley <bob> |
Component: | [OLD] KDE | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | btsht23, bujdoso, david.gurvich, dma147, giacomo_giorgianni, jakub, kde, leon_es00-g2, manschwetus, miker, tonglebeak |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://lists.gnu.org/archive/html/bug-bash/2006-10/msg00046.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 151149 | ||
Attachments: | kdebase-3.5.5 config.log |
Description
Bob Reveley
2006-10-13 01:38:26 UTC
Did you upgrade to bash-3.2 ? I also have the same problem with using kdebase-meta. To be more precise kde-base/kdepasswd fails. I'm using ~amd64, and I have upgraded to bash 3.2 *** Bug 151109 has been marked as a duplicate of this bug. *** *** Bug 151152 has been marked as a duplicate of this bug. *** *** Bug 151099 has been marked as a duplicate of this bug. *** I'd masked =app-shells/bash-3.2 localy in /etc/portage/package.mask Now all problematic ebuilds are compiling as they should. (In reply to comment #1) > Did you upgrade to bash-3.2 ? > In the process of running an 'emerge --sync' then 'emerge -uDv world', bash-3.2 ran first. After reporting the bug, I ran 'etc-update', which updated some kde files and then again ran 'emerge -uDv world'. Kdebase-3.5.5 failed in the same place. Just FYI, bash-3.2 is now package.masked Created attachment 99527 [details]
kdebase-3.5.5 config.log
Seems like I found the problem, and this is bash-style breakage of rules.. ac_cv_maxpathlen=`sed 's#KDE_HELLO ##' conftest.out` bash handles one of the # as a comment separator (probably the one with a space before it), even if it's in a non-expansion string (''): :3: checking for MAXPATHLEN checking for MAXPATHLEN... test.bash: line 30: unexpected EOF while looking for matching ``' test.bash: line 39: syntax error: unexpected end of file zsh, BSD's ash, bb and bash < 3.2 handle the thing correctly, but bash 3.2 seems not to. I can work it around, but seems like a bug to me. Bad bash! (In reply to comment #10) > :3: checking for MAXPATHLEN > checking for MAXPATHLEN... > test.bash: line 30: unexpected EOF while looking for matching ``' > test.bash: line 39: syntax error: unexpected end of file > > zsh, BSD's ash, bb and bash < 3.2 handle the thing correctly, but bash 3.2 > seems not to. > > I can work it around, but seems like a bug to me. Bad bash! Doesn't your test say that it's a "`" that it can't find the match for rather than "#"? Looks like I backup to bash-3.1_p17 to get a look at kde-3.5.5. It can't find ` because the closing ` is considered out of the comment. The error appears about 1000 lines below the point where MAXPATHLEN test is started (which fooled me up for a bit) because it needs to close first a ' and then a `. (In reply to comment #12) Right. Bad bash. Looks like we'll get a better bash out of it. Good lookin' out. *** Bug 151178 has been marked as a duplicate of this bug. *** *** Bug 151195 has been marked as a duplicate of this bug. *** *** Bug 151193 has been marked as a duplicate of this bug. *** *** Bug 151204 has been marked as a duplicate of this bug. *** *** Bug 151258 has been marked as a duplicate of this bug. *** fixed with bash-3.2_p1 *** Bug 152146 has been marked as a duplicate of this bug. *** |