[00:57] <simplify> (I'm new to using IRC chat, btw.) Hello, I get an error while building the Precise 12.04.4 kernel in a VM, and also on the host system (a laptop). The same error has occurred at a different (I think) file each time during the compile process. I need help, and I haven't found any solution on the web. (and I found only one person asking about an issue with these symptoms on the web.) On the laptop I am building linux-lts-
[00:57] <simplify> raring-3.8.0, and in the VM I'm building linux-lts-saucy-3.11.0. The only change I have made in the amd64 kernel configuration is specifying the location of the dsdt.aml file. Here are the applicable lines of (error) output:
[00:58] <simplify>   CC [M]  fs/xfs/xfs_ioctl32.o␤
[00:58] <simplify>   LD [M]  fs/xfs/xfs.o␤
[00:58] <simplify>   LD      fs/built-in.o␤
[00:58] <simplify> make[1]: *** [sub-make] Error 2␤
[00:58] <simplify> make[1]: Leaving directory `/home/luc/linux-lts-saucy-3.11.0'␤
[00:58] <simplify> make: *** [/home/luc/linux-lts-saucy-3.11.0/debian/stamps/stamp-build-generic] Error 2␤
[00:58] <simplify> luc@ubuntukernel:~/linux-lts-saucy-3.11.0$␤
[00:58] <simplify> Linux ubuntukernel 3.11.0-15-generic #25~precise1-Ubuntu SMP Thu Jan 30 17:39:31 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux␤
[00:58] <simplify> By the way, I followed these instructions: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
[07:47] <apw> simplify (N,BFTL), there would likely have been an error before that one ... look back for eror
[07:48] <apw> Bharat (N,BFTL), yes you should file a bug and try and describe "not responsive" in more detail
[13:34] <diwic> oookay... so I used the --no-signed-off-by-cc switch and yet git sends cc to Intel and tiwai...?!
[13:34] <rtg> diwic, --suppress-cc=all
[13:34] <diwic> rtg, right
[13:35] <diwic> rtg, I'll remember that for next time
[13:35] <rtg> I've done it a couple of times
[13:35] <diwic> the thing is, with this switch it didn't even ask. It just sent the emails
[13:35] <diwic> but actually maybe there was some sense to it after all
[13:36] <diwic> maybe tiwai didn't get htem
[13:36] <diwic> just the patch author
[13:36] <rtg> it is kind of the default workflow
[15:10] <lpwrobin> test irc
[15:31] <jsalisbury> **
[15:31] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[15:31] <jsalisbury> **
[15:57] <arges> rtg: how do we verify intel-microcode updates? just install and reboot?
[15:57] <arges> iff you have intel hardware
[15:58] <rtg> arges, lemme check on a SNB server that I have
[15:58] <arges> rtg: no hurry. just wondering how its done 
[15:58] <rtg> arges, I just load the package and look in dmesg
[15:59] <rtg> arges, there isn't anything in -proposed ?
[15:59] <arges> rtg: well i just accepted it.. so may take a bit
[16:00] <rtg> ah, well I'll just have to be patient
[16:00] <arges> : )
[16:55] <jsalisbury> ##
[16:55] <jsalisbury> ## Kernel team meeting in 5 minutes
[16:55] <jsalisbury> ##
[17:22] <rtg> rsalveti, all of the touch kernels have been refreshed with CVE updates, etc. You can find them at https://launchpad.net/~canonical-kernel-team/+archive/ppa/+packages?field.name_filter=&field.status_filter=published&field.series_filter=utopic
[17:28] <amitk> rtg: just curious, how many touch kernels do you have?
[17:28] <rtg> amitk, flo, goldfish, manta, and mako
[17:29] <amitk> rtg: these are google devices?
[17:29] <rtg> amitk, all except goldfish which is the Android emulator kernel
[17:29] <amitk> *google device codenames?
[17:30] <rtg> Nexus, Nexus 7, and Nexus 10
[17:30] <amitk> rtg: anything that is newer than 3.4?
[17:30] <rtg> nope, all are 3.4
[17:35] <amitk> rtg: any plans to support nexus 5?
[17:36] <rtg> amitk, not to my knowledge, but then I'm not really driving the platform selection either.
[17:36] <rtg> amitk, ogra_ probably has better info then I do
[17:49] <ogra_> amitk, we have a nexus5 build but dont support it officially 
[17:51] <amitk> ogra_: thx, will check it out one of these days
[17:52] <ogra_> amitk, http://2buntu.com/articles/1489/installing-ubuntu-touch-on-a-nexus-5/