After upgrading snv_128a to snv_129 via image-update, a call to apxs within the httpd test framework fails because /usr/ucb/echo isn't found:
/usr/apache2/2.2/bin/apxs -D APACHE2 -I/export/home/trawick/svn/httpd-test/c-modules -c mod_echo_post_chunk.c /usr/apr/1.3/build/libtool --silent --mode=compile cc -m32 -prefer-pic -xO3 -m32 -xchip=pentium -xspace -Xa -xildoff -xc99=all -DSSL_EXPERIMENTAL -DSSL_ENGINE -xO4 -DSOLARIS2=11 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -mt -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/apache2/2.2/include -I/usr/apr/1.3/include -I/usr/apr-util/1.3/include -I/usr/include -I/export/home/trawick/svn/httpd-test/c-modules -DAPACHE2 -c -o mod_echo_post_chunk.lo mod_echo_post_chunk.c && touch mod_echo_post_chunk.slo /usr/apr/1.3/build/libtool: line 790: /usr/ucb/echo: No such file or directory /usr/apr/1.3/build/libtool: line 957: /usr/ucb/echo: No such file or directory /usr/apr/1.3/build/libtool: line 958: /usr/ucb/echo: No such file or directory /usr/apr/1.3/build/libtool: line 1101: /usr/ucb/echo: No such file or directory ... Installing SUNWscp resolves the problem. This is apparently a packaging change, as I don't recall any manual intervention being required before. I doubt there's any special reason libtool needs to use /usr/ucb/echo; I guess it was the first [suitable] echo found in the build environment. I don't know enough about the build environment to suggest what needs to change.
