Circular dependencies and test programs

2007-10-20 Thread Michael B Allen
Hi, I have two libraries liba and libb. I would like liba to call a function in libb but libb is linked with liba. So I have a circular dependency. Normally this is not a problem because the linker doesn't try to resolve dependencies when linking libraries. But here's the problem: liba uses libto

Forcing an AC_CHECK to fail

2007-10-20 Thread Michael B Allen
Hey, I have a package that uses AC and checks for a lib but the package also has it's own implementation of that lib. I have the said lib installed on the system but I want autoconf to fail that check and used the one provided in the package. So is there a way to tell a specific check to fail? M

Re: Circular dependencies and test programs

2007-10-20 Thread Michael B Allen
Nuts. On 10/20/07, Bob Friesenhahn <[EMAIL PROTECTED]> wrote: > My best advice is to change the design of your libraries to avoid the > circular dependencies.

Re: Forcing an AC_CHECK to fail

2007-10-20 Thread Michael B Allen
On 10/20/07, Andreas Schwab <[EMAIL PROTECTED]> wrote: > > So is there a way to tell a specific check to fail? > > You can preset the cache variable before running configure. Excellent! So how to do I preset a cache variable before running configure? Mike

Re: Forcing an AC_CHECK to fail

2007-10-20 Thread Michael B Allen
On 10/20/07, Andreas Schwab <[EMAIL PROTECTED]> wrote: > "Michael B Allen" <[EMAIL PROTECTED]> writes: > > > So how to do I preset a cache variable before running configure? > > You can put it in the environment, or use config.site. See > (autoconf)Site

Re: Circular dependencies and test programs

2007-10-20 Thread Michael B Allen
On 10/20/07, Ben Pfaff <[EMAIL PROTECTED]> wrote: > "Michael B Allen" <[EMAIL PROTECTED]> writes: > > > But here's the problem: liba uses libtool / automake and builds a > > number of test programs not just by configure but by liba's test suite &g