You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, compilers and binutils are wrapped with libraries from the next stage (targetPackages), and stdenvs take all their tools from the previous stage (buildPackages). For the moment I think it's easiest to continue with that. But a super early cross attempt of mine #21268 put the wrapper in the middle stage instead.
Once libc is not special I was thinking it would be a good time to revisit such things.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:
Search for maintainers and people that previously touched the related code and @ mention them in a comment.
Issue description
Currently we don't have good support for cross compiling when we use wrapCC. We should ensure that buildPackages is always used correctly here.
/cc @Ericson2314
The text was updated successfully, but these errors were encountered: