On 64-bit OSs compiling Mupen64bit requires more swap #3576
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
On 64-bit OSs compiling Mupen64bit requires more swap Compiling on 64bit requires more memory
GeorgeMcMullen
force-pushed
the
mupen64bit
branch
from
504bad7
to
fd4374a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
A little while ago, I had created a pull request (#3522), but then I had lost track of the status. Relevant info is as follows:
In my testing on 64bit OSes, I found that mupen64bit would throw errors while compiling. After further investigation, I found that just increasing swap when on a 64-bit system would alleviate the issue. This is similar to how more swap is needed when compiling MAME on a 64-bit platform.
On my original pull request, I recently discovered that it was suggested I squash commits. It had been quite some time though since my original commits so my attempts at squashing them grew messier and messier. So I reset my branch and recommitted the changes. Unfortunately, in doing so, my original pull request was closed (since there were no changes after my branch was reset). So I've created a new pull request.
Apologies for the confusion and for letting my original pull request languish for so long.