I think if you edit acconfig.h in the root of the OpenDX source tree and add "#undef SunOS" down where its undeffing ibm6000, intelnt, cygwin and linux, all will be well. Don't ask me why.
Greg David Starks-Browning <[EMAIL PROTECTED]>@opendx.watson.ibm.com on 04/11/2001 11:02:00 AM Please respond to [email protected] Sent by: [EMAIL PROTECTED] To: [email protected] cc: Subject: Re: [opendx-dev] autoheader error I've re-installed GNU m4-1.4, automake-1.4, and autoconf-2.13. I still get the exact same error when I run ./CVSMake: aclocal && \ autoheader && \ automake -a -i && \ autoconf Are you sure it's a problem with my installation? If it is, can anyone help me fix it? I don't know what else to do besides (re-)install these tools. I'm sorry to be so helpless here. Thanks, David On Tuesday 10 Apr 01, David Thompson writes: > This is a problem with your autoconf tools setup. But as for the > AC_TRY_RUN warnings, you can ignore them. > > David > > >Greetings, > > > >I'm attempting to build dx from CVS, checked out today. When I run > >./CVSMake, I get the following error from autoheader: > > > >configure.in:873: warning: AC_TRY_RUN called without default to allow cross compiling > >configure.in:899: warning: AC_TRY_RUN called without default to allow cross compiling > >/sw/arch/bin/autoheader: Symbol `SunOS' is not covered by /sw/common/share/autoconf/acconfig.h ./acconfig.h > > > >(BTW, should I ignore the warnings?) > > > >This is GNU autoconf-2.13 and GNU m4-1.4. Whatever platform I try > >(SunOS, OSF1, IRIX64, Linux), I get similar errors, with the > >corresponding uname result substituted in the error message. > > > >I searched the mail archives, but did not find a similar complaint. > >(At least, not about a `uname` symbol.) > > > >I am a complete novice when it comes to autoconf tools. Is this a > >problem with dx, or with our autoconf installation? > > > >Should I have ignored the error and done the rest of the CVSMake > >commands manually? (They abort at autoheader because it returns 1.)
