On Tue, May 20, 2008 at 01:36:14PM +0100, rubisher wrote: > Hello, > > > Hey, > > > > Rebuilding now with gcc-4.2 (instead of gcc-4.3) and retesting > > with 2.6.26-rc3. > > > Just a short report, tbh I didn't pay attention that gcc-4.3 became the > default gcc on my unstable install: > same Kyle git tree 2.6.26-rc2 + fixed vmlinux.lds 32bit up build for d380 & > b2k with new gcc-4.3 boot well but nic failed to work (either from box ping > outside or the contrary: nothing respond)? (the same for the 2 different boxes.) Yes - we have to track down what causes the network to fail. ARP is still working correctly so I'm doubtful this is a NIC driver problem. I've posted more notes on this several weeks ago. The gcc-4.3/networking bug is a seperate issue from the bug which I original reported in this thread. hth, grant > Otoh, same src tree rebuild with gcc-4.2 works fine on the boxes without any > other chg. > > Hth, > r. > > -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
