Re: Bug#453267: tested patch
On Sun, 09 Dec 2007, Neil Williams wrote:
> Emdebian cannot build, patch or test every permutation of toolchain that
> people need so this isn't about "us" patching locally, it is about
> lowering the barrier to cross building on Debian by not forcing every
> user to patch locally. This is why we are at the current impasse - too
> many permutations.
Emdebian provides ready to use cross compiler. You can also provides
ready-to-use source packages for building other cross-compilers that are
not yet provided.
> Why propose changing every version of gcc (a process that could take
> extreme amounts of time to test, implement and get into testing) and
> then make it impossible to build cross compilers in Etch? Are we looking
> at backports as well?? Who is going to do all that work? (Not me, before
> anyone asks.)
ARCH is a very generic environment variable that might be set for some
other reasons (I use it for example in debian-cd) and I don't like to
change the behaviour of dpkg-shlibdeps just because it's set. IMO,
there should be a single check to activate cross-building support
and gcc's crossbuild should provide the right variables. I'm ok with a
supplementary specific check for building of a cross-compiler, but not
with a generic check like testing the ARCH environment variable.
Furthermore, all the cross-building support in gcc has been contributed
by various Emdebian people (according to doko), so it looks like Emdebian
is also able to fix gcc in that regard if needed.
> Now that we finally have a chance to fix dpkg-shlibdeps, why must all
> the previous work be undone? For the sake of one environment variable?
Please stop dramatizing the situation, we're not undoing your work. We're
adding proper support for cross-building by trying to do the right thing
instead of integrating crude hacks to match other crude hacks on the gcc
side.
Until you convince me that there's a good reason on the gcc side to not
have a consistent set of variables set, my opinion won't change just
because you repeat the same non-arguments.
> them - changing every gcc package is simply not workable IMHO and the
You make it sound like it would require horribly complicated patches on
the gcc side but we're speaking of setting a few environment variables
only. IMO it's perfectly workable.
Cheers,
--
Raphaël Hertzog
Le best-seller français mis à jour pour Debian Etch :
http://www.ouaza.com/livre/admin-debian/
Reply to: