When I had to work with autoconf'd packages, I found that they worked (most times) for platforms already considered by the package maintainers. Auto* was a big obstacle otherwise. In general, I ended up removing most of the #ifdef code once I found which symbols were in place for the platform I had to cope with.
When having to deal with several platforms, I applied the same technique to lead to different .c files for the different platforms. This worked well for me. On 5/8/06, Jack Johnson <[EMAIL PROTECTED]> wrote:
On 5/8/06, LiteStar numnums <[EMAIL PROTECTED]> wrote: > seems. So for the half > our conformity test/configuration, it still wouldn't actually tell me what > was really missing, which was > fun because it kept passing the thread test sections... So, it sounds like autoconf may function as intended but perhaps the person who wrote the test needs some help? Given that progress is likely to be evolutionary rather than revolutionary, what kind of system or environment do you see that has potential to wean people from autoconf with as minimal hassle as possible? If I'm engrossed in autoconf hell for whatever reason -- say I'm the Firefox build maintainer, for instance -- what does the path out look like? -Jack
