August 2009 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] -fPIC failing on RHEL5/CentOS5 builds?
by Scott Cantor 19 Aug '09

19 Aug '09

I've just started attempting to use the build service for my project and got a report that one of the binaries contained a bunch of text relocations, indicating -fPIC wasn't used during the build. After some cross checking, I found that the usual checks in configure were being done, but that on two of the build platforms (RH5/CentOS5), the gcc/g++ checks were failing and it was omitting the flag. Both architectures were affected. I tested locally with CentOS 5 and confirmed that I get different (correct) results from my rpmbuild. I know there's no direct access to config.log, so it's a bit difficult to determine why this might be, but wondered if anybody had a clue or has seen this behavior in their projects? For reference the checks I'm referring to are: checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... no checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... no I saw nothing unexpected in my local config.log where the check passes, it's a typical gcc/g++ command. -- Scott -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] Re: [Mono-list] MonoOSC Help wanted :-)
by Petit Eric 18 Aug '09

18 Aug '09

2009/8/18 Oisín Grehan <oising(a)gmail.com>: > Is that OSC as in Open Sound Control? sorry, i don't understand your question, you mean : MonoOSC is Open source ? > > On Tue, Aug 18, 2009 at 6:47 AM, Petit Eric <surfzoid(a)gmail.com> wrote: >> >> Hi >> An user ask to an "quickstart guide", is there an MonoOSC user who >> want to write it ? >> >> https://sourceforge.net/tracker/index.php?func=detail&aid=2839338&group_id=… >> >> Unlucky, i really haven't got time and don't practice doc. >> >> -- >> Cordially. >> >> Small Eric Quotations of the days: >> >> --------------------------------------------------------------------------- >> I have no special talents. I am only passionately curious >> _______________________________________________ >> Mono-list maillist - Mono-list(a)lists.ximian.com >> http://lists.ximian.com/mailman/listinfo/mono-list > > > > -- > > --- > 404 signature missing > -- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] package publishing issues
by Cristian Rodríguez 18 Aug '09

18 Aug '09

Hi: The server:php and server:php:extensions repositories are taking a significant amount of time that varies between 3 days to weeks to get already built packages published to the download server, I was wondering how exactly the obs chooses what to publish and when, and if that is configurable .. let's say: I have target A in server:php and target B in server:php:extensions, B uses A for build and hence depends on it, If A rebuilds I want to have A and B published at the same time to avoid inconsistencies, is that possible ? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] MonoOSC Help wanted :-)
by Petit Eric 18 Aug '09

18 Aug '09

Hi An user ask to an "quickstart guide", is there an MonoOSC user who want to write it ? https://sourceforge.net/tracker/index.php?func=detail&aid=2839338&group_id=… Unlucky, i really haven't got time and don't practice doc. -- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] Unowned directories question
by doiggl＠velocitynet.com.au 18 Aug '09

18 Aug '09

Hello To get past this Warning message I have gotten a workaround for it. (see workaround below) Warning message: bugzilla-3.4.1-14.1.noarch.rpm: directories not owned by a package: - /etc/httpd - /etc/httpd/conf.d - /usr/share/bugzilla/extensions - /usr/share/bugzilla/lib bugzilla-doc-3.4.1-14.1.noarch.rpm: directories not owned by a package: - /usr/share/bugzilla/docs bugzilla-doc-build-3.4.1-14.1.noarch.rpm: directories not owned by a package: - /usr/share/bugzilla/docs System halted. #WORKAROUND #---------- %if 0%{?suse_version} # With unowned dirs /etc/httpd/, the build will fail so own them ourselves %dir %{_sysconfdir}/etc/httpd %dir %{_sysconfdir}/etc/httpd/conf.d %dir %{_sysconfdir}/etc/httpd/conf.d/bugzilla.conf %endif Questions: Does the workaround look ok ?, and at what line should I place the code in the .specfile ? Specfile -> https://build.opensuse.org/package/view_file?file=bugzilla.spec&package=Bug… Thanks for the advice Glenn -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 4

[opensuse-buildservice] Is this a bug in osc?
by Dave Plater 17 Aug '09

17 Aug '09

I removed a package from my build service project and home directory ( a .desktop file) and then found that it was necessary so I put it back in my local project directory. Then I performed an osc ci and it checked in three files that I had changed but failed to include the above mentioned package is this normal and I should manually upload new files or is this a bug? Regards Dave P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] BUG: self-dependency in build problem on OBS
by David Greaves 17 Aug '09

17 Aug '09

If I want to build a deb package that depends on itself for building then it fails. I assumed it was being removed by build or osc but traced it to the API response. eg: https://api.opensuse.org/build/home:lbt:arm:cross/xUbuntu_9.04/armv5el/m4/_… https://api.opensuse.org/build/home:lbt:arm:cross/xUbuntu_9.04/armv5el/dpkg… Both m4 and dpkg-dev are build-essential The first (m4) package does not have m4 in the <bdep> list but has dpkg-dev The second (dpkg) package does not have dpkg-dev in the <bdep> list but has m4 (dpkg provides dpkg-dev of course) This bites when building any package in build-essential or any other package that self build-depends; they all need modifying to build on OBS. David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] bs and ARM
by Peter Czanik 17 Aug '09

