On 8/1/23 10:15, Till Wegmüller wrote:
Hi Stephan
Your idea is sound. The pkg file next to a Makefile in the same
directory indicate a component.
The pkg file contains a json with all required packages so the grep
trick works, you can also use jq to filter out the json syntax cleanly.
The rebuild is one thing we should do yes, so if you can bump the
version numbers I can run it through CI.
It's a good idea! keep going.
-Till
On 01.08.23 07:40, Stephan Althaus wrote:
Hello!
We are stumbling over some faults with regard to the GCC Version change.
i had the idea of a half-automation of these steps:
- find packages that need a rebuild
- patch Makefile and pkg5
- git checkout -b , git add, git commit, etc..
How to identify the appropriate packages ?
When i select packages by " (grep gcc-7-runtime" pkg) == true " i get
some candidates..
-> Do we have to rebuild all other packages that have been build
prior to the commit "switch default gcc to version 10"
because of the "ABI change" ??
That would be >200 packages..
Or is my idea "stupid" in the end?
Regards,
Stephan
_______________________________________________
oi-dev mailing list
[email protected]
https://openindiana.org/mailman/listinfo/oi-dev
_______________________________________________
oi-dev mailing list
[email protected]
https://openindiana.org/mailman/listinfo/oi-dev
Hello!
Thanks for your response!
The one thing left open in my mind,
does the "ABI change" indeed change the function calls in a way,
so that in situations like
someprog_compiled_with_gcc10 -> somelib-compiled-with-gcc7->func() ->
somelib-compiled-with-gcc10->func() ...
or-the-like are broken?
In this case we have to rebuild all packages that have been build before
december-2022.
Regards,
Stephan
_______________________________________________
oi-dev mailing list
[email protected]
https://openindiana.org/mailman/listinfo/oi-dev
