Hi. I haven't been able to find mention of this problem elsewhere: on
Solaris 8, my autoconf-generated configure script fails to relate test
results to the generated config.h file.
However, removing config.cache and re-running configure *does*
generate a correct config.h file. This pattern is
Akim Demaille <[EMAIL PROTECTED]> writes:
> Hi!
>
> Sorry, but if you want help, you need to help us. We have little
> time.
Sure. :) (I know the feeling.)
> What version of Autoconf?
I used both 2.13 and 2.50 with the same results for both versions.
...
> Could you send the two versions o
The problem is back (probably it was a fluke that it went away), so
I'm sending specifics. This is a Solaris 8 machine on SPARC in the
sourceforge compile farm.
Recap of problem: configure script doesn't generate config.h on the
basis of results from tests. Removing config.cache and rerunning
c
Russ Allbery <[EMAIL PROTECTED]> writes:
> Mike Castle <[EMAIL PROTECTED]> writes:
>
> > Personally, I'd vote for getting rid of AC_C_BIGENDIAN. No need to in
> > supporting poor programming.
>
> I use it to allow more optimized versions of algorithms like MD5 where you
> can skip additional m
Akim Demaille <[EMAIL PROTECTED]> writes:
> | Recap of problem: configure script doesn't generate config.h on the
> | basis of results from tests. Removing config.cache and rerunning
> | configure yeilds a correct config.h.
> |
> | > What version of Autoconf?
> |
> | 2.13 and 2.50.
>
> Hm...
Akim Demaille <[EMAIL PROTECTED]> writes:
> >>>>> "Ed" == Ed L Cashin writes:
>
> Ed> I've found that saying "test -r" is not reliable on Solaris.
>
> Huh?
Sorry, I think I was confusing "test -e" with "test
