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

Pr 4380 spidermonkey check #4382

Closed
wants to merge 3 commits into from
Closed

Pr 4380 spidermonkey check #4382

wants to merge 3 commits into from

Conversation

nickva
Copy link
Contributor

@nickva nickva commented Jan 18, 2023

THIS IS A TEST PR ONLY. The original is #4380 where we wondering why Jenkins wasn't picking up the Jenkinsfile.pr changes. Making a new PR from a local branch seems to have solved the issue around modifying Jenkinsfile.pr.

(Authored-by: PÁLI Gábor János pgj)

Perhaps one of the committers can split up the ./configure --skip-deps --spidermonkey-version 78 into a separate PR.

The `configure` script does not check whether SpiderMonkey
actually exists at the presumed location.  This may go wrong when
the user has a version different from the default one.  The
mistake is spotted only in build time, indirectly, via missing
header files.  That is too late and it may not be evident for the
user what the problem is.

Add a user-friendly safeguard for Unix-like systems to prevent
this from happening.
@nickva
Copy link
Contributor Author

nickva commented Jan 18, 2023

Closing PR now that the check is complete.

Pulled out the Jenkinsfile.pr bit into a separate PR #4383 to help the original one make progress.

@nickva nickva closed this Jan 18, 2023
@nickva nickva deleted the pr-4380-spidermonkey-check branch January 18, 2023 03:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants