On 6 April 2015 at 19:03, Tianon Gravi <admwig...@gmail.com> wrote: > On 3 April 2015 at 17:16, Felipe Sateler <fsate...@debian.org> wrote: >> Hi, please find attached a patch implementing this, stealing from the >> patch at [1] implementing same thing for gdb-avr. > > Neat, thanks! It's not as cool as I was hoping for (something that > detects use of libc and adds appropriate Built-Using generically based > on that), but it'll do just fine, and solves the problem.
Yes, there should probably be a helper to do this. > >> I have used libc-dev-bin because libc-dev is a virtual package, >> libcN-dev has a different N in different architectures. > > Yeah, that's fair. :) > > Another option that might be worth trying (for a little more > defensibility) is something with "dpkg -S", ala "dpkg -S > /usr/lib/x86_64-linux-gnu/libc.a", but this is much definitely better > than not having anything at all. Unfortunately, dpkg -S is slow, so I'm not sure it is the best option. A better one might be to somehow tell gcc to print the library it is using when told -lc. > > I've applied the change in Git, and plan to get a release of 1.6.0~rc4 > including it in experimental ASAP. :) -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
