You should report upstream about the problem and fix code.
вс, 31 мая 2020 г., 12:49 <ycollette.nos...@free.fr>:
> Hello again !
>
> I've got a new problem: a gcc flags trigger a problem during generation of
> an object file.
> The application is based on Qt5. The problematic file is produced from a
> moc generated file.
> The flag in question: -fcf-protection
>
> The solution I found is to send a custom set of flags to qmake.
>
> What is the best approach to remove a flags from a rpm macro variable ?
>
>
> # optflags %{__global_compiler_flags} -m64 -mtune=generic
> -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
> # -fcf-protection produce an error in an object generatoin ...
>
> qmake-qt5 Jamulus.pro \
> QMAKE_CFLAGS_DEBUG="%{__global_compiler_flags} -m64
> -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection" \
> QMAKE_CFLAGS_RELEASE="%{__global_compiler_flags} -m64
> -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection" \
> QMAKE_CXXFLAGS_DEBUG="%{__global_compiler_flags} -m64
> -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection" \
> QMAKE_CXXFLAGS_RELEASE="%{__global_compiler_flags} -m64
> -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection" \
> CONFIG+=opus_shared_lib
>
> %make_build VERBOSE=1
>
>
>
> ----- Mail original -----
> De: "ycollette nospam" <ycollette.nos...@free.fr>
> À: "Development discussions related to Fedora" <
> devel@lists.fedoraproject.org>
> Envoyé: Samedi 30 Mai 2020 21:58:55
> Objet: Re: Packaging problem
>
> OK, thanks, it works with %{qmake_qt5} but not with %_qt5_qmake ...
>
> Thanks a lot
>
> I see that qmake_qt5 macro call _qt5_qmake with some flags ...
> I found the macro via rpm --showrc | grep qmake and I choose the wrong
> result.
>
>
> ----- Mail original -----
> De: "Vascom" <vasc...@gmail.com>
> À: "Development discussions related to Fedora" <
> devel@lists.fedoraproject.org>
> Envoyé: Samedi 30 Mai 2020 21:49:46
> Objet: Re: Packaging problem
>
> First you should use this macro %{qmake_qt5} and remove %{set_build_flags}.
>
> And show your spec or give srpm.
>
> сб, 30 мая 2020 г. в 22:21, <ycollette.nos...@free.fr>:
> >
> > Hello,
> >
> > I've got a problem with a package.
> > I am trying to clean up a spec file before sending it to review and I've
> got an error:
> >
> > erreur : Empty %files file
> /home/artelys/rpmbuild/BUILD/jamulus-c6b6e3ab02d7ec1e93edeeb8042a89a561924826/debugsourcefiles.list
> >
> > The code is Qt-5 / c++. It's an application which allows to perform live
> rehearsale via an internet connection.
> >
> > On the gcc / c++ command line, I can see the -g flags.
> >
> > The build section:
> >
> > %{set_build_flags}
> >
> > %_qt5_qmake Jamulus.pro CONFIG+=opus_shared_lib
> >
> > %make_build VERBOSE=1
> >
> > The install section (the qmake file defines no install rule so I must
> install everything manually):
> >
> > %__install -m 755 -d %{buildroot}/%{_bindir}/
> > %__install -m 755 Jamulus %{buildroot}%{_bindir}/jamulus
> >
> > %__install -m 755 -d %{buildroot}/%{_datadir}/applications/
> > %__install -m 644 distributions/jamulus.desktop
> %{buildroot}%{_datadir}/applications/
> >
> > %__install -m 755 -d %{buildroot}/%{_datadir}/pixmaps/
> > %__install -m 644 distributions/jamulus.png
> %{buildroot}%{_datadir}/pixmaps/
> >
> > How can I build the debug part of the package ?
> >
> > The only solution I've found is to add:
> >
> > %global debug_package %{nil}
> >
> > At the beginning of the spec file ...
> >
> > Best regards,
> >
> > YC
> > _______________________________________________
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
