October 2009 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] dep for suse-release broken ?
by Christian 18 Oct '09

18 Oct '09

Hi, I tried to define dep for suse-release. It is working for any {suse_version} but SLE_10. I did not get it work. I looked into sles-release-10 spec file Provides: distribution-release Provides: %{name}-10 %{name}-10-sp1 %{name}-10-sp2 and tested them all without success. %if 0%{?sles_version} == 10 BuildRequires: distribution-release %endif buildinfo is broken... it says: expansion error: nothing provides distribution-release Is this worth for a bug ? Regards Chris -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

Re: [opensuse-packaging] Skrooge: No %description skrooge-lang
by Dominique Leuenberger 17 Oct '09

17 Oct '09

Hi Sascha, >>> "Sascha 'saigkill' Manns" <samannsml(a)directbox.com> 10/17/09 8:48 PM >>> >Hi Mates, > >does anyone know why the Spec not respect my %description? Yes :) > http://pastebin.ca/1625585 (Specfile) A syntax error in this line (87) Obsoletes: %{name}-lang < %{version]-%{release} the version tag is not closed, as such %description is not getting defined at any point in the spec file. Hope this helps. Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 2

[opensuse-packaging] osc rq decline 22540 ...
by Boyd Lynn Gerber 17 Oct '09

17 Oct '09

When I looked at it, there were not any builds scheduled. I just looked again an now a couple builds have succedded. I think this rq should be re-submmited once everything has built. Not before. I wanted to make sure it was clear that at the time I reviewed the rq it did not have any builds even scheduled. That is why I rejected it. Maybe in a day or so all the build will have had a chance to build. I think there should be a policy that the project the rq is being done agains at least pass the builds on the OBS. Thanks, -- Boyd Gerber <gerberb(a)zenez.com> 801 849-0213 ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Re: --as-needed and pthread
by Michael Matz 17 Oct '09

17 Oct '09

