[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#373193: About #373193

Hello Nikita,

On Sun, Jul 23, 2006 at 11:57:40PM +0400, Nikita V. Youshchenko wrote:
> Starting with dpkg-cross 1.29, usage of gccross wrapper should be seen very 
> well in the build log.

Great! Unfortunately, I may not be able to test that soon.

> - add code to gccross that will try to detect the exact situation as 
> described in the bug, and not mangle paths if they look like old 
> cross-compilation setup,

I don't think it is worth the effort. That's unstable, after all.

> - add option to dpkg-buildpackage not to use gccross

I'd like to understand how that works first. dpkg-cross's
dpkg-buildpackage wrapper uses gccross if -a arch != $build has been
requested? dpkg-bp calls configure with (possibly implicit) --host
$build --build $build? dpkg-bp calls rules with CC=gccross? And gccross
pretends to be $build's native compiler, but calls the cross-compiler
and rewrites the -I / -L paths accordingly? Please correct me if
anything is wrong.

My understanding is that gccross is a good short-term solution, and in
the long-term all packages should be cross-build aware and use the right
tools themselves. In fact, my package is configured with
--host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE), so make
should already call the right compiler with the right paths.

So, with my current understanding, I think even further, there should be
a mechanism (an option, environment variable, whatever) to *enable*
using gccross. It should be disabled by default since compliant packages
don't need it.

What do you think?

With kind regards,

Reply to: