Summary: | ports-mgmt/poudriere: reason for failure becomes bad_C++_code by outputting Mk/Scripts/ports_env.sh to the log | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Tatsuki Makino <tatsuki_makino> |
Component: | Individual Port(s) | Assignee: | Bryan Drewery <bdrewery> |
Status: | New --- | ||
Severity: | Affects Only Me | CC: | ndowens04 |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(bdrewery) |
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any | ||
See Also: |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227158 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230759 |
Description
Tatsuki Makino
2018-12-02 04:28:07 UTC
(In reply to Tatsuki Makino from comment #0) It's "normal" I have that in poudriere in mine as well (13-current) and it was like that in older versions and builds don't fail because of it I do not know when it will be, but 13.x-RELEASE returns CC_OUTPUT_xxxxxxxx_xxxxxxxx=error: invalid value 'c++2?' in '-std=c++2?'. If the reason for the build failure is a patch (or reasons to appear after reason="bad_C++_code"), poudriere reports the reason bad_C++_code. |