On Mon, Jul 24, 2006 at 01:30:52PM +0400, Nikita V. Youshchenko wrote: > dpkg-buildpackage from dpkg-cross just sets DEB_HOST_* variables in > cross-compilation case, the rest is done by normal dpkg-buildpackage. > > Gccross is substituted similar to tools like distcc or ccache - by > prepending to PATH a directory that has symlinks to gccross named "gcc", > "g++", "$target-gcc", "$target-g++" and similar. Those are prepared by > dpkg-cross version of dpkg-buildpackage. > When started, gccross checks command line, replaces paths from -I and -L > args if those don't point to cross-compilation dirs, and calls next > argv[0] in path.
Thanks for the explanation! > See above. I still agree with Raphael (gccross author) that this should be > enabled by default - at least until (almost) all debian packages will > cross-compile without it. That's ok with me, you might not want to immediately hack the caller of dpkg-buildpackage. But I support your idea to have an option to disable gccross -- otherwise I don't see a way how people could migrate their packages away from it. With kind regards, Baurzhan. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
