[Bug 1118626] Re: binutils: Split out libiberty-dev to multiarch paths

Wookey wookey at wookware.org
Thu Feb 7 23:14:39 UTC 2013


But it isn't a separate source - it's all built together from the
binutils source. What's the point of having another copy of binutils
upstream source to make libiberty-dev out of?

And I/we have no control over which libraries upstreams use.  There are
40 source packages that build-dep on binutils-dev. I don't know if all
of those are using libiberty or something else in binutils-dev (about 10
are kernels so those all will be). We can start telling people to use
gnulib if that is equivalent, but in the meantime people need to cross-
build kernels, so some solution is needed, and it is likely to take a
long time to get them all to change unless it's something mechanical we
can fix in the distro.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1118626

Title:
  binutils: Split out libiberty-dev to multiarch paths

Status in Ubuntu:
  New

Bug description:
  The kernel build-depends on binutils-dev for builds, (because
  libiberty is used for perf in the linux-tools package). This prevents
  automated kernel cross-building because binutils-dev is not Multi-
  Arch: same, and cannot be easily made so due to its dependency on
  binutils. So apt-get --only-source build-dep -a linux fails

  The maintainer's suggested fix is to split out the libiberty static
  library into an M-A: same package, which the kernel can then build-
  depend on.

  The attached patch implements this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1118626/+subscriptions



More information about the Ubuntu-sponsors mailing list