On Sunday 2013-01-13 20:30, Linda Walsh wrote:
All programs in openSUSE version xyz use the features of the particular glibc that is shipped in openSUSE xyz.
I find that hard to believe. I would believe that some use new features, but sometimes, the difference between versions are bug fixes. I can't believe that all programs relied on the bug fix and would fail without it.
Yeah I was imprecise there. But consider this:
#include
Just to be clear. I realize that there is no guarantee taking a program from V.[v+n] and having it run on a V.v system, however, it was possible to ***try*** this in suse versions prior to 12.0 -- USUALLY with success if prereqs were met.
That was just luck. It all depends on when a symbol was last modified. Some are as old as fopen@GLIBC_2.2.5. Prior to glibc 2.12~2.14 [openSUSE 12.0 and earlier], glibc was considered a slower-moving target. https://lwn.net/Articles/488778/ https://lwn.net/Articles/492624/
So question -- if I build a binary on OBS -- can I specify what OS it is being built for? Or is it always going to build for factory?
Yes, <repository name="openSUSE_12.2"> <path project="openSUSE:12.2" repository="standard"/> <arch>x86_64</arch> <arch>i586</arch> </repository>
I.e. if I take the source rpm for "12.2/3 can I tell OBS to build it in a 12.1 environment?
Yes.
Example -- perl5.16 doesn't seem to build on 12.1.
Works for me. osc co devel:languags:perl/perl cd there osc build -bd openSUSE_12.2 x86_64 <success after a while> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org