Skip to content

Fix the build broken of examples/llm_manual used in llm/getting-started.md #12095

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

DamonFool
Copy link

Hi all,

While I was following https://docs.pytorch.org/executorch/main/llm/getting-started , the cmake build was broken due to the following error:

CMake Error at third-party/executorch/tools/cmake/common/preset.cmake:122 (message):
  Use of 'EXECUTORCH_BUILD_EXTENSION_MODULE' requires
  'EXECUTORCH_BUILD_EXTENSION_FLAT_TENSOR'
Call Stack (most recent call first):
  third-party/executorch/tools/cmake/preset/default.cmake:300 (check_required_options_on)
  third-party/executorch/CMakeLists.txt:87 (include)

It would be better to fix it.
Thanks.

CMake Error at third-party/executorch/tools/cmake/common/preset.cmake:122 (message):
  Use of 'EXECUTORCH_BUILD_EXTENSION_MODULE' requires
  'EXECUTORCH_BUILD_EXTENSION_FLAT_TENSOR'
Call Stack (most recent call first):
  third-party/executorch/tools/cmake/preset/default.cmake:300 (check_required_options_on)
  third-party/executorch/CMakeLists.txt:87 (include)
Copy link

pytorch-bot bot commented Jun 28, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/12095

Note: Links to docs will display an error until the docs builds have been completed.

❌ 2 New Failures

As of commit d1a3fa6 with merge base db8ef6b (image):

NEW FAILURES - The following jobs have failed:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@facebook-github-bot
Copy link
Contributor

Hi @DamonFool!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

Copy link

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@DamonFool
Copy link
Author

I had signed the CLA just now.

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jun 28, 2025
@DamonFool
Copy link
Author

The two failures should not be related to this change.
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants