-
Notifications
You must be signed in to change notification settings - Fork 14
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
glibc checkoutScript fails on rebuild #180
Comments
There are not many reasons why the Anyway, the real culprit is the patch class that cannot cope with the fact when some or all of it's modifications were reverted. Plus the fact that the |
I did neither of those things. I also keep deleting the source directory I mentioned above. However I do build 2 glibcs, one for the gcc-native to look at during compilation and one for the target rootfs, I have yet to find out how to tell bob to reuse the first glibc. |
Each applied patch is tracked individually. This has the benefit of being able to handle situations where multiple patches touch the same file. Also remove the check if the patch is still applied. This proved to be unreliable, especially if multiple patches touch the same file. We now solely rely on the tracked applied patches and compare them to the desired ones. If they match, the class will assume the patch is still applied. Fixes BobBuildTool#55. Fixes BobBuildTool#180.
I am building the glibc recipe for my target rootfs, but everytime I run
bob build ...
again it fails with the following error. For now I'm deletingwork/libs/glibc/src
as a workaround, which does cause a new checkout, but not a new build.My guess is bob tries to run the checkoutScript again on sources where the checkoutScript was already executed?
The text was updated successfully, but these errors were encountered: