On Wed, 05 Dec 2007, Neil Williams wrote:
> Raphael Hertzog wrote:
> > On Tue, 04 Dec 2007, Neil Williams wrote:
> >> On Wed, 5 Dec 2007 00:01:22 +0100
> >> Raphael Hertzog <[EMAIL PROTECTED]> wrote:
> >>
> >>> On Tue, 04 Dec 2007, Neil Williams wrote:
> >>>> +my @shlibdeps=();
> >>>> +# ARCH for some awkward builds
> >>>> +my $crossprefix = Dpkg::Arch::debarch_to_gnutriplet($ENV{ARCH}) if
> >>>> ($ENV{ARCH});
> >>> What's the role of $ARCH ? And why shall we consider that we're
> >>> crossbuilding only because this variable is set ?
> >> Not cross building - building a cross compiler.
> >
> > Do we need to check twice for building a cross-compiler ? We don't need to
> > check $ARCH if we already have DEB_TARGET_GNU_TYPE != DEB_BUILD_GNU_TYPE,
> > no ?
>
> My first patch did exactly that - and failed on building a cross
> compiler. gcc needs dpkg-shlibdeps to take notice of $ARCH in the
> preparation of libgcc1-$arch-cross and other libraries used in the
> complete toolchain. It needs (and sets) DEB_TARGET_GNU_TYPE !=
> DEB_BUILD_GNU_TYPE at other stages of the build.
If that's the case, I'd like to know if this is deliberate and really
required... can't the gcc package be consistent and always have both
DEB_TARGET_GNU_TYPE and DEB_BUILD_GNU_TYPE properly set ?
(Ccing [EMAIL PROTECTED] to have their opinion)
Cheers,
--
Raphaël Hertzog
Le best-seller français mis à jour pour Debian Etch :
http://www.ouaza.com/livre/admin-debian/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
