>OSes *with* ruserpass() will probably build (but will be using the wrong >ruserpass()) in the first case. Again, Shantonu, looks like your libmts.a >has circular dependencies with libmh.a. If you want to change how SASL works in terms of using ruserpass(), I'd be willing to do that. BTW ... after this is all fixed, can we do a new nmh release? Please? :-) --Ken
- Circular dependency in libmh.a and libmts.a causes build to ... Dan Harkless
- Re: Circular dependency in libmh.a and libmts.a causes ... Dan Harkless
- Re: Circular dependency in libmh.a and libmts.a causes ... Ken Hornstein
- Re: Circular dependency in libmh.a and libmts.a causes ... Dan Harkless
- Re: Circular dependency in libmh.a and libmts.a causes ... Shantonu Sen
- Re: Circular dependency in libmh.a and libmts.a causes ... Dan Harkless
- Re: Circular dependency in libmh.a and libmts.a causes ... Shantonu Sen
- Re: Circular dependency in libmh.a and libmts.a causes ... Dan Harkless
- Re: Circular dependency in libmh.a and libmts.a causes ... Dan Harkless
