Skip to content

wasi-sdk/25 package update - #36444

Merged
debasishbsws merged 6 commits into
mainfrom
wolfictl-37c31b06-9c32-489e-b0a6-30563f55c91f
Jan 2, 2025
Merged

debasishbsws merged 6 commits into
mainfrom
wolfictl-37c31b06-9c32-489e-b0a6-30563f55c91f

Conversation

@octo-sts

@octo-sts octo-sts Bot commented Dec 12, 2024

Copy link
Copy Markdown
Contributor

@octo-sts octo-sts Bot added request-version-update request for a newer version of a package automated pr labels Dec 12, 2024
@octo-sts

octo-sts Bot commented Dec 12, 2024

Copy link
Copy Markdown
Contributor Author

Gen AI suggestions to solve the build error:

• Detected Error: "cp: can't stat '/home/build/melange-out/wasi-sdk/usr/lib/clang/18/lib/wasi/libclang_rt.builtins-wasm32.a': No such file or directory"

• Error Category: Path/Version Mismatch

• Failure Point: Subpackage pipeline for wasi-sdk-libclang-rt-builtins during file copy operation

• Root Cause Analysis: The error occurs because the script is trying to copy a file from a path that uses LLVM version 18, but the build is actually using LLVM version 19 (as seen in the build artifacts)

• Suggested Fix: Update the path in the subpackage pipeline to use version 19 instead of 18:

subpackages:
  - name: wasi-sdk-libclang-rt-builtins
    pipeline:
      - runs: |
          mkdir -p ${{targets.subpkgdir}}/usr/lib/clang/lib/wasi
          # Update path from 18 to 19
          cp ${{targets.destdir}}/usr/lib/clang/19/lib/wasi/libclang_rt.builtins-wasm32.a ${{targets.subpkgdir}}/usr/lib/clang/lib/wasi/

• Explanation: The build artifacts clearly show that LLVM version 19 is being used (visible in the file listing), but the subpackage pipeline is trying to access version 18. Updating the path to match the actual version will allow the file copy to succeed.

• Additional Notes:

  • The vars.llvm-vers is set to 19 in the configuration
  • The build artifacts show all files are under clang/19/
  • This type of version mismatch is common when updating LLVM/Clang versions
  • Consider making the version reference dynamic using the vars.llvm-vers variable

• References:

Signed-off-by: wolfi-bot <121097084+wolfi-bot@users.noreply.github.com>
@mamccorm
mamccorm force-pushed the wolfictl-37c31b06-9c32-489e-b0a6-30563f55c91f branch from 41cbbe5 to 182a735 Compare December 12, 2024 01:33
@octo-sts

octo-sts Bot commented Dec 12, 2024

Copy link
Copy Markdown
Contributor Author

Gen AI suggestions to solve the build error:

• Detected Error: "cp: can't stat '/home/build/melange-out/wasi-sdk/usr/lib/clang/18/lib/wasi/libclang_rt.builtins-wasm32.a': No such file or directory"

• Error Category: Configuration

• Failure Point: Subpackage pipeline for wasi-sdk-libclang-rt-builtins during file copy operation

• Root Cause Analysis: The error occurs because the path to libclang_rt.builtins-wasm32.a references LLVM 18, but the build is actually using LLVM 19 as specified in the vars.llvm-vers variable.

• Suggested Fix: Update the path in the subpackage pipeline to use the correct LLVM version:

  - name: wasi-sdk-libclang-rt-builtins
    pipeline:
      - runs: |
          mkdir -p ${{targets.subpkgdir}}/usr/lib/clang/lib/wasi
          # Update path to use LLVM 19 instead of 18
          cp ${{targets.destdir}}/usr/lib/clang/19/lib/wasi/libclang_rt.builtins-wasm32.a ${{targets.subpkgdir}}/usr/lib/clang/lib/wasi/

• Explanation: The build error occurs because the subpackage is looking for the runtime library in the LLVM 18 directory, but the package is built using LLVM 19 as specified in the vars section. Updating the path to reference version 19 will align with the actual build configuration.

• Additional Notes:

  • The file listing in the error output confirms the presence of the library under the clang/19 directory structure
  • This type of version mismatch is common when updating LLVM versions in the build
  • The fix ensures consistency between the declared LLVM version and the filesystem paths

• References:

Signed-off-by: Debasish Biswas <debasishbsws.dev@gmail.com>
@debasishbsws debasishbsws self-assigned this Dec 30, 2024
@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 30, 2024
Signed-off-by: Debasish Biswas <debasishbsws.dev@gmail.com>
Signed-off-by: Debasish Biswas <debasishbsws.dev@gmail.com>
@debasishbsws

Copy link
Copy Markdown
Member

This should get fixed and pass the test now.

@debasishbsws
debasishbsws requested a review from a team December 30, 2024 18:31
@debasishbsws
debasishbsws enabled auto-merge (squash) December 30, 2024 18:31
Signed-off-by: Debasish Biswas <debasishbsws.dev@gmail.com>
Signed-off-by: Debasish Biswas <debasishbsws.dev@gmail.com>
@debasishbsws

Copy link
Copy Markdown
Member

All the downstream package of wasi-sdk epoch has been bumped

@debasishbsws
debasishbsws merged commit 780a871 into main Jan 2, 2025
@debasishbsws
debasishbsws deleted the wolfictl-37c31b06-9c32-489e-b0a6-30563f55c91f branch January 2, 2025 13:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated pr bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. manual/review-needed request-version-update request for a newer version of a package

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants