Stepan Kasal <[EMAIL PROTECTED]> writes: > well, it was me who created the controversy here. :-)
> I presume you use AC_CONFIG_LIBOBJ_DIR to specify a certain directory, > and then you call AC_LIBOBJ with object names (without any directory > components). Then you use LIBOBJS or LTLIBOBJS in the top directory. That was the goal, yes. > I think there is no doubt this should be supported. > The controversy is about implementation: current implementation uses > variable LIBOBJDIR to prepent the path, while I proposed that > ./configure would insert the directory part to the substituted > value of (LT)LIBOBJS. > It is possible that Autoconf/Automake will support multiple libobj > directories on future; in that case, the two possible implications > will have consequences for the shape of that support. > But the basic use case for AC_CONFIG_LIBOBJ_DIR shall continue to > work in either case. Oh, excellent. Then I will look forward with great eagerness to the next releases of Autoconf and Automake, and in the meantime continue to apply my patch to work around the problem. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