Hi, [including some random mailing list, so that the text isn't lost :) ] On Thu, 18 Jun 2009, Cristian Rodríguez wrote: > > there are some packages that fail to build because they miss phtread > > symbols. I have always have the doubt about why there is the > > "-pthread" gcc flag... somewhere I read that's the correct thing to > > do, that using -lpthread is wrong, but without explanations. What > > should I use in these cases? I suppose use -lpthread would be the > > equivalent to what they did without --as-needed... but perhaps the > > behavior without --as-needed was already wrong. > > matz is the right person to answer your question, as far as I know, the > right way is using -lpthread instead of -pthread , is that correct ? Nope, -pthread is better than -lpthread (see below). It's completely possible that something is broken with as-needed vs. pthreads. Those cases have to be identified and then worked around (export SUSE_AS_NEEDED=0), or better, analyzed for the root cause. I didn't get the complete thread, only this forward, so I don't know what the nature of the breakage is, so I can give only speculations: I would think that if something with pthread and as-needed breaks it doesn't get exposed as missing symbols or the like (so that apps don't even start) but rather mysterious breakages related to non-thread-aware functions being used even though -pthread was given as compile and link flag. [background] Regarding the explanation of -pthread/-lpthread: Unfortunately the initial threading support for UNIX was a bit like bolted onto the existing (non thread-aware) libc. For various reasons it was decided that users that aren't interested in threading are not supposed to pay the cost of _potential_ thread safety. This cost is mostly associated with locking some shared data structures for libc and the process output (e.g. output of printf() ). Now, given this criteria, there's not much choice. Basically the user has to announce to the system if or if not the application is thread aware, so that it (the system) can chose between thread-aware or non thread-aware functions. This announcement is done by the -pthread flag. The difference to the -lpthread flag is that it is not only a link time flag (saying that the libpthread library has to be put into the dependence libraries) but also a compile time flag. So for compiling .c to .o files for a thread aware program it's necessary to include -pthread into the compile flags. The effect of that option is system dependend. Usually it will result in the compiler defining some preprocessor symbols (_REENTRANT) so that system headers can choose between different implementations of various posix functions (where the API doesn't make a difference between thread-safe and -unsafe functions) and internal data structures. So, for memoizing the difference: -lpthread is a link time only flag, simply telling the linker to include libpthread into the application. -pthread (without the "l") is a link time _and compile time flag_. Because sometimes different code has to be emitted (for the runtime system including libc) for programs supposed to be thread-safe, this can't be announced only at the link phase, the compiler has to know about this. [more magic] Now, for linux there's a bit magic involved. To make the cost for non thread-safe programs really low some routines in libc _are not thread-safe_. That's fine, those programs aren't linked against libpthread, so they have announced to be not interested in threads. libpthread.so provides thread-aware variants of some functions that are also provided by libc itself. For instance open() and friends is such function. The libpthread variant includes some locking for shared data structures. (Apart from these overriding functions it also includes the usual pthread functions, pthread_*, e.g. pthread_spin_lock). How this all works is because ELF symbols resolution rules say so. If an application calls "open" and is linked against libpthread and libc (which both provide a version of "open", one thread-aware the other not) then the dynamic linker will chose the first it finds. Other things (gcc .spec files) make sure that libpthread is linked in _before_ libc when -pthread is given. This can't be ensured for -lpthread, the latter being simply a request for a random other library, as far as the system knows. So only -pthread, not -lpthread, makes really sure that libpthread is linked at the right place vs. libc, so that it can override the non thread-aware functions of it. [less magic] Having said all this, it usually is just fine to simply link against libpthread (via -lpthread) with linux, as long as you don't mention -lc before. This is because most headers don't care about the _REENTRANT preprocessor define, i.e. they don't change their content depending on the flag, and because ELF rules will still make the functions from libpthread be preferred. But for cross-platform compatibility it's important to use -pthread, _not_ -lpthread. And as it's important for others, and at least good under linux, you can just as well use it always if you need. Ciao, Michael.

5 15

[opensuse-packaging] Skrooge: No %description skrooge-lang
by Sascha 'saigkill' Manns 17 Oct '09

17 Oct '09

Hi Mates, does anyone know why the Spec not respect my %description? http://pastebin.ca/1625585 (Specfile) -- Sincerely yours Sascha Manns openSUSE Member openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://saigkill.wordpress.com ClaimID: http://claimid.com/saigkill -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] *.desktop run as user
by Sascha 'saigkill' Manns 17 Oct '09

17 Oct '09

Hello Mates, i have written an *.desktop Files, and i would like to run this as root. In the KMenu i can specify an User. But how can i add this in the File directly? I have searched there: http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s05.html But don't find the Key, Has anyone an Idea? -- Sincerely yours Sascha Manns openSUSE Member openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://saigkill.wordpress.com ClaimID: http://claimid.com/saigkill -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 2

[opensuse-packaging] Building KMP openSUSE 11.2 i586
by Matwey V. Kornilov 17 Oct '09

17 Oct '09

Hi, Adrian advised me to write here. I have the problem with building my KMP at i586 with Factory repository using OBS. Building for other platforms is successful. I checked building the rpm with opensuse 11.2 i586 livecd and It was successful. Full error message: + make -C /usr/src/linux-obj/i586/debug modules M=/usr/src/packages/BUILD/rs485-5.1.2/obj/debug/lpt/kernel LDDINC=/usr/src/packages/BUILD/rs485-5.1.2/obj/debug/lpt/include make: Entering directory `/usr/src/linux-2.6.31.3-1-obj/i386/debug' make -C ../../../linux-2.6.31.3-1 O=/usr/src/linux-2.6.31.3-1- obj/i386/debug/. modules CC [M] /usr/src/packages/BUILD/rs485-5.1.2/obj/debug/lpt/kernel/lpt.o CC [M] /usr/src/packages/BUILD/rs485-5.1.2/obj/debug/lpt/kernel/rs485_irq.o make[3]: execvp: /bin/sh: Argument list too long make[3]: *** [/usr/src/packages/BUILD/rs485-5.1.2/obj/debug/lpt/kernel/rs485_tools.o] Error 127 make[2]: *** [_module_/usr/src/packages/BUILD/rs485-5.1.2/obj/debug/lpt/kernel] Error 2 make[1]: *** [sub-make] Error 2 I am sure that my Makefiles are valid. The problem appears only with OBS Factory i586. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] openSUSE 11.2 setup in OBS
by Adrian Schröter 17 Oct '09

17 Oct '09

Hi, (and sorry for the cross post, please answer only on one ml with me in CC) The openSUSE Build Service is now building 11.2 in the openSUSE 11.2 project. openSUSE:Factory is de-prefered atm (building only, if really nothing else is there). The build-compare stuff is disabled for now (to ensure that all packages get the new tags and that all packages have chronical build times). We will enable it again after GA (when openSUSE:11.2 project is frozen). Happy Weekend. adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] skrooge 0.5.2
by Sascha 'saigkill' Manns 16 Oct '09

16 Oct '09

Hello Mates, while building skrooge i'm getting an Error. -> http://pastebin.ca/1623972 Anyone know how to fix it? -- Sincerely yours Sascha Manns openSUSE Member openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://saigkill.wordpress.com ClaimID: http://claimid.com/saigkill -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] 11.2 is done, long lives 11.2
by Stephan Kulow 16 Oct '09

16 Oct '09

Hi, As you may have heard, 11.2 RC1 was released. This means, development of it has ended, from now on we will only fix bugs that we would have fixed as maintenance update too. So everything you submit to openSUSE:Factory will not automatically go into 11.2, but I will hand pick. As this has to be done with care, factory checkins will be very slow the the next weeks. And openSUSE:Factory will get a lower priority than 11.2, but if you build against the snapshot this shouldn't be a problem for you. But again: for now you submit your fixes to openSUSE:Factory and just make sure your changelog makes clear it's a bug fix and we look up the bug report to decide if we want to take the risk and for those I do not feel worth it, will end up in openSUSE:Factory only. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1