>But shouldn't absolute names work as arguments to -I, or in CCLD >settings? >From the point of oure building, you are right: there is absolute no difference in using relative or absolute pathes. However, there might be some differences in the usability of the binary output and I think this is what Steffen is referencing. 1) cross compiling on linux using a windows compiler (e.g. cl.exe from microsoft) via wine command line. wine uses some internal tricks to translate absolute unix pathes to dos compliant ones. these translated pathes are stored in the compiled binaries, e.g. the debugging information. using these binaries later in debugger requires to have exactly the same drive mapping which wine used internally. This is normally no problem with relative pathes, since they aren't mapped usually. 2) you might like to be able to move a configured directory to somewhere else and still be able to use it. For both reasons we try to avoid absolute pathes. But thanks a lot for the idea of transporting the top configure's directory. I will give it a try. regards, Carsten _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
