Bug#901488: Please provide static archives inside libtqt4-dev !

2018-06-15 Thread Diederik de Haas 
On vrijdag 15 juni 2018 02:30:46 CEST Lisandro Damián Nicanor Pérez Meyer 
wrote:
> > No, because of porting, it doesn't. But that time, that's on my side.
> > Though please note that no Bitcoin forks got ported to qt5 in general,
> > ever (not Bitcoin core itself, not Litecoin, not Peercoin. among more
> > than 5000 cryptocurrencies they all use qt4 when the gui feature is
> > available).
> 
> Well, they better do the switch, there will be no Qt4 in the near future.

FTR: bitcoin-qt and litecoin-qt (which are also packaged for Debian ) are 
using QT5 for a while now.
Monero also uses QT5 and upstream is working on Debian packages [1]. I dunno 
if the plan is to also bring it to Debian, but I think there's a reasonable 
chance as they want to make it available for Tails.

If your favorite crypto currency hasn't been updated to use QT5, there's a 
reasonable chance it's pretty much unmaintained and that should raise some red 
flags. There are a LOT of crypto currency projects which cloned bitcoin a long 
time ago, changed a few parameters and thought they were done. Several don't 
even compile. That's not a Debian problem, but an upstream problem.


[1] https://github.com/monero-project/monero/issues/2395

signature.asc
Description: This is a digitally signed message part.

Bug#901488: Please provide static archives inside libtqt4-dev !

2018-06-15 Thread none 

Le 2018-06-15 02:30, Lisandro Damián Nicanor Pérez Meyer a écrit :

El jueves, 14 de junio de 2018 20:42:21 -03 none escribió:

Hello,

>> If you refuse to fix it for Qt4, please fix it for Qt5 !
>
> - With respect to static libraries: we refuse for any version of Qt :-)

But, why ? Why make such exception ?


https://wiki.debian.org/StaticLinking#Downsides

So non static libraries.



Yes, but you’re providing static libraries for every libraries. From 
glibc to kdelibs.

Why making only Qt5 specificly follow such rule ?

Bug#901488: Please provide static archives inside libtqt4-dev !

2018-06-14 Thread Lisandro Damián Nicanor Pérez Meyer 
El jueves, 14 de junio de 2018 20:42:21 -03 none escribió:
> Hello,
> 
> >> If you refuse to fix it for Qt4, please fix it for Qt5 !
> > 
> > - With respect to static libraries: we refuse for any version of Qt :-)
> 
> But, why ? Why make such exception ?

https://wiki.debian.org/StaticLinking#Downsides

So non static libraries.
 
> > - With respect cross compiling: you should *really* try with Qt5. It
> > rocks.
> > Well, at least it has abeen a pleasure for the projects I keep so far
> > 
> > :-)
> 
> No, because of porting, it doesn't. But that time, that's on my side.
> Though please note that no Bitcoin forks got ported to qt5 in general,
> ever (not Bitcoin core itself, not Litecoin, not Peercoin. among more
> than 5000 cryptocurrencies they all use qt4 when the gui feature is
> available).

Well, they better do the switch, there will be no Qt4 in the near future.

> Qt5 still rely heavily on /proc/cpuinfo for building which returns the
> wrong architecture (hence the problem above).

I have never heard this, please enlighten me :-)

> I have no reason to port
> to qt5

If we get to it, no more Qt4 in Debian buster. Worst case scenario: Buster+1.
Really, Qt4 has been dead upstream since literally years.


-- 
 __
< ¿Nunca viste a una vaca hablar? >
 --
\   ^__^
 \  (oo)\___
(__)\   )\/\
||w |
|| ||

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#901488: Please provide static archives inside libtqt4-dev !

2018-06-14 Thread none 

Hello,


If you refuse to fix it for Qt4, please fix it for Qt5 !


- With respect to static libraries: we refuse for any version of Qt :-)


But, why ? Why make such exception ?

- With respect cross compiling: you should *really* try with Qt5. It 
rocks.
Well, at least it has abeen a pleasure for the projects I keep so far 
:-)


No, because of porting, it doesn't. But that time, that's on my side. 
Though please note that no Bitcoin forks got ported to qt5 in general, 
ever (not Bitcoin core itself, not Litecoin, not Peercoin. among more 
than 5000 cryptocurrencies they all use qt4 when the gui feature is 
available).


Qt5 still rely heavily on /proc/cpuinfo for building which returns the 
wrong architecture (hence the problem above). I have no reason to port 
to qt5, especially if it is still to buy monthly that hammer whereas I 
have the source code http://www.magicermine.com/



Cheers!

Bug#901488: Please provide static archives inside libtqt4-dev !

2018-06-14 Thread none 

Ok bitcoin-core was ported to qt5, indeed

Bug#901488: Please provide static archives inside libtqt4-dev !

2018-06-13 Thread none 

Package: qt4-x11
Version: 4:4.8.7+dfsg-11


Looks like debbuild doesn’t works well when used for cross compiling (I 
don’t have enough ram for native building on the target device) :


-march=armv8-a+crc+crypto+simd -mtune=cortex-a73.cortex-a53 -std=gnu++11 
-c -g -O2 -fdebug-prefix-map=/home/invite/qt4-x11-4.8.7+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=gnu++11 -I/usr/include/freetype2 -pthread 
-I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include 
-O2 -fvisibility=hidden -fvisibility-inlines-hidden -Wall -W 
-D_REENTRANT -fPIC -DQT_BUILD_CORE_LIB -DQT_NO_USING_NAMESPACE 
-DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT 
-DQT_USE_QSTRINGBUILDER -DQLIBRARYINFO_EPOCROOT -DQT_USE_ICU 
-DHB_EXPORT=Q_CORE_EXPORT -DQT_NO_DEBUG -D_LARGEFILE64_SOURCE 
-D_LARGEFILE_SOURCE -I../../mkspecs/linux-g++ -I. -I../../include 
-I../../include/QtCore -I.rcc/release-static -Iglobal 
-I../../tools/shared -I../3rdparty/harfbuzz/src -I../3rdparty/md5 
-I../3rdparty/md4 -I.moc/release-static -o 
.obj/release-static/qfutureinterface.o concurrent/qfutureinterface.cpp

{standard input}: Assembler messages:
{standard input}:8398: Error: operand mismatch -- `swpb x2,x20,[x19]'
{standard input}:8398: Info:did you mean this?
{standard input}:8398: Info:swpb w2, w20, [x19]
{standard input}:8419: Error: operand mismatch -- `swpb x4,x20,[x19]'
{standard input}:8419: Info:did you mean this?
{standard input}:8419: Info:swpb w4, w20, [x19]
{standard input}:8448: Error: operand mismatch -- `swpb x3,x5,[x6]'
{standard input}:8448: Info:did you mean this?
{standard input}:8448: Info:swpb w3, w5, [x6]
{standard input}:8491: Error: operand mismatch -- `swpb x10,x20,[x19]'
{standard input}:8491: Info:did you mean this?
{standard input}:8491: Info:swpb w10, w20, [x19]
{standard input}:8512: Error: operand mismatch -- `swpb x11,x20,[x19]'
{standard input}:8512: Info:did you mean this?
{standard input}:8512: Info:swpb w11, w20, [x19]
{standard input}:8541: Error: operand mismatch -- `swpb x3,x12,[x13]'
{standard input}:8541: Info:did you mean this?
{standard input}:8541: Info:swpb w3, w12, [x13]
{standard input}:8803: Error: operand mismatch -- `swpb x2,x20,[x19]'
{standard input}:8803: Info:did you mean this?
{standard input}:8803: Info:swpb w2, w20, [x19]
{standard input}:8824: Error: operand mismatch -- `swpb x4,x20,[x19]'
{standard input}:8824: Info:did you mean this?
{standard input}:8824: Info:swpb w4, w20, [x19]
{standard input}:8853: Error: operand mismatch -- `swpb x3,x5,[x6]'
{standard input}:8853: Info:did you mean this?
{standard input}:8853: Info:swpb w3, w5, [x6]
{standard input}:8896: Error: operand mismatch -- `swpb x10,x20,[x19]'
{standard input}:8896: Info:did you mean this?
{standard input}:8896: Info:swpb w10, w20, [x19]
{standard input}:8917: Error: operand mismatch -- `swpb x11,x20,[x19]'
{standard input}:8917: Info:did you mean this?
{standard input}:8917: Info:swpb w11, w20, [x19]
{standard input}:8946: Error: operand mismatch -- `swpb x3,x12,[x13]'
{standard input}:8946: Info:did you mean this?
{standard input}:8946: Info:swpb w3, w12, [x13]
{standard input}:9180: Error: operand mismatch -- `swpb x2,x20,[x19]'
{standard input}:9180: Info:did you mean this?
{standard input}:9180: Info:swpb w2, w20, [x19]
{standard input}:9203: Error: operand mismatch -- `swpb x4,x20,[x19]'
{standard input}:9203: Info:did you mean this?
{standard input}:9203: Info:swpb w4, w20, [x19]
{standard input}:9234: Error: operand mismatch -- `swpb x3,x5,[x6]'
{standard input}:9234: Info:did you mean this?
{standard input}:9234: Info:swpb w3, w5, [x6]
{standard input}:9407: Error: operand mismatch -- `swpb x2,x20,[x19]'
{standard input}:9407: Info:did you mean this?
{standard input}:9407: Info:swpb w2, w20, [x19]
{standard input}:9430: Error: operand mismatch -- `swpb x4,x20,[x19]'
{standard input}:9430: Info:did you mean this?
{standard input}:9430: Info:swpb w4, w20, [x19]
{standard input}:9461: Error: operand mismatch -- `swpb x3,x5,[x6]'
{standard input}:9461: Info:did you mean this?
{standard input}:9461: Info:swpb w3, w5, [x6]
{standard input}:9604: Error: operand mismatch -- `swpb x0,x20,[x19]'
{standard input}:9604: Info:did you mean this?
{standard input}:9604: Info:swpb w0, w20, [x19]
{standard input}:9627: Error: operand mismatch -- `swpb x3,x20,[x19]'
{standard input}:9627: Info:did you mean this?
{standard input}:9627: Info:swpb w3, w20, [x19]
{standard input}:9658: Error: operand mismatch -- `swpb x1,x6,[x5]'
{standard input}:9658: Info:did you mean this?
{standard input}:9658: Info:swpb w1, w6, [x5]
{standard