** Tags added: multiarch-followup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/726428
Title:
Enabling of all possible targets broke ARM cross toolchain
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
This bug was fixed in the package binutils - 2.21.0.20110216-1ubuntu3
---
binutils (2.21.0.20110216-1ubuntu3) natty; urgency=low
* Read multiarch targets from the first column of /usr/share/dpkg/archtable;
it's not the ideal list, but it's better than a hardcoded list and
en
** Changed in: binutils (Ubuntu)
Importance: Undecided => Medium
** Changed in: binutils (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/726428
Title:
En
** Changed in: binutils (Ubuntu)
Assignee: (unassigned) => Loïc Minier (lool)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/726428
Title:
Enabling of all possible targets broke ARM cross toolch
18:17 < hrw> slangasek: dh_strip checks for
DEB_BUILD_GNU_TYPE/DEB_HOST_GNU_TYPE when it tries to find cross tools and it
is ok. but for cross-gcc it is only partially good as we generate both host
binaries (dh-strip is fine) and cross ones (dh-strip fails)
18:17 < slangasek> hrw: right
18:18 <
Thanks for the report
I think it's inconvenient that objcopy has this behavior, and it does
probably make sense to change it to not list all ARM architectures.
That said, it seems like the above build calls dh_strip on an armel-
cross architecture all package, which is not too common, and also cal
