Re: glibc-devel vs. glibc-devel{,-static}

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

 



On Wednesday 18 February 2009 21:14:57 Kevin Kofler wrote:

> In principle, libc_nonshared.a etc. all fall under the "what if only a
> static library is provided" policy, so if the guideline was enforced for
> glibc, every single package containing compiled code would need to BR
> glibc-static (or rather glibc-nonshared-static or something like that to
> distinguish it from a true glibc-static subpackage which should be what
> ships libc.a) because it links libc_nonshared.a.

Surely either the compiler, or binutils, would need to have that as a Requires: 
rather than every package that's built with gcc (especially since it's not the 
program itself that *has* that requirement, it's the toolchain).

>         Kevin Kofler


-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux