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

Update crosstool-ng 1.25.0 -> 1.26.0 #816

Open
VirtualTim opened this issue Feb 23, 2024 · 2 comments · May be fixed by #828
Open

Update crosstool-ng 1.25.0 -> 1.26.0 #816

VirtualTim opened this issue Feb 23, 2024 · 2 comments · May be fixed by #828

Comments

@VirtualTim
Copy link

crosstool-ng 1.26.0 was released September 2023 - https://github.com/crosstool-ng/crosstool-ng/releases.

It looks like the process could be as simple as updating CT_VERSION, and regenerating all the crosstool-ng.configs.
The release notes mention:

If you're updating an existing configuration from crosstool-ng 1.25.0 make sure to use ct-ng upgradeconfig to pick up some internal changes.

@VirtualTim
Copy link
Author

@bensuperpc it looks like you've been handling the previous crosstool updates.
I'm willing to attempt this update, would you be able to guide me through the process?

@bensuperpc
Copy link
Member

bensuperpc commented Mar 27, 2024

You have several choices for the update, some images were updated with the "ct-ng upgradeconfig" command and check if everything looks good in the crosstool-ng menu, for others, I took one of the examples provided by crosstool-ng and made the modifications to match the old version (like enable some libs, CROSS_TRIPLE etc...) in the crosstool-ng menu, ct-ng upgrade config doesn't work very well sometimes.

Afterwards there may be some debian packages or commands that have changed, sometimes it is necessary to make some changes in the dockcross-base.

After building the docker image, then test by building a program (like python, stockfish etc... like in CI) and launching it on the target (like on Raspberry Pi 4 with Raspberry PI OS or Ubuntu), if you don't have the hardware, you can use QEMU with an image of a system (Risc-v ect...).

Here is an example to add an image, but the beginning will help you:

https://github.com/dockcross/dockcross/blob/master/CONTRIBUTING.md

@VirtualTim VirtualTim linked a pull request Apr 11, 2024 that will close this issue
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 a pull request may close this issue.

2 participants