Hi Patrick
Yes i rebuild the Compilers after every coreboot build. So the steps where
1.) Git bisect start
2.) Git bisect good <commit>
3.) Git bisect bad <commit>
4.) Make crossgcc-i386
5.) Make
6.) Check the coreboot Image live on physical alix
7.) Make clean
8.) Make crossgcc-clean
9.) Git bisect bad/good
10.) Start over at step 4 again and so on… until found breaking commit.
Gesendet von Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 für Windows 10
Von: Patrick Georgimailto:pgeorgi@google.com Gesendet: Freitag, 8. April 2016 22:05 An: Reto Rayenmailto:retorayen@hotmail.com Cc: coreboot@coreboot.orgmailto:coreboot@coreboot.org Betreff: Re: [coreboot] Alix 2d13 coreboot breaking source
Just to clarify: Did you rebuild the compilers after applying that commit? It doesn't touch anything that ends up affecting the coreboot binaries with a given toolchain.
2016-04-08 21:47 GMT+02:00 Reto Rayen retorayen@hotmail.com:
Hi guys
Finally i found out, which git commit broke coreboot to build for a «Alix 2d13». I used «git bisect» recommended by «PaulePanther» in october 2015 to identify the commit. A doc about the different git commits and their results can be found here: https://file.youngsolutions.ch/index.php/s/g2cixjqepvTwJhR
Commit which breaks coreboot for successfull buid: 53c388fe6dfb4fc4ffcee6c58345d353c6ec33bf (crossgcc: Update toolchain)
So what the next steps, to get coreboot working with the latest build for Alix 2d13?
Thank your guys, for your help so far.
Kind regards
Reto Rayen
-- coreboot mailing list: coreboot@coreboot.org https://www.coreboot.org/mailman/listinfo/coreboot
-- Google Germany GmbH, ABC-Str. 19, 20354 Hamburg Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle