Skip to content

Config refactor#137

Merged
TheMrIron2 merged 17 commits into
masterfrom
config-refactor
Jun 7, 2026
Merged

Config refactor#137
TheMrIron2 merged 17 commits into
masterfrom
config-refactor

Conversation

@TheMrIron2
Copy link
Copy Markdown
Contributor

config refactor

Moved from #135 - refactors config.guess and config.sub retrieval.

Attempts to contact Savannah for latest config, given timeout CONFIG_TIMEOUT (default: 15s). If successful, use Savannah; if not, use local copy to avoid build stall or crash.
This logic has additionally been moved to a separate script, get-config-scripts.sh, in order to unify the logic. There's room for a faster implementation, but this improves the stability of the build process.

TheMrIron2 and others added 17 commits June 7, 2026 10:13
Replaced a bad path. On modern macOS, both `TARGET_OS_MAC` and `__APPLE__` can be visible. So the old "no fdopen()” path runs and the macro replaces fdopen() with NULL and corrupts it.
Same behaviour as ps3libraries - check Savannah, and if not, fall back on local copy
sys/utime.h declares utimbuf using time_t, but does not include a header that declares time_t. This breaks libraries that include <utime.h> directly, eg libnfs.
Include <sys/types.h> earlier so the header is self-contained.
This reverts commit 9475164.
@TheMrIron2 TheMrIron2 marked this pull request as ready for review June 7, 2026 11:07
@TheMrIron2 TheMrIron2 requested a review from bucanero June 7, 2026 11:07
@TheMrIron2 TheMrIron2 merged commit 14add94 into master Jun 7, 2026
2 checks passed
@TheMrIron2 TheMrIron2 deleted the config-refactor branch June 7, 2026 11:11
@zeldin
Copy link
Copy Markdown
Member

zeldin commented Jun 7, 2026

Ugh. The commit message of the pushed commit is a mess. Also you included changes to gcc-7.2.0-PS3.patch which should not be there (at least not in this PR).

Please give more than 5 minutes of time for peer reviews next time...

@zeldin
Copy link
Copy Markdown
Member

zeldin commented Jun 7, 2026

The change to check-python.sh and several of the scripts/ changes seem unrelated as well.

This was not a good merge.

@TheMrIron2
Copy link
Copy Markdown
Contributor Author

Sorry Marcus, I shouldn’t have let that through. What do you suggest we do?

@bucanero
Copy link
Copy Markdown
Contributor

bucanero commented Jun 7, 2026

Please give more than 5 minutes of time for peer reviews next time...

Sorry, my bad, 🙏 I missed some of the context from the previous PR thread. Next time if there's an ongoing thread I'll ping the original reviewers so things can be followed-up in a better way.

@zeldin
Copy link
Copy Markdown
Member

zeldin commented Jun 7, 2026

Sorry Marcus, I shouldn’t have let that through. What do you suggest we do?

Normally I'd say back it out with a force push, but it looks like those are blocked, and I can't figure out how to unblock them for admins only...

So I guess we'll just have to live with it. But please do be more careful next time.

@zeldin
Copy link
Copy Markdown
Member

zeldin commented Jun 7, 2026

I'm going to revert the change to gcc-7.2.0-PS3.patch though. That file should always contain the current state of the master branch of ps3dev/gcc-7.2.0-PS3 repo, which it doesn't do right now.

@bucanero
Copy link
Copy Markdown
Contributor

bucanero commented Jun 7, 2026

Sorry Marcus, I shouldn’t have let that through. What do you suggest we do?

Normally I'd say back it out with a force push, but it looks like those are blocked, and I can't figure out how to unblock them for admins only...

So I guess we'll just have to live with it. But please do be more careful next time.

@zeldin I think you should be able to enable force pushes for specific users under the repo settings, check here:
https://github.com/ps3dev/ps3toolchain/settings/branch_protection_rules/78077902

I see an option at the end Allow force pushes, and then an option Everyone / Specific users. I think that's where you could define some granular access to force pushes.

@zeldin
Copy link
Copy Markdown
Member

zeldin commented Jun 7, 2026

@bucanero Ah, sneaky. Before you click the checkbox it just says "Rules applied to everyone including administrators", so I didn't check the box since I didn't want it to apply to everyone...

@zeldin
Copy link
Copy Markdown
Member

zeldin commented Jun 7, 2026

Ok, force pushed.

@TheMrIron2 You can now restore your branch and clean it up (remove unrelated stuff, do a squash to fix up the commit message). I don't know if this PR can be reactivated or if you need to make a new one.

Once the branch has been reviewed and merged again, you can rebase your other branch on the new master and it should remove everything already merged, so you are left with only stuff belonging to the other PR.

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.

3 participants