I synced the Portage tree yesterday and got an updated libtool.eclass dated 9 June. When trying to build any packages that inherit it, Portage dies while evaluating the eclass. Reproducible: Always Steps to Reproduce: Emerge any package inheriting libtool.eclass. /usr/portage/eclass/libtool.eclass: line 34: syntax error near unexpected token `>' /usr/portage/eclass/libtool.eclass: line 34: ` ) &>> "${T}/elibtool.log"'
Created attachment 276473 [details] build log for sqlite
Created attachment 276475 [details] the offending libtool.eclass
Can you please attach emerge --info? Because none of my five systems here has trouble with that syntax.
I've switched to a safer syntax, but I'd still like to see your emerge --info.
Created attachment 276531 [details] output of emerge --info
I'm now getting a complaint about the same item on a different line; I don't think it was the parentheses: /usr/portage/eclass/libtool.eclass: line 32: syntax error near unexpected token `>' /usr/portage/eclass/libtool.eclass: line 32: ` &>> "${T}/elibtool.log"' It looks like it (bash?) doesn't like the second ">" in "&>>", and I don't see anything matching "&>>" in the list of esoteric redirections. What's it supposed to do?
Sigh, it looks like only bash4 supports that (which actually makes me wonder why you got bash 3 still).
Upgrading to bash-4 resolved the issue, and apparently that ebuild didn't trigger the bug. Not sure if this makes it "resolved" or "invalid", but my problem's fixed. Thanks!