So did you do a git pull on your existing ti-linux-kernel-dev project? If you did, then it won’t build. To see the error, you have to scroll back, sometime you have to scroll back a lot to see the error. If the build was successful, you will see the deploy folder update successfully. The reason you don’t see the error at the end is because of the parallel build. The builder launches several threads and when one thread has an error, the other threads continue until they finish.
Regards, John > On Jul 1, 2016, at 2:34 PM, Greg Wilson-Lindberg <gl4jal...@gmail.com> wrote: > > Hi Robert, > > As I said above, I found a backup of the ti-linux-kernel-dev directory from > when I built my working kernel. I've tried to build it now on three systems, > two x86 systems, one Kubuntu 12-04, one Kubuntu 14-04, and the third system, > an OMAP-UEVM running a debian build of yours. On two of them the build > doesn't finish (the 14-04 x86 and the UEVM), it compiles most everything, > does links of some builtins.o files and then just stops without error > messages and without creating the final kernel or the tar archives in the > deploy directory. The third system finishes, the kernel boots, but it fails > to read a max1363 ADC that is connected to the I2C bus. The I2C bus is > enabled in the config, as is IIO and the ADC. > > I had originally built this kernel on a Kubuntu 12-04 system last August. Now > I can't get it to compile a fully working system. On at least the UEVM > system, if I run the build_kernel.sh script again, it tries to download new > code and fails because the tags from back then are all bad and it can't check > the newest version out. > > I'm about at my wits end, I need to be able to build a fully working kernel, > and have in the past, but now it doesn't work. I've verified that the config > file that I'm using to compile the various kernel builds matches the one from > the working kernel. I've verified that the dtb is the correct one, either the > original working one, or a new one built with the kernel. > > Any suggestions that you may have would be greatly appreciated. > > Regards, > > -- > For more options, visit http://beagleboard.org/discuss > <http://beagleboard.org/discuss> > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beagleboard+unsubscr...@googlegroups.com > <mailto:beagleboard+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/ddab4a90-9c32-497b-8f61-7213189923d4%40googlegroups.com > > <https://groups.google.com/d/msgid/beagleboard/ddab4a90-9c32-497b-8f61-7213189923d4%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/EB383BF9-75FD-4080-AEF4-61D7C32FB6A1%40gmail.com. For more options, visit https://groups.google.com/d/optout.
