[Bug 2259590] F40FailsToInstall: slic3r

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/show_bug.cgi?id=2259590

Jonathan Wakely <jwakely@xxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jwakely@xxxxxxxxxx



--- Comment #1 from Jonathan Wakely <jwakely@xxxxxxxxxx> ---
This wasn't rebuilt for the new boost because the package FTBFS with gcc-14:

/usr/include/c++/14/x86_64-redhat-linux/bits/c++config.h:2509:2: warning:
#warning "__STRICT_ANSI__ seems to have been undefined; this is not supported"
[-Wcpp]
 2509 | #warning "__STRICT_ANSI__ seems to have been undefined; this is not
supported"
      |  ^~~~~~~
In file included from /usr/include/c++/14/bits/chrono.h:39,
                 from /usr/include/c++/14/mutex:43,
                 from /usr/include/boost/system/detail/mutex.hpp:68,
                 from
/usr/include/boost/system/detail/error_category_impl.hpp:101,
                 from /usr/include/boost/system/errc.hpp:17,
                 from /usr/include/boost/system/system_error.hpp:9,
                 from /usr/include/boost/thread/exceptions.hpp:22,
                 from /usr/include/boost/thread/pthread/thread_data.hpp:10,
                 from /usr/include/boost/thread/thread_only.hpp:17,
                 from /usr/include/boost/thread/thread.hpp:12,
                 from /usr/include/boost/thread.hpp:13,
                 from src/libslic3r/libslic3r.h:11:
/usr/include/c++/14/limits:2100:30: error: exponent has no digits
 2100 |         return __extension__ 0x1.0p-16382Q;
      |                              ^~~~~~


The warning says what the problem is, and indeed the build.log shows that the
package uses -U__STRICT_ANSI__ '-std=c++11' 

DO. NOT. DO. THIS.

__STRICT_ANSI__ is an internal macro defined and used by the compiler, it is
NOT a macro that users can define/undefined in their own code. Doing so
completely breaks the C++ standard library headers.

If you want non-strict C++11 then just use -std=gnu++11 instead of -std=c++11

Asking the compiler to be strict then undefining the macro that says it's being
strict is just wrong. Please get this fixed upstream.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2259590

Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202259590%23c1
--
_______________________________________________
perl-devel mailing list -- perl-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to perl-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/perl-devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Legacy Announce]     [Fedora PHP Devel]     [Kernel Devel]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite Information]

  Powered by Linux