[opensuse-packaging] glibc-devel-static coming to Factory
I'm submitting now to Base:System a glibc with a glibc-devel-static subpackage, so for static linking you need to add to your spec files: BuildRequire: glibc-devel-static this was suggested at bnc#655261. if you see serious problems, please speak up, Andreas -- Andreas Jaeger, Program Manager openSUSE aj@{novell.com,suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Thursday 16 June 2011 15:20:29 Andreas Jaeger wrote:
I'm submitting now to Base:System a glibc with a glibc-devel-static subpackage, so for static linking you need to add to your spec files:
BuildRequire: glibc-devel-static
this was suggested at bnc#655261. if you see serious problems, please speak up,
Andreas awesome, thanks! -- Mit freundlichen Grüßen, Sascha Peilicke http://saschpe.wordpress.com
El 16/06/11 09:20, Andreas Jaeger escribió:
I'm submitting now to Base:System a glibc with a glibc-devel-static subpackage, so for static linking you need to add to your spec files:
BuildRequire: glibc-devel-static
this was suggested at bnc#655261. if you see serious problems, please speak up,
Andreas
If something fails to compile, please open a bug report and CC to me, I will check if the complains are valid or not ;-) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
El 16/06/11 09:20, Andreas Jaeger escribió:
I'm submitting now to Base:System a glibc with a glibc-devel-static subpackage, so for static linking you need to add to your spec files:
BuildRequire: glibc-devel-static
this was suggested at bnc#655261. if you see serious problems, please speak up,
Andreas
There is also libstdc++<version>-devel that contains /usr/lib64/gcc/x86_64-suse-linux/4.5/libstdc++.a which might get splitted off a different package -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Thu, 16 Jun 2011, Cristian Rodríguez wrote:
El 16/06/11 09:20, Andreas Jaeger escribió:
I'm submitting now to Base:System a glibc with a glibc-devel-static subpackage, so for static linking you need to add to your spec files:
BuildRequire: glibc-devel-static
this was suggested at bnc#655261. if you see serious problems, please speak up,
Andreas
There is also libstdc++<version>-devel that contains /usr/lib64/gcc/x86_64-suse-linux/4.5/libstdc++.a which might get splitted off a different package
No, then -static-libstdc++ doesn't work anymore. Seriously, who
cares about the size of -devel packages??
Richard.
--
Richard Guenther
Hi, On Fri, 17 Jun 2011, Richard Guenther wrote:
There is also libstdc++<version>-devel that contains /usr/lib64/gcc/x86_64-suse-linux/4.5/libstdc++.a which might get splitted off a different package
No, then -static-libstdc++ doesn't work anymore. Seriously, who cares about the size of -devel packages??
In this context the wish for explicitely having a package containing the static library is to know which packages link against libc statically and hence which ones to recompile should there be a security update for libc. I don't fully buy this way of thinking, and for libstdc++ it doesn't make much sense, as much code will always be statically in the application (all the template expansions). Ciao, Michael. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (5)
-
Andreas Jaeger -
Cristian Rodríguez -
Michael Matz -
Richard Guenther -
Sascha Peilicke