[Development] Qt 5.6.0-rc build issues on CentOS 6.7 x86_64 with g++

[Helio Chissini de Castro]

Hello again

The packages built on copr repository IS 5.6.0rc and is the reference that
we use to upstream in Fedora when reach final.

This is the proper repository:
https://copr.fedorainfracloud.org/coprs/g/kdesig/Qt5/

This is the repository to add on Yum
https://copr.fedorainfracloud.org/coprs/g/kdesig/Qt5/repo/epel-6/heliocastro-Qt5-epel-6.repo

This are the effective packages:
https://copr.fedorainfracloud.org/coprs/g/kdesig/Qt5/packages/

[]'s Helio

On Fri, Mar 4, 2016 at 9:47 AM, Heikkinen Jani <
jani.heikkinen at theqtcompany.com> wrote:

> >>Workaround: do not use the convenience qt-everywhere-* tarball. Build
> each
> >>module independently.
> >>
> >>Ossi: have there been changes to rpath or rpath-link handling recently?
> We
> >>need to bring it back.
>
> There is some fixes for src packages coming in after RC, see
>
> https://codereview.qt-project.org/#/c/150517/
> https://codereview.qt-project.org/#/c/150232/
> https://codereview.qt-project.org/#/c/151015/
>
> (+ c++98 related ones in https://codereview.qt-project.org/#/c/151328/ )
>
> Those all are now in qt5.git but we don't have re-created src packages for
> testing yet :(
>
> Br,
> Jani
>
>
> >>-----Original Message-----
> >>From: Development [mailto:development-
> >>bounces+jani.heikkinen=theqtcompany.com at qt-project.org] On Behalf Of
> >>Thiago Macieira
> >>Sent: 4. maaliskuuta 2016 9:28
> >>To: development at qt-project.org
> >>Subject: Re: [Development] Qt 5.6.0-rc build issues on CentOS 6.7 x86_64
> with
> >>g++
> >>
> >>On sexta-feira, 4 de março de 2016 07:07:00 PST Walter Stefan wrote:
> >>> I have done a clean build.
> >>>
> >>> Where can we address this issue?
> >>
> >>I've managed to reproduce this issue now. It only happens with the old
> bfd
> >>linker (ld.bfd). Gold appears unaffected.
> >>
> >>Workaround: do not use the convenience qt-everywhere-* tarball. Build
> each
> >>module independently.
> >>
> >>Ossi: have there been changes to rpath or rpath-link handling recently?
> We
> >>need to bring it back.
> >>
> >>The command-line for linking the example was:
> >>
> >>g++ -Wl,-O1 -fuse-ld=bfd -Wl,--enable-new-dtags -Wl,-z,origin
> -Wl,-rpath,\
> >>$ORIGIN/../../../lib -o annotatedurl .obj/main.o .obj/mainwindow.o .obj/
> >>annotatedurl.o .obj/moc_mainwindow.o .obj/moc_annotatedurl.o -L/tmp/qt-
> >>build/
> >>qtbase/lib -lQt5Widgets.t -lQt5Gui.t -L/tmp/qt-build/qtconnectivity/lib -
> >>lQt5Nfc.t -lQt5Core.t -lGL -lpthread
> >>
> >>Every Qt module path in an -L option needs to be repeated with
> -Wl,-rpath-
> >>link,
> >>
> >>--
> >>Thiago Macieira - thiago.macieira (AT) intel.com
> >>  Software Architect - Intel Open Source Technology Center
> >>
> >>_______________________________________________
> >>Development mailing list
> >>Development at qt-project.org
> >>http://lists.qt-project.org/mailman/listinfo/development
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160304/39093b5c/attachment.html>