In recent emerge build systems there are failures in emerging gst-plugins-mad and gstreamer. The failures happen in the "configure" step of the ebuilds. The key lines are:
gst-plugins-mad: case `(ac_space=' '; set | grep ac_space) 2>&1` in
gstreamer: for ac_var in `(set) 2>&1 | sed -n 's/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'`; do
Steps to Reproduce:
1. Have older version (~3.1?) of bash installed...
2. emerge gst-plugins-mad
3. emerge gstreamer
Both emerges will fail in the configure step.
Runing "sh configure" by hand will fail as well.
Packages should compile cleanly.
The problem is that bash seems to have been enhanced to allow `...` output in new places in the shell language. The packages will compile if one unmasks app-shells/bash and emerges a current bash (3.2_p9-r1) before emerging gst-plugins-mad or gstreamer. The build dependency processing needs to be changed to allow (or force) an upgrade to bash before emerging gst-plugins-mad or gstreamer.
Which versions is this about? Also post emerge --info and the actual errors here.