Skip to content
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

Add the missing LoongArch64 definition in the v8.gyp file. #47641

Closed
wants to merge 1 commit into from

Conversation

sunhaiyong1978
Copy link
Contributor

In the tools/v8_gypfiles/v8.gyp file, there is a missing definition for the LoongArch64 architecture (defined as loong64 in v8). This can lead to errors when compiling node.js that supports v8 on the LoongArch64 architecture.

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/gyp
  • @nodejs/v8-update

@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. tools Issues and PRs related to the tools directory. v8 engine Issues and PRs related to the V8 dependency. labels Apr 20, 2023
@sunhaiyong1978
Copy link
Contributor Author

Modify the title, because the check failed due to the original title being too long.

@gengjiawen gengjiawen added the request-ci Add this label to start a Jenkins CI on a PR. label Apr 21, 2023
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Apr 21, 2023
@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@sunhaiyong1978
Copy link
Contributor Author

Modify the title again, because the title check failed.

@VoltrexKeyva
Copy link
Member

Hey @sunhaiyong1978, it seems like your commit has an invalid user (basically doesn't point to you), make sure you've configured Git with the appropriate details so that you would be shown as a contributor after this gets merged.

This is generally the cause of the incorrect email being used, make sure it is set to the primary email of your GitHub account by running the following:

$ git config --global user.email "<The primary email>"

(Replace <The primary email> with the primary email of your GitHub account)

And then do a force-push.

@sunhaiyong1978
Copy link
Contributor Author

Okay, I have modified my submission email.

@debadree25 debadree25 added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. request-ci Add this label to start a Jenkins CI on a PR. labels Apr 26, 2023
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Apr 26, 2023
@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@sunhaiyong1978
Copy link
Contributor Author

I received 3 failing checks , but it seems that they are not caused by the pull request I submitted. What should I do next?

@nodejs-github-bot
Copy link
Collaborator

@targos
Copy link
Member

targos commented May 1, 2023

Landed in aa6600d

@targos targos closed this May 1, 2023
targos pushed a commit that referenced this pull request May 1, 2023
PR-URL: #47641
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
targos pushed a commit that referenced this pull request May 2, 2023
PR-URL: #47641
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
@targos targos mentioned this pull request May 2, 2023
targos pushed a commit that referenced this pull request May 3, 2023
PR-URL: #47641
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
@danielleadams danielleadams added the dont-land-on-v18.x PRs that should not land on the v18.x-staging branch and should not be released in v18.x. label Jun 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. dont-land-on-v18.x PRs that should not land on the v18.x-staging branch and should not be released in v18.x. needs-ci PRs that need a full CI run. tools Issues and PRs related to the tools directory. v8 engine Issues and PRs related to the V8 dependency.
Projects
None yet
Development

Successfully merging this pull request may close these issues.