Hallo Birger, On Wed, Nov 19, 2003, Birger Kr�gelin wrote: > I try to install an armored, minimal Solaris 9 environment with > OpenPKG (built for /opt/local). > If you are talking about a new Solaris installation with only 'core' or 'end user' solaris packages, then please publish your results. Most people don't like installing the 'entire distribution' or even 'developer system' Solaris packages, but nobody has had time to really find out the interpackage Solaris dependencies.
> When doing a rebuild for rsync (my current test scenario) > I get the following error message: > > configure: Configuring rsync 2.5.6 > checking build system type... sparc-sun-solaris2.9 > checking host system type... sparc-sun-solaris2.9 > checking target system type... sparc-sun-solaris2.9 > checking for gcc... /opt/local/bin/cc > checking for C compiler default output... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether /opt/local/bin/cc accepts -g... yes > checking how to run the C preprocessor... /lib/cpp > configure: error: C preprocessor "/lib/cpp" fails sanity check > error: Bad exit status from /opt/local/RPM/TMP/rpm-tmp.11852 (%build) > Here's how it should look. configure: Configuring rsync 2.5.6 checking build system type... sparc-sun-solaris2.9 checking host system type... sparc-sun-solaris2.9 checking target system type... sparc-sun-solaris2.9 checking for gcc... /cw/bin/cc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /cw/bin/cc accepts -g... yes checking how to run the C preprocessor... /cw/bin/cc -E It looks like you've bootstrapped the OpenPKG instance to /opt/local. In any case, the GCC compiler at /opt/local/bin/cc must work. To make sure that it can preprocess source code, type: $ /opt/local/bin/cc -E If this succeeds, then post the config.log from your failed rsync build. It should be in /opt/local/RPM/TMP/rsync-2.5.6/config.log. That should tell us why rsync can't use your 'cc -E' as the preprocessor, and why the /lib/cpp fails as well. Also, which version of OpenPKG are you using, and which rsync package? Regards, Michael -- [EMAIL PROTECTED] Development Team, Operations Northern Europe Cable & Wireless Telecommunications Services GmbH
pgp00000.pgp
Description: PGP signature