17 Aug '09

Hello, Finally I got a little time, so I'd like to try to compile a few packages for Debian ARM. Last time I worked with the BS, I used PPC and openSUSE 11.0. Now looking for info, how to get started BS for ARM. So, I got some questions: - which version to use if I want to compile for ARM? - http://en.opensuse.org/Build_Service/Build_Service_Installation_Tutorial only has instructions up to openSUSE 11.0. Does the same apply for 11.1? Is it the doc I should use for cross builds: http://en.opensuse.org/Build_Service/Concepts/CrossDevelopment ? - Can I compile for Debian Lenny? ( http://en.opensuse.org/Build_Service/Concepts/CrossDevelopment only mentions Etch ) Some packages are not included in Debian Lenny for ARM, which are available in Ubuntu and I'd try to recompile them for Debian... - is it already possible to boot openSUSE/ARM? Would be nice to see it running at least in Qemu... Bye, CzP -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 7

[opensuse-buildservice] RPM signing problem
by Cristian Morales Vega 16 Aug '09

16 Aug '09

For some days I have been receiving emails about failed builds. Now I'm looking into them and seems to be a problem signing packages in Factory: sign libglpng-devel-1.45-1.41.i586.rpm failed: 256 Any idea? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] [osc] patch to support overlay filesystem - RFC
by Jan-Simon Möller 14 Aug '09

14 Aug '09

Hi ! During work on openSUSE@ARM I frequently wanted to change single files or add single files to the buildroot without recompiling a dependency package or adding the files to a dummy rpm. Thus here are 2 patches for osc and build which will do this: Take all files in the specified "overlay"-folder and copy them to the buildroot before actually starting the build. This can help especially in local development with osc build if you e.g. want to delpoy a custom debugger, a custom qemu-arm or even a patched file. Best, Jan-Simon Signed-off-by: Jan-Simon Möller <jansimon.moeller(a)opensuse.org> Index: build.py =================================================================== --- build.py (Revision 7845) +++ build.py (Arbeitskopie) @@ -511,6 +511,23 @@ vm_options, build_descr, buildargs) + # special handling for overlay + if opts.overlay: + myoverlay=os.path.abspath(opts.overlay) + if os.path.isdir(myoverlay): + cmd = '%s --root=%s --rpmlist=%s --dist=%s --overlay=%s --arch=%s %s %s %s' \ + % (config['build-cmd'], + config['build-root'], + rpmlist_file.name, + bc_file.name, + myoverlay, + bi.buildarch, + vm_options, + build_descr, + buildargs) + else: + print "ERROR: OVERLAY ("+myoverlay+") is no directory." + sys.exit(1) if config['su-wrapper'].startswith('su '): tmpl = '%s \'%s\'' Index: commandline.py =================================================================== --- commandline.py (Revision 7845) +++ commandline.py (Arbeitskopie) @@ -2238,6 +2238,8 @@ @cmdln.option('--clean', action='store_true', help='Delete old build root before initializing it') + @cmdln.option('--overlay', metavar='OVERLAY', + help='Copy overlay filesystem to buildroot after installing all RPMs. This must be a valid directory (e.g. /tmp/overlay-root). The files are copied as-is.') @cmdln.option('--no-changelog', action='store_true', help='don\'t update the package changelog from a changes file') @cmdln.option('--noinit', '--no-init', action='store_true', Index: build =================================================================== --- build (Revision 7845) +++ build (Arbeitskopie) @@ -63,6 +63,7 @@ INCARNATION= DISTURL= CHANGETARGET= +OVERLAY= export PATH=$BUILD_DIR:/sbin:/usr/sbin:$PATH @@ -157,6 +158,9 @@ --icecream N use N parallel build jobs with icecream + --overlay OVERLAY + Copy overlay filesystem to buildroot after installing + all RPMs. This must be a valid directory. --debug enable creation of a debuginfo package @@ -664,6 +668,10 @@ *-changelog) CHANGELOG=true ;; + --overlay) + OVERLAY=$ARG + shift + ;; -*) echo Unknown Option "$PARAM". Exit. cleanup_and_exit 1 @@ -1332,6 +1340,17 @@ BUILD_SUCCEEDED=false + if test -n "$OVERLAY" ; then + if test -d "$OVERLAY"; then + pushd $OVERLAY + echo "Copying overlay to BUILD_ROOT" + tar -cpf - . | (cd $BUILD_ROOT ; tar -xf -) + popd + else + echo "OVERLAY ($OVERLAY) is no directory - skipping" + fi + fi + if test "$BUILDTYPE" = spec ; then test -z "$BUILD_RPM_BUILD_STAGE" && BUILD_RPM_BUILD_STAGE=-ba -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 13