[opensuse-buildservice] Ports:ARM:11.2
Hello, Ports:ARM:11.2 has some failing packages: https://build.opensuse.org/project/monitor?arch_armv5el=1&defaults=0&failed=1&project=Ports%3AARM%3A11.2&repo_crosscompiled=1 I could probably fix some of the packages. How should I do that (once "osc co" works again...)? I definitely need somebody to review my changes, as they will make the packages compile, but without actually knowing the packages, they won't always do the right stuff :-) Bye, CzP -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Donnerstag, 11. Februar 2010 21:11:39 schrieb Peter Czanik:
Hello, Ports:ARM:11.2 has some failing packages: https://build.opensuse.org/project/monitor?arch_armv5el=1&defaults=0&failed =1&project=Ports%3AARM%3A11.2&repo_crosscompiled=1 I could probably fix some of the packages. How should I do that (once "osc co" works again...)? I definitely need somebody to review my changes, as they will make the packages compile, but without actually knowing the packages, they won't always do the right stuff :-) Bye, CzP
osc branch osc sr ;) Best, Jan-Simon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
2010-02-11 23:32 keltezéssel, Jan-Simon Möller írta:
Am Donnerstag, 11. Februar 2010 21:11:39 schrieb Peter Czanik:
Hello, Ports:ARM:11.2 has some failing packages: https://build.opensuse.org/project/monitor?arch_armv5el=1&defaults=0&failed =1&project=Ports%3AARM%3A11.2&repo_crosscompiled=1 I could probably fix some of the packages. How should I do that (once "osc co" works again...)? I definitely need somebody to review my changes, as they will make the packages compile, but without actually knowing the packages, they won't always do the right stuff :-) Bye, CzP
osc branch osc sr
OK. How do I make an "osc sr" if the fixed package is: python-base in project home:czanik:branches:Ports:ARM:11.2 ? Here all I did is removing three lines from the python-base.spec file (an IFDEF), as bz2.so is now actually built also on ARM :-) Bye, CzP -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello, 2010-02-11 21:11 keltezéssel, Peter Czanik írta:
Hello, Ports:ARM:11.2 has some failing packages: https://build.opensuse.org/project/monitor?arch_armv5el=1&defaults=0&failed=1&project=Ports%3AARM%3A11.2&repo_crosscompiled=1
What is the proper way of fixing perl packages? If I add the following lines to the perl-Text-Reform.spec spec file, it compiles fine on armv5tel, but fails badly on armv7l :-( %ifarch %arm %dir %{perl_vendorlib}/armv5tel-linux-thread-multi/auto/Text %dir %{perl_vendorlib}/armv5tel-linux-thread-multi/auto/Text/Reform %{perl_vendorlib}/armv5tel-linux-thread-multi/auto/Text/Reform/.packlist %endif Bye, CzP -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Freitag 12 Februar 2010 11:20:24 schrieb Peter Czanik:
Hello,
2010-02-11 21:11 keltezéssel, Peter Czanik írta:
Hello, Ports:ARM:11.2 has some failing packages: https://build.opensuse.org/project/monitor?arch_armv5el=1&defaults=0&failed=1&project=Ports%3AARM%3A11.2&repo_crosscompiled=1
What is the proper way of fixing perl packages? If I add the following lines to the perl-Text-Reform.spec spec file, it compiles fine on armv5tel, but fails badly on armv7l :-(
%ifarch %arm %dir %{perl_vendorlib}/armv5tel-linux-thread-multi/auto/Text %dir %{perl_vendorlib}/armv5tel-linux-thread-multi/auto/Text/Reform %{perl_vendorlib}/armv5tel-linux-thread-multi/auto/Text/Reform/.packlist %endif
There's rpm macro stuff for the "<arch>-linux-thread-multi" which might need a fix. Then it will work by itself. Best, Jan-Simon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
2010-02-11 21:11 keltezéssel, Peter Czanik írta:
Hello, Ports:ARM:11.2 has some failing packages: https://build.opensuse.org/project/monitor?arch_armv5el=1&defaults=0&failed=1&project=Ports%3AARM%3A11.2&repo_crosscompiled=1
This seems to be a qemu problem in the test phase of libsigc++2: [...] |f(int 1) terminate called after throwing an instance of 'std::range_error' what(): out of range qemu: uncaught target signal 6 (Aborted) - core dumped /bin/sh: line 4: 6560 Aborted ${dir}$tst FAIL: test_exception_catch| [...] Would it be an option to turn off testing temporarily on ARM? Bye, CzP -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
2010-02-12 11:43 keltezéssel, Peter Czanik írta:
2010-02-11 21:11 keltezéssel, Peter Czanik írta:
Hello, Ports:ARM:11.2 has some failing packages: https://build.opensuse.org/project/monitor?arch_armv5el=1&defaults=0&failed=1&project=Ports%3AARM%3A11.2&repo_crosscompiled=1
This seems to be a qemu problem in the test phase of libsigc++2:
[...] |f(int 1) terminate called after throwing an instance of 'std::range_error' what(): out of range qemu: uncaught target signal 6 (Aborted) - core dumped /bin/sh: line 4: 6560 Aborted ${dir}$tst FAIL: test_exception_catch| [...]
Would it be an option to turn off testing temporarily on ARM?
Checked, and with this "%ifnarch %arm" around "%check", the package is built... %ifnarch %arm %check export MALLOC_CHECK_=2 MALLOC_PERTURB_=$((${RANDOM:-256} % 256)) %{__make} check unset MALLOC_CHECK_ MALLOC_PERTURB_ %endif Bye, CzP -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello, 2010-02-12 11:56 keltezéssel, Peter Czanik írta:
Checked, and with this "%ifnarch %arm" around "%check", the package is built...
%ifnarch %arm %check export MALLOC_CHECK_=2 MALLOC_PERTURB_=$((${RANDOM:-256} % 256)) %{__make} check unset MALLOC_CHECK_ MALLOC_PERTURB_ %endif
The same is true for package "gc", everything is compiled, but qemu crashes in the test phase. Moving check to ifnarch arm lets the package to build. Another qemu problem suspect is bsdtar, also in the testin phase: "|Unsupported ioctl: cmd=0xffffffff80046601 lt-bsdtar: Couldn't list extended attributes: Operation not supported|" Should I add the "ifnarch arm" around "check" and "osc sr" them, or you rather fix qemu? :-) I checked all of the failing packages. The rest seem to need some C expertise to get fixed, so outside of my (current) capabilities... Bye, CzP -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Jan-Simon Möller
-
Peter Czanik