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

Bug#720363: gcc-4.8: i386 on armhf cross-compiler FTBFS



On Wed, Aug 21, 2013 at 5:20 AM, Matthias Klose <doko@debian.org> wrote:
> building a i386 on armhf cross-compiler (according to https://wiki.debian.org/MultiarchCrossToolchainBuild)
> builds, but then fails on dh_strip:
>
> dh_strip -plibgcc1 --dbg-package=libgcc1-dbg
> objcopy: Unable to recognise the format of the input file `debian/libgcc1/lib/i386-linux-gnu/libgcc_s.so.1'
> dh_strip: objcopy --only-keep-debug debian/libgcc1/lib/i386-linux-gnu/libgcc_s.so.1 debian/libgcc1-dbg/usr/lib/debug//lib/i386-linux-gnu/libgcc_s.so.1 returned exit code 1
>
>
> If i replace the objcopy command above with i486-linux-gnu-objcopy (which is installed, and was built
> from binutils source according to the same instructions), then then command runs successfully.

does using binutils-multiarch help?

got same issue with amd64 on armhf
dh_strip -plibgcc1 --dbg-package=libgcc1-dbg
objcopy:debian/libgcc1/lib/x86_64-linux-gnu/libgcc_s.so.1: File format not recognized
dh_strip: objcopy --only-keep-debug debian/libgcc1/lib/x86_64-linux-gnu/libgcc_s.so.1 debian/libgcc1-dbg/usr/lib/debug//lib/x86_64-linux-gnu/libgcc_s.so.1 returned exit code 1
 
 but installing binutils-multiarch made it work 

The problem here is that debhelper isn't aware of the target architecture.  I
can export the DEB_TARGET_* macros to the environment, if debhelper can use
these. I don't intend working on these.

And I hope such a cross compiler remains an academic exercise ...

well i wanted to test cross-building, but i am on a armhf as my primary laptop....


--

---
Shawn Landden
+1 360 389 3001 (SMS preferred)

Reply to: