Bug#746900: qtdeclarative-opensource-src: ftbfs with GCC-4.9
On Thursday 26 June 2014 12:45:51 Yunqiang Su wrote: On Thu, Jun 26, 2014 at 12:35 PM, Lisandro Damián Nicanor Pérez perezme...@gmail.com wrote: Note: I'm sending yuou a copy because I mistakenly sent it to the original bug reporter. On Thursday 26 June 2014 12:16:22 Yunqiang Su wrote: I refreshed this patch for mips64el Yunqiang: again, when we are talking about symbols files, a simple patch for just one arch is not enough. The best way to solve this is to let mips64[el] build logs be available trough debian-ports. Yes, of course, while we are still waiting for the debian-ports guys to let us in. For now, you can get the buildlog from http://mips64el.debian.net/debian/buildlog Ah, that's a good workaround, thanks! -- Compartir las cosas buenas es una necesidad fácil de satisfacer. Compartir las cosas malas es una necesidad mayor, pero mucho mas difícil de satisfacer. Sin embargo, es el compartir las cosas malas lo que mas nos une como hermanos. Lisandro Damián Nicanor Pérez Meyer Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#746900: qtdeclarative-opensource-src: ftbfs with GCC-4.9
On Thu, Jun 26, 2014 at 8:50 PM, Lisandro Damián Nicanor Pérez Meyer perezme...@gmail.com wrote: On Thursday 26 June 2014 12:45:51 Yunqiang Su wrote: On Thu, Jun 26, 2014 at 12:35 PM, Lisandro Damián Nicanor Pérez perezme...@gmail.com wrote: Note: I'm sending yuou a copy because I mistakenly sent it to the original bug reporter. On Thursday 26 June 2014 12:16:22 Yunqiang Su wrote: I refreshed this patch for mips64el Yunqiang: again, when we are talking about symbols files, a simple patch for just one arch is not enough. The best way to solve this is to let mips64[el] build logs be available trough debian-ports. Yes, of course, while we are still waiting for the debian-ports guys to let us in. For now, you can get the buildlog from http://mips64el.debian.net/debian/buildlog Ah, that's a good workaround, thanks! I noticed that your new upload ftbfs on mips64el again. I think that we should make sure that the packages build successfully on any archs, so we can get the full symbols list on all of these archs. If they ftbfs, it will cost us much more time on get the full list of symbols. -- Compartir las cosas buenas es una necesidad fácil de satisfacer. Compartir las cosas malas es una necesidad mayor, pero mucho mas difícil de satisfacer. Sin embargo, es el compartir las cosas malas lo que mas nos une como hermanos. Lisandro Damián Nicanor Pérez Meyer Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ -- Yunqiang Su -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746900: qtdeclarative-opensource-src: ftbfs with GCC-4.9
On Friday 27 June 2014 09:32:59 Yunqiang Su wrote: [snip] Ah, that's a good workaround, thanks! I noticed that your new upload ftbfs on mips64el again. I think that we should make sure that the packages build successfully on any archs, so we can get the full symbols list on all of these archs. Sadly that's expected. I filled #736640 and it seemed solved, but I'm now finding that it must not be the case, although I really need to carefully test it and check that it's not pkgkde-tools' symbolshelper that doesn't knows how to handle more diff in the same buildlog (although I really doubt it). Anyway it has always been like this: if you ship more than one lib in the same source package, you might not get all the symbols changes needed in the same build and thus you might still get symbols changing. If you take a look at [0] you can see that I uploaded it two more times after closing this bug. You can rest assured that I'm taking a look at buildds, and that's why I insist in making mips64[el] available in debian-ports as soon as possible, it really makes my job much easier. [0] http://metadata.ftp-master.debian.org/changelogs//main/q/qtdeclarative-opensource-src/qtdeclarative-opensource-src_5.3.1-1_changelog -- No pienses que estoy loco, es sólo una manera de actuar De mí - Charly García Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#746900: qtdeclarative-opensource-src: ftbfs with GCC-4.9
On Fri, Jun 27, 2014 at 10:06 AM, Lisandro Damián Nicanor Pérez Meyer perezme...@gmail.com wrote: On Friday 27 June 2014 09:32:59 Yunqiang Su wrote: [snip] Ah, that's a good workaround, thanks! I noticed that your new upload ftbfs on mips64el again. I think that we should make sure that the packages build successfully on any archs, so we can get the full symbols list on all of these archs. Sadly that's expected. I filled #736640 and it seemed solved, but I'm now finding that it must not be the case, although I really need to carefully test it and check that it's not pkgkde-tools' symbolshelper that doesn't knows how to handle more diff in the same buildlog (although I really doubt it). Anyway it has always been like this: if you ship more than one lib in the same source package, you might not get all the symbols changes needed in the same build and thus you might still get symbols changing. If you take a look at [0] you can see that I uploaded it two more times after closing this bug. You can rest assured that I'm taking a look at buildds, and that's why I insist in making mips64[el] available in debian-ports as soon as possible, it really makes my job much easier. I wish this happening as soon as possible. [0] http://metadata.ftp-master.debian.org/changelogs//main/q/qtdeclarative-opensource-src/qtdeclarative-opensource-src_5.3.1-1_changelog -- No pienses que estoy loco, es sólo una manera de actuar De mí - Charly García Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ -- Yunqiang Su -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746900: qtdeclarative-opensource-src: ftbfs with GCC-4.9
On Thursday 26 June 2014 12:16:22 Yunqiang Su wrote: I refreshed this patch for mips64el Yunqiang: again, when we are talking about symbols files, a simple patch for just one arch is not enough. The best way to solve this is to let mips64[el] build logs be available trough debian-ports. Kinds regards, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#746900: qtdeclarative-opensource-src: ftbfs with GCC-4.9
On Thu, Jun 26, 2014 at 12:35 PM, Lisandro Damián Nicanor Pérez perezme...@gmail.com wrote: Note: I'm sending yuou a copy because I mistakenly sent it to the original bug reporter. On Thursday 26 June 2014 12:16:22 Yunqiang Su wrote: I refreshed this patch for mips64el Yunqiang: again, when we are talking about symbols files, a simple patch for just one arch is not enough. The best way to solve this is to let mips64[el] build logs be available trough debian-ports. Yes, of course, while we are still waiting for the debian-ports guys to let us in. For now, you can get the buildlog from http://mips64el.debian.net/debian/buildlog Kinds regards, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ -- Yunqiang Su -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746900: qtdeclarative-opensource-src: ftbfs with GCC-4.9
With the attached patch, it can be built on mips64el, amd64, i386
without symbols warning.
On Tue, May 13, 2014 at 2:15 PM, Yunqiang Su wzss...@gmail.com wrote:
The attachment is build log of mips64el.
On mips64el, beside the same gcc-4.9 problem,
there are some more problems.
With this patch, I can build it on both amd64, mips64el, and i386.
While it still has some warnings.
I think that we should try to build it on experimental to determine the
symbols
for archs.
on amd64: no warnings
on mips64el
--- debian/libqt5quickparticles5.symbols
(libqt5quickparticles5_5.2.1-5+mips64.1_mips64el)
+++ dpkg-gensymbolsGKlBFe 2014-05-13 14:02:42.189846293 +
@@ -1,5 +1,6 @@
libQt5QuickParticles.so.5 libqt5quickparticles5 #MINVER#
| libqt5quickparticles5 #MINVER#, qtdeclarative-abi-5-2-1
+ _ZN10QByteArray7reserveEi@Base 5.2.1-5+mips64.1
(optional=templinst|arch=ia64
sparc)_ZN11QMetaMethod10fromSignalIM18QQuickTrailEmitterFv12QQmlV4HandleS2_EEES_T_@Base
5.2.0 1
(optional=templinst|arch=ia64
sparc)_ZN11QMetaMethod10fromSignalIM20QQuickCustomAffectorFv12QQmlV4HandledEEES_T_@Base
5.2.0 1
(optional=templinst|arch=ia64
sparc)_ZN11QMetaMethod10fromSignalIM21QQuickParticleEmitterFv12QQmlV4HandleEEES_T_@Base
5.2.0 1
on i386:
dpkg-gensymbols: warning: some new symbols appeared in the symbols
file: see diff output below
dpkg-gensymbols: warning: debian/libqt5qml5/DEBIAN/symbols doesn't
match completely debian/libqt5qml5.symbols
--- debian/libqt5qml5.symbols (libqt5qml5_5.2.1-5+mips64.1_i386)
+++ dpkg-gensymbolsvlHWhi 2014-05-13 05:56:04.078015536 +
@@ -353,6 +353,9 @@
_ZN13QQmlValueType16staticMetaObjectE@Base 5.0.2 1
_ZN13QQmlValueTypeC1EiP7QObject@Base 5.0.2 1
_ZN13QQmlValueTypeC2EiP7QObject@Base 5.0.2 1
+ _ZN13QQmlValueTypeD0Ev@Base 5.2.1-5+mips64.1
+ _ZN13QQmlValueTypeD1Ev@Base 5.2.1-5+mips64.1
+ _ZN13QQmlValueTypeD2Ev@Base 5.2.1-5+mips64.1
_ZN14QQmlExpression10clearErrorEv@Base 5.0.2
_ZN14QQmlExpression11qt_metacallEN11QMetaObject4CallEiPPv@Base 5.0.2
_ZN14QQmlExpression11qt_metacastEPKc@Base 5.0.2
@@ -2234,6 +2237,7 @@
_ZN8QQmlTypeD2Ev@Base 5.0.2 1
(optional=templinst|arch=ia64)_ZN8QVariant9fromValueIP9ListModelEES_RKT_@Base
5.2.0
(arch=alpha armel mips mipsel powerpc ppc64
s390x)_ZN9QBitArray6setBitEi@Base 5.2.1
+ _ZN9QBitArray8clearBitEi@Base 5.2.1-5+mips64.1
_ZN9QJSEngine10newQObjectEP7QObject@Base 5.0.2
_ZN9QJSEngine11qt_metacallEN11QMetaObject4CallEiPPv@Base 5.0.2
_ZN9QJSEngine11qt_metacastEPKc@Base 5.0.2
@@ -2804,6 +2808,7 @@
(optional=templinst|arch=ia64
sparc)_ZNSt6vectorIN3JSC4Yarr8ByteTermESaIS2_EE13_M_insert_auxIIRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
5.2.0
(optional=templinst|arch=ia64
sparc|subst)_ZNSt6vectorIN3JSC4Yarr8ByteTermESaIS2_EE7reserveE{size_t}@Base
5.2.0
(optional=templinst|subst)_ZNSt6vectorIS_IiSaIiEESaIS1_EE17_M_default_appendE{size_t}@Base
5.2.1
+ _ZNSt6vectorIcSaIcEE17_M_default_appendEj@Base 5.2.1-5+mips64.1
(optional=templinst|arch=ia64
sparc)_ZNSt6vectorIiSaIiEE13_M_insert_auxIIRKiEEEvN9__gnu_cxx17__normal_iteratorIPiS1_EEDpOT_@Base
5.2.1
(optional=templinst|subst)_ZNSt6vectorIiSaIiEE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPiS1_EE{size_t}RKi@Base
5.2.1
(optional=templinst|arch=!ia64
!sparc)_ZNSt6vectorIiSaIiEE19_M_emplace_back_auxIIRKiEEEvDpOT_@Base
5.2.1
@@ -2821,7 +2826,9 @@
(arch=alpha amd64 armel armhf hurd-i386 i386 kfreebsd-amd64
kfreebsd-i386 mips mipsel mips64 mips64el powerpc ppc64
s390x)_ZNSt6vectorItSaItEE13_M_insert_auxIJRKtEEEvN9__gnu_cxx17__normal_iteratorIPtS1_EEDpOT_@Base
5.2.0
(arch=alpha amd64 armel armhf hurd-i386 i386 kfreebsd-amd64
kfreebsd-i386 mips mipsel mips64 mips64el powerpc ppc64
s390x)_ZNSt6vectorItSaItEE13_M_insert_auxIJtEEEvN9__gnu_cxx17__normal_iteratorIPtS1_EEDpOT_@Base
5.2.0
(arch=alpha amd64 armel armhf hurd-i386 i386 kfreebsd-amd64
kfreebsd-i386 mips mipsel mips64 mips64el powerpc ppc64
s390x)_ZNSt6vectorItSaItEE19_M_emplace_back_auxIIRKtEEEvDpOT_@Base
5.2.0
+ _ZNSt6vectorItSaItEE19_M_emplace_back_auxIItEEEvDpOT_@Base 5.2.1-5+mips64.1
(arch=alpha amd64 armel armhf hurd-i386 i386 kfreebsd-amd64
kfreebsd-i386 mips mipsel mips64 mips64el powerpc ppc64
s390x)_ZNSt6vectorItSaItEE19_M_emplace_back_auxIJRKtEEEvDpOT_@Base
5.2.0
+ _ZNSt6vectorItSaItEE19_M_emplace_back_auxIJtEEEvDpOT_@Base 5.2.1-5+mips64.1
(optional=templinst|arch=ia64
sparc)_ZNSt6vectorItSaItEE6insertEN9__gnu_cxx17__normal_iteratorIPtS1_EERKt@Base
5.2.0
(optional=templinst|arch=sparc)_ZSt11__push_heapIN5QListI4QUrlE8iteratorEiS1_N12QQmlSequenceIS2_E14CompareFunctorEEvT_T0_S8_T1_T2_@Base
5.2.0 1
(optional=templinst|arch=sparc)_ZSt11__push_heapIN5QListI4QUrlE8iteratorEiS1_N12QQmlSequenceIS2_E21DefaultCompareFunctorEEvT_T0_S8_T1_T2_@Base
5.2.0 1
@@ -2868,8 +2875,10 @@
(optional=templinst|arch=ia64)_ZSt13__adjust_heapIN5QListIiE8iteratorExiEvT_T0_S4_T1_@Base
5.2.0 1
Bug#746900: qtdeclarative-opensource-src: ftbfs with GCC-4.9
The attachment is build log of mips64el.
On mips64el, beside the same gcc-4.9 problem,
there are some more problems.
With this patch, I can build it on both amd64, mips64el, and i386.
While it still has some warnings.
I think that we should try to build it on experimental to determine the symbols
for archs.
on amd64: no warnings
on mips64el
--- debian/libqt5quickparticles5.symbols
(libqt5quickparticles5_5.2.1-5+mips64.1_mips64el)
+++ dpkg-gensymbolsGKlBFe 2014-05-13 14:02:42.189846293 +
@@ -1,5 +1,6 @@
libQt5QuickParticles.so.5 libqt5quickparticles5 #MINVER#
| libqt5quickparticles5 #MINVER#, qtdeclarative-abi-5-2-1
+ _ZN10QByteArray7reserveEi@Base 5.2.1-5+mips64.1
(optional=templinst|arch=ia64
sparc)_ZN11QMetaMethod10fromSignalIM18QQuickTrailEmitterFv12QQmlV4HandleS2_EEES_T_@Base
5.2.0 1
(optional=templinst|arch=ia64
sparc)_ZN11QMetaMethod10fromSignalIM20QQuickCustomAffectorFv12QQmlV4HandledEEES_T_@Base
5.2.0 1
(optional=templinst|arch=ia64
sparc)_ZN11QMetaMethod10fromSignalIM21QQuickParticleEmitterFv12QQmlV4HandleEEES_T_@Base
5.2.0 1
on i386:
dpkg-gensymbols: warning: some new symbols appeared in the symbols
file: see diff output below
dpkg-gensymbols: warning: debian/libqt5qml5/DEBIAN/symbols doesn't
match completely debian/libqt5qml5.symbols
--- debian/libqt5qml5.symbols (libqt5qml5_5.2.1-5+mips64.1_i386)
+++ dpkg-gensymbolsvlHWhi 2014-05-13 05:56:04.078015536 +
@@ -353,6 +353,9 @@
_ZN13QQmlValueType16staticMetaObjectE@Base 5.0.2 1
_ZN13QQmlValueTypeC1EiP7QObject@Base 5.0.2 1
_ZN13QQmlValueTypeC2EiP7QObject@Base 5.0.2 1
+ _ZN13QQmlValueTypeD0Ev@Base 5.2.1-5+mips64.1
+ _ZN13QQmlValueTypeD1Ev@Base 5.2.1-5+mips64.1
+ _ZN13QQmlValueTypeD2Ev@Base 5.2.1-5+mips64.1
_ZN14QQmlExpression10clearErrorEv@Base 5.0.2
_ZN14QQmlExpression11qt_metacallEN11QMetaObject4CallEiPPv@Base 5.0.2
_ZN14QQmlExpression11qt_metacastEPKc@Base 5.0.2
@@ -2234,6 +2237,7 @@
_ZN8QQmlTypeD2Ev@Base 5.0.2 1
(optional=templinst|arch=ia64)_ZN8QVariant9fromValueIP9ListModelEES_RKT_@Base
5.2.0
(arch=alpha armel mips mipsel powerpc ppc64
s390x)_ZN9QBitArray6setBitEi@Base 5.2.1
+ _ZN9QBitArray8clearBitEi@Base 5.2.1-5+mips64.1
_ZN9QJSEngine10newQObjectEP7QObject@Base 5.0.2
_ZN9QJSEngine11qt_metacallEN11QMetaObject4CallEiPPv@Base 5.0.2
_ZN9QJSEngine11qt_metacastEPKc@Base 5.0.2
@@ -2804,6 +2808,7 @@
(optional=templinst|arch=ia64
sparc)_ZNSt6vectorIN3JSC4Yarr8ByteTermESaIS2_EE13_M_insert_auxIIRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
5.2.0
(optional=templinst|arch=ia64
sparc|subst)_ZNSt6vectorIN3JSC4Yarr8ByteTermESaIS2_EE7reserveE{size_t}@Base
5.2.0
(optional=templinst|subst)_ZNSt6vectorIS_IiSaIiEESaIS1_EE17_M_default_appendE{size_t}@Base
5.2.1
+ _ZNSt6vectorIcSaIcEE17_M_default_appendEj@Base 5.2.1-5+mips64.1
(optional=templinst|arch=ia64
sparc)_ZNSt6vectorIiSaIiEE13_M_insert_auxIIRKiEEEvN9__gnu_cxx17__normal_iteratorIPiS1_EEDpOT_@Base
5.2.1
(optional=templinst|subst)_ZNSt6vectorIiSaIiEE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPiS1_EE{size_t}RKi@Base
5.2.1
(optional=templinst|arch=!ia64
!sparc)_ZNSt6vectorIiSaIiEE19_M_emplace_back_auxIIRKiEEEvDpOT_@Base
5.2.1
@@ -2821,7 +2826,9 @@
(arch=alpha amd64 armel armhf hurd-i386 i386 kfreebsd-amd64
kfreebsd-i386 mips mipsel mips64 mips64el powerpc ppc64
s390x)_ZNSt6vectorItSaItEE13_M_insert_auxIJRKtEEEvN9__gnu_cxx17__normal_iteratorIPtS1_EEDpOT_@Base
5.2.0
(arch=alpha amd64 armel armhf hurd-i386 i386 kfreebsd-amd64
kfreebsd-i386 mips mipsel mips64 mips64el powerpc ppc64
s390x)_ZNSt6vectorItSaItEE13_M_insert_auxIJtEEEvN9__gnu_cxx17__normal_iteratorIPtS1_EEDpOT_@Base
5.2.0
(arch=alpha amd64 armel armhf hurd-i386 i386 kfreebsd-amd64
kfreebsd-i386 mips mipsel mips64 mips64el powerpc ppc64
s390x)_ZNSt6vectorItSaItEE19_M_emplace_back_auxIIRKtEEEvDpOT_@Base
5.2.0
+ _ZNSt6vectorItSaItEE19_M_emplace_back_auxIItEEEvDpOT_@Base 5.2.1-5+mips64.1
(arch=alpha amd64 armel armhf hurd-i386 i386 kfreebsd-amd64
kfreebsd-i386 mips mipsel mips64 mips64el powerpc ppc64
s390x)_ZNSt6vectorItSaItEE19_M_emplace_back_auxIJRKtEEEvDpOT_@Base
5.2.0
+ _ZNSt6vectorItSaItEE19_M_emplace_back_auxIJtEEEvDpOT_@Base 5.2.1-5+mips64.1
(optional=templinst|arch=ia64
sparc)_ZNSt6vectorItSaItEE6insertEN9__gnu_cxx17__normal_iteratorIPtS1_EERKt@Base
5.2.0
(optional=templinst|arch=sparc)_ZSt11__push_heapIN5QListI4QUrlE8iteratorEiS1_N12QQmlSequenceIS2_E14CompareFunctorEEvT_T0_S8_T1_T2_@Base
5.2.0 1
(optional=templinst|arch=sparc)_ZSt11__push_heapIN5QListI4QUrlE8iteratorEiS1_N12QQmlSequenceIS2_E21DefaultCompareFunctorEEvT_T0_S8_T1_T2_@Base
5.2.0 1
@@ -2868,8 +2875,10 @@
(optional=templinst|arch=ia64)_ZSt13__adjust_heapIN5QListIiE8iteratorExiEvT_T0_S4_T1_@Base
5.2.0 1
(optional=templinst|arch=ia64)_ZSt13__adjust_heapIN5QListIiE8iteratorExiN12QQmlSequenceIS1_E14CompareFunctorEEvT_T0_S7_T1_T2_@Base
5.2.0 1
(optional=templinst|arch=ia64)_ZSt13__adjust_heapIN5QListIiE8iteratorExiN12QQmlSequenceIS1_E21DefaultCompareFunctorEEvT_T0_S7_T1_T2_@Base
5.2.0 1
+
Bug#746897: Bug#746900: qtdeclarative-opensource-src: ftbfs with GCC-4.9
These bugs seems to be just symbols issues. If so, trying to fix them while gcc-4.9 is not the default compiler might be a call for problems and rebuilds. The best approach here will be to check the packages once gcc-4.9 is the default compiler letting the buildds FTBFS to get the symbols changes and then fix them all at once. Of course, this also depends on when gcc-4.9 becomes the default compiler and when the next upstream release happens. Kinds regards, Lisandro. -- No pienses que estoy loco, es sólo una manera de actuar De mí - Charly García Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#746897: Bug#746900: qtdeclarative-opensource-src: ftbfs with GCC-4.9
Am 04.05.2014 19:36, schrieb Lisandro Damián Nicanor Pérez Meyer: These bugs seems to be just symbols issues. If so, trying to fix them while just symbols resulting in a build failure. gcc-4.9 is not the default compiler might be a call for problems and rebuilds. The best approach here will be to check the packages once gcc-4.9 is the default compiler letting the buildds FTBFS to get the symbols changes and then fix them all at once. sorry, I don't think it's wise to fix an issue only when 4.9 already is the default compiler. The build logs for amd64 are available, and you could build a package on a 32bit architecture too if you think they will differ. Of course, this also depends on when gcc-4.9 becomes the default compiler and when the next upstream release happens. no next upstream release has anything to do with this. Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746897: Bug#746900: qtdeclarative-opensource-src: ftbfs with GCC-4.9
On Monday 05 May 2014 01:02:45 Matthias Klose wrote: Am 04.05.2014 19:36, schrieb Lisandro Damián Nicanor Pérez Meyer: These bugs seems to be just symbols issues. If so, trying to fix them while just symbols resulting in a build failure. We might have a different understanding of what does default compiler means, but it's not a build failure until the compiler used by the buildds is 4.9. gcc-4.9 is not the default compiler might be a call for problems and rebuilds. The best approach here will be to check the packages once gcc-4.9 is the default compiler letting the buildds FTBFS to get the symbols changes and then fix them all at once. sorry, I don't think it's wise to fix an issue only when 4.9 already is the default compiler. The build logs for amd64 are available, and you could build a package on a 32bit architecture too if you think they will differ. And what about the other archs? Building webkit alone takes much effort and more than a day on some of them. No, it won't happen until the buildds start using 4.9. Of course, this also depends on when gcc-4.9 becomes the default compiler and when the next upstream release happens. no next upstream release has anything to do with this. Not in your POV, but let's say it doesn't, there is no need for you to understand what happens on the Qt side after all. Regards, Lisandro. -- 1: Una computadora sirve: * Para tratar de dominar el mundo, un caso conocido de esto fue el de Skinet Damian Nadales http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
