Bug#768876: unblock: busybox/1:1.22.0-14

[Michael Tokarev <mjt@tls.msk.ru>]

28.11.2014 15:11, Thorsten Glaser wrote:
> On Thu, 27 Nov 2014, Michael Tokarev wrote:
> 
>> (The Built-Using field generation is a bit fun here: I asked on IRC
>> how people identify which libc is in use, and got various somewhat-
>> incpmplete replies (the prob is that on different arches, libc package
>> is named differently).  So I invented my own way for busybox, because
> 
> You didn’t ask in the #!/bin/mksh channel on IRC (= Freenode) ;-)

I asked in several debian-related places, since this is a debian-specific
thing.

> So let me add mine:
> 
> ‣ intimate knowledge of the build system required, so you know
>   what precidely is pulled in (reading shlibs:Depends from the
>   build of the shared version is almost certainly wrong)

Why it is wrong?  To be this looks like the most accurate approach
really.

> In the mksh case, I have a switch between different libcs to use.
> For dietlibc and klibc, the cases are clear:

Wug.

[]
> In *all* cases, you also need
> 
> • x=$(dpkg -S "$(readlink -f "$($CC -print-file-name=libgcc.a)")")
>   libgcc_pkgname=${x%%: *}

Why?  This assumes it is gcc an it uses libgcc, so it wont work with,
say, clang.  Note also that if libgcc is used by shared build, it will
also be listed in shilbdeps.

Thanks,

/mjt