Re: [Interest] Qt5.15 from source on centOS 7

2022-06-19 Thread Alexander Carôt
Hej Mike and Simon,

allright – although I successfully (conventionally) installed a more recent gcc 
on my centOS 7 I ran into further trouble with the actual Qt5.15 compilation. 
Now I brought all back to centOS defaults including gcc4.8 and Qt5.9.

As suggested by you I will now give it a try with the Developer Toolset and get 
back later.

Thanks and best

Alex

--
http://www.carot.de
Email : alexan...@carot.de
Tel.: +49 (0)177 5719797


> Gesendet: Sonntag, 19. Juni 2022 um 01:06 Uhr
> Von: "Mike Rochefort" 
> An: interest@qt-project.org
> Betreff: Re: [Interest] Qt5.15 from source on centOS 7
>
> Alex, I'm going to echo Simon's suggestion from earlier. The Developer 
> Toolsets are designed and provided for the purpose of enabling the use 
> of newer toolchains on RHEL-compatible platforms. Compiled objects still 
> dynamically link against the system libraries and will statically link 
> in the pieces from the toolset that they need for portability.
> 
> To access DTS on CentOS 7:
> $ yum install centos-release-scl-rh
> $ yum install devtoolset-
> 
> To use a DTS:
> # Run a specific command from the toolset
> $ scl enable devtoolset-11 'g++ --version'
> 
> # Run an interactive sub-shell inside the DTS environment
> $ scl enable devtoolset-11 $SHELL
> $ g++ --version
> 
> DTS 7 through DTS 11 (e.g. GCC 7 through 11) are currently available on 
> the mirrors; I would recommend going as current as you can.
> 
> Cheers,
> Mike
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] Qt5.15 from source on centOS 7

2022-06-19 Thread Alexander Carôt
Succes !! Thanks so much for this hint of using the Developer Toolset ! Qt5.15 
is compiled and installed just fine but now a new issue arises which might have 
a different cause but I am embedding it into this thread anyways: My app 
contains a secure websocket and anything related to ssl is not available 
obviously:


echoserver.cpp: In Konstruktor »EchoServer::EchoServer(quint16, bool, 
QObject*)«:
echoserver.cpp:18:63: Fehler: »SecureMode« ist kein Element von 
»QWebSocketServer«
 QWebSocketServer::SecureMode, 
this)),
   ^~
echoserver.cpp:27:23: Fehler: Aggregat »QSslConfiguration sslConfiguration« hat 
unvollständigen Typ und kann nicht definiert werden
 QSslConfiguration sslConfiguration;
   ^~~~
echoserver.cpp:33:19: Fehler: Variable »QSslKey sslKey« hat Initialisierung, 
aber unvollständigen Typ
 QSslKey sslKey(&keyFile, QSsl::Rsa, QSsl::Pem);
   ^
echoserver.cpp:36:40: Fehler: »QSslSocket« wurde nicht deklariert
 sslConfiguration.setPeerVerifyMode(QSslSocket::VerifyNone);
^~
echoserver.cpp:40:25: Fehler: »class QWebSocketServer« hat kein Element namens 
»setSslConfiguration«
 m_pWebSocketServer->setSslConfiguration(sslConfiguration);
 ^~~
