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

Bug#708143: mips64(el) and mipsn32(el) support with multilib



On Wed, Aug 28, 2013 at 11:54 PM, Matthias Klose <doko@debian.org> wrote:
> Am 21.08.2013 20:55, schrieb YunQiang Su:
>> This new one won't define TARGET for control.m4 when
>> with_deps_on_target_arch_pkgs=yes is used.
>
> why? TARGET is used in conditionals in the control.m4, so it has to be defined
> for every cross build. Am I missing something?
It will have no Multi-Arch tag when with TARGET defined.
>
> the patch for debian/rules.defs is unrelated, and already there.
>
> checked in the remaining chunks.
>
>> With this patch,
>> 1. echo "mips64el" > debian/target
>>    with_deps_on_target_arch_pkgs=yes DH_VERBOSE=1 \
>>    WITH_SYSROOT=/ BACKPORT=false PKG_IGNORE_CURRENTLY_BUILDING=1 \
>>    DEB_BUILD_OPTIONS=nostrip BACKPORT=false dpkg-buildpackage -b -uc -us -d -nc
>> successfully build with
>> {gcc,cpp,g++...}-4.8-mips64el-linux-gnuabi64-4.8.1-10*_amd64.deb
>> and lib*_mips64el.deb out.
>>
>> 2. dpkg-buildpackage -B successfully build for native amd64 build.
>>
>> 3. dpkg-buildpackage failed to build with an error
>>     dh_installdeb -pgcj-4.8-source
>> dh_md5sums -pgcj-4.8-source
>> dh_builddeb -pgcj-4.8-source
>> dpkg-deb: building package `gcj-4.8-source' in
>> `../gcj-4.8-source_4.8.1-10_all.deb'.
>> touch stamps/08-binary-stamp-libgcjsrc
>> mkdir -p /tmp/buildd/gcc-4.8-svn/gcc-4.8-4.8.1/build/java-src
>> cd /tmp/buildd/gcc-4.8-svn/gcc-4.8-4.8.1/build/java-src && fastjar -xf
>> /tmp/buildd/gcc-4.8-svn/gcc-4.8-4.8.1/build/x86_64-linux-gnu/libjava/src.zip
>> Error! CRCs do not match! Got 264aca47, expected 95962ba4
>> make[1]: *** [stamps/05-build-javadoc-stamp] Error 1
>
> is this reproducible?  I did see this in a archive test rebuild too, done by Lucas.
>
Yes, it reproducible.
I create a new chroot environment on tmpfs, and chroot into it by pbuilder.
Is is related with tmpfs or pbuilder?
I did meet some failures when sbuild successful while pbuilder failed.

-- 
YunQiang Su


Reply to: