Mailinglist Archive: opensuse-packaging (250 mails)
| < Previous | Next > |
Re: [opensuse-packaging] Bootstrap broken, cyclic dependencies in factory
- From: "Jan-Simon Möller" <dl9pf@xxxxxx>
- Date: Thu, 13 Aug 2009 10:39:13 +0200
- Message-id: <200908131039.13710.dl9pf@xxxxxx>
Am Thursday 13 August 2009 10:10:42 schrieb Richard Guenther:
Atm I can't bootstrap the packages in 2) (without nasty tricks), so lets try
that if its not too much hassle.
Regarding gcc4.4.1, i've 2 small issues left:
--- gcc44.spec.orig
+++ gcc44.spec
@@ -2221,6 +2242,7 @@ cat cpplib%{binsuffix}.lang gcc%{binsuff
%endif
%ifarch %arm
%{libsubdir}/include/mmintrin.h
+%{libsubdir}/include/arm_neon.h
%endif
%ifarch %ix86 x86_64
%{libsubdir}/include/cross-stdarg.h
And: bootstrapping gcc on ARM still requires s/-O/-O2/ in bootstrap-lean.
Should I submit a request with these 2 ?
Best,
Jan-Simon
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
On Thu, 13 Aug 2009, Jan-Simon Möller wrote:
Hi !
I've discovered bootstrap-cycles in Factory
1) ConsoleKit buildrequire polkit which requires ConsoleKit
2) libffi buildrequires gtk2-devel which buildrequires pango which
buildrequires
gobject-introspection which buildrequires libffi
Does this one matter? If so I can try building libffi from gcc44.spec
instead from libgcj44.spec.
Atm I can't bootstrap the packages in 2) (without nasty tricks), so lets try
that if its not too much hassle.
Regarding gcc4.4.1, i've 2 small issues left:
--- gcc44.spec.orig
+++ gcc44.spec
@@ -2221,6 +2242,7 @@ cat cpplib%{binsuffix}.lang gcc%{binsuff
%endif
%ifarch %arm
%{libsubdir}/include/mmintrin.h
+%{libsubdir}/include/arm_neon.h
%endif
%ifarch %ix86 x86_64
%{libsubdir}/include/cross-stdarg.h
And: bootstrapping gcc on ARM still requires s/-O/-O2/ in bootstrap-lean.
Should I submit a request with these 2 ?
Best,
Jan-Simon
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
| < Previous | Next > |