echoserver.cpp:52:56: Fehler: »sslErrors« ist kein Element von 
»QWebSocketServer«
 connect(m_pWebSocketServer, &QWebSocketServer::sslErrors,
^
echoserver.cpp: In Elementfunktion »void EchoServer::onNewConnection()«:
echoserver.cpp:190:14: Fehler: »class QWebSocket« hat kein Element namens 
»ignoreSslErrors«
 pSocket->ignoreSslErrors();


I believe there is another module to be compiled, however, since I build 
everything I currently don't know how to proceed next.

Thanks for helping me out also with this,
best

Alex

--
http://www.carot.de
Email : alexan...@carot.de
Tel.: +49 (0)177 5719797


> Gesendet: Sonntag, 19. Juni 2022 um 09:49 Uhr
> Von: "Alexander Carôt" 
> An: "Mike Rochefort" 
> Cc: interest@qt-project.org
> Betreff: Re: [Interest] Qt5.15 from source on centOS 7
>
> Hej Mike and Simon,
> 
> allright – although I successfully (conventionally) installed a more recent 
> gcc on my centOS 7 I ran into further trouble with the actual Qt5.15 
> compilation. Now I brought all back to centOS defaults including gcc4.8 and 
> Qt5.9.
> 
> As suggested by you I will now give it a try with the Developer Toolset and 
> get back later.
> 
> Thanks and best
> 
> Alex
> 
> --
> http://www.carot.de
> Email : alexan...@carot.de
> Tel.: +49 (0)177 5719797
> 
> 
> > Gesendet: Sonntag, 19. Juni 2022 um 01:06 Uhr
> > Von: "Mike Rochefort" 
> > An: interest@qt-project.org
> > Betreff: Re: [Interest] Qt5.15 from source on centOS 7
> >
> > Alex, I'm going to echo Simon's suggestion from earlier. The Developer 
> > Toolsets are designed and provided for the purpose of enabling the use 
> > of newer toolchains on RHEL-compatible platforms. Compiled objects still 
> > dynamically link against the system libraries and will statically link 
> > in the pieces from the toolset that they need for portability.
> > 
> > To access DTS on CentOS 7:
> > $ yum install centos-release-scl-rh
> > $ yum install devtoolset-
> > 
> > To use a DTS:
> > # Run a specific command from the toolset
> > $ scl enable devtoolset-11 'g++ --version'
> > 
> > # Run an interactive sub-shell inside the DTS environment
> > $ scl enable devtoolset-11 $SHELL
> > $ g++ --version
> > 
> > DTS 7 through DTS 11 (e.g. GCC 7 through 11) are currently available on 
> > the mirrors; I would recommend going as current as you can.
> > 
> > Cheers,
> > Mike
> > ___
> > Interest mailing list
> > Interest@qt-project.org
> > https://lists.qt-project.org/listinfo/interest
> >
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] Build report - QT 6.3 on FreeBSD 13.1

2022-06-19 Thread Thiago Macieira
On Saturday, 18 June 2022 21:42:23 PDT Chris Benesch wrote:
> especially that annoying xcb stuff which for some reason on Linux is broken
> down into about 20 separate packages.
> CMAKE_LIBRARY_PATH=/usr/local/lib

That's not only annoying, it's counter-productive. Those libraries are tiny, 
and yet each library has a *minimum* RSS commitment of 3 pages (12 kB) on 
Linux (FreeBSD *may* compile them to 2, I haven't checked), one of which 
cannot be shared. The 33 libraries combined need only a total of 16 writable 
pages, instead of the 35 they actually consume.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Cloud Software Architect - Intel DCAI Cloud Engineering



___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] Qt5.15 from source on centOS 7

2022-06-19 Thread Thiago Macieira
On Sunday, 19 June 2022 03:51:43 PDT Alexander Carôt wrote:
> Succes !! Thanks so much for this hint of using the Developer Toolset !
> Qt5.15 is compiled and installed just fine but now a new issue arises which
> might have a different cause but I am embedding it into this thread
> anyways: My app contains a secure websocket and anything related to ssl is
> not available obviously:

Please paste English messages.

> echoserver.cpp: In Konstruktor »EchoServer::EchoServer(quint16, bool,
> QObject*)«: echoserver.cpp:18:63: Fehler: »SecureMode« ist kein Element von
> »QWebSocketServer« QWebSocketServer::SecureMode, this)), ^~
> echoserver.cpp:27:23: Fehler: Aggregat »QSslConfiguration sslConfiguration«
> hat unvollständigen Typ und kann nicht definiert werden QSslConfiguration
> sslConfiguration;
>^~~~

I'm going to guess that this means the type QSslConfiguration is unknown.

You need OpenSSL 1.1 to enable SSL support in QtNetwork 5.15.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Cloud Software Architect - Intel DCAI Cloud Engineering



___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] Build report - QT 6.3 on FreeBSD 13.1

2022-06-19 Thread Henry Skoglund

On 2022-06-19 17:57, Thiago Macieira wrote:

On Saturday, 18 June 2022 21:42:23 PDT Chris Benesch wrote:

especially that annoying xcb stuff which for some reason on Linux is broken
down into about 20 separate packages.
CMAKE_LIBRARY_PATH=/usr/local/lib

That's not only annoying, it's counter-productive. Those libraries are tiny,
and yet each library has a *minimum* RSS commitment of 3 pages (12 kB) on
Linux (FreeBSD *may* compile them to 2, I haven't checked), one of which
cannot be shared. The 33 libraries combined need only a total of 16 writable
pages, instead of the 35 they actually consume.


That plethora of libxcb-xxx libraries kept breaking my build of 6.3.1 on 
a new Ubuntu 22.04 recently. First I tried installing them nicely one by 
one:

sudo apt install libxcb-fruitbasket
sudo apt install libxcb-flowerarrangement
sudo apt install libxcb-birdwatcher
...
etc. etc. until I learned that you could do
sudo apt install libxcb*

Got all 68 (!) of them but at least my Qt build was successful :-)

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] Qt5.15 from source on centOS 7

2022-06-19 Thread Chris Benesch
Build OpenSSL 3 and add its install directory lib/pkgconfig to
PKG_CONFIG_PATH and choose -openssl-linked as one of the config
parameters.  If you can get through configure, it should build.

On Sun, Jun 19, 2022 at 10:03 AM Thiago Macieira 
wrote:

> On Sunday, 19 June 2022 03:51:43 PDT Alexander Carôt wrote:
> > Succes !! Thanks so much for this hint of using the Developer Toolset !
> > Qt5.15 is compiled and installed just fine but now a new issue arises
> which
> > might have a different cause but I am embedding it into this thread
> > anyways: My app contains a secure websocket and anything related to ssl
> is
> > not available obviously:
>
> Please paste English messages.
>
> > echoserver.cpp: In Konstruktor »EchoServer::EchoServer(quint16, bool,
> > QObject*)«: echoserver.cpp:18:63: Fehler: »SecureMode« ist kein Element
> von
> > »QWebSocketServer« QWebSocketServer::SecureMode, this)), ^~
> > echoserver.cpp:27:23: Fehler: Aggregat »QSslConfiguration
> sslConfiguration«
> > hat unvollständigen Typ und kann nicht definiert werden QSslConfiguration
> > sslConfiguration;
> >^~~~
>
> I'm going to guess that this means the type QSslConfiguration is unknown.
>
> You need OpenSSL 1.1 to enable SSL support in QtNetwork 5.15.
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Cloud Software Architect - Intel DCAI Cloud Engineering
>
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>


-- 
Chris Benesch
BeneschTech, LLC
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] Qt5.15 from source on centOS 7

2022-06-19 Thread Thiago Macieira
On Sunday, 19 June 2022 14:29:33 PDT Chris Benesch wrote:
> Build OpenSSL 3 and add its install directory lib/pkgconfig to
> PKG_CONFIG_PATH and choose -openssl-linked as one of the config
> parameters.  If you can get through configure, it should build.

OpenSSL 3 isn't supported in 5.15.

Use the very latest release from 1.1, but no older and no newer.

Then there's the question of whether you want to ship OpenSSL libraries with 
your product.  If you do, then you must also keep an eye to OpenSSL security 
advisories and make proper and timely updates to your release. Be prepared to 
make new builds and release to customers once per month. If you can't sustain 
this rate, then don't ship OpenSSL.

You don't have to do it: the default build doesn't link to OpenSSL, but 
instead tries to find it at runtime and dlopens() it. That places the burden of 
providing OpenSSL and keeping it up to date on your user, not you. If they 
choose to be vulnerable by choice or by ignorance, it's not your fault.

If you choose this route, make sure your application works properly when 
OpenSSL 1.1 is missing. By "properly", I mean "doesn't crash left and right". 
Please make sure that it is not silently falling back to unencrypted 
connections where encrypted were required. If your application requires 
encrypted connections to work at all, then display a dialog with a link to 
documentation on how to install OpenSSL.

PS: OpenSSL is the most visible and most important library when it comes to 
patching security vulnerabilities, but is not the only one. You should do the 
same for ALL libraries you ship with your application, and that includes ALL 
the libraries that are bundled inside Qt's source. For example, the just-
released Qt 5.15.5-LTS includes a vulnerable version of zlib, so you should 
patch it.

Better yet, don't use bundled libraries.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Cloud Software Architect - Intel DCAI Cloud Engineering



___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest