Re: Prototyping new packages

2010-04-22 Thread Matthew Burgess
On Fri, 16 Apr 2010 11:31:05 -0500, Bruce Dubbs wrote: > I didn't see that fix in 2.6.34-rc4, but it is in 2.6.34-rc4-git4 and > 2.6.34-rc4-next-20100415 It's now also in the 2.6.32.x and 2.6.33.x stable trees after I submitted it to the stable mailing list. Commit message at http://www.spinics.

Re: Prototyping new packages

2010-04-18 Thread Matthew Burgess
On 18/04/2010 16:30, Bruce Dubbs wrote: > Matthew Burgess wrote: >> On 16/04/2010 07:03, Bruce Dubbs wrote: >>> I've been working with some new packages: >>> >>> GCC-4.5.0 >> >> Note that this causes a test failure in Bison-2.4.2. It's already been >> reported at >> http://lists.gnu.org/archive/ht

Re: Prototyping new packages

2010-04-18 Thread Bruce Dubbs
Matthew Burgess wrote: > On 16/04/2010 07:03, Bruce Dubbs wrote: >> I've been working with some new packages: >> >> GCC-4.5.0 > > Note that this causes a test failure in Bison-2.4.2. It's already been > reported at > http://lists.gnu.org/archive/html/bug-bison/2010-03/msg00030.html with a > pa

Re: Prototyping new packages

2010-04-18 Thread Matthew Burgess
On 16/04/2010 07:03, Bruce Dubbs wrote: > I've been working with some new packages: > > GCC-4.5.0 Note that this causes a test failure in Bison-2.4.2. It's already been reported at http://lists.gnu.org/archive/html/bug-bison/2010-03/msg00030.html with a patch attached to the reply there. Rega

Re: Prototyping new packages

2010-04-16 Thread Bruce Dubbs
Matthew Burgess wrote: > On 16/04/2010 17:31, Bruce Dubbs wrote: >> I'm not sure the fix is fixing the root of the problem or masking it, >> but that's for the driver developers to decide. I didn't see that fix >> in 2.6.34-rc4, but it is in 2.6.34-rc4-git4 and 2.6.34-rc4-next-20100415 > > I cou

Re: Prototyping new packages

2010-04-16 Thread Matthew Burgess
On 16/04/2010 17:31, Bruce Dubbs wrote: > William Immendorf wrote: >> On Fri, Apr 16, 2010 at 6:48 AM, William Immendorf >> wrote: >>> I think you should just be patient, Bruce. Wait for 2.6.33.3 to come >>> out, and hopefully your system will boot up again. >> Or if you are impatient, try using

Re: Prototyping new packages

2010-04-16 Thread Bruce Dubbs
William Immendorf wrote: > On Fri, Apr 16, 2010 at 6:48 AM, William Immendorf > wrote: >> I think you should just be patient, Bruce. Wait for 2.6.33.3 to come >> out, and hopefully your system will boot up again. > Or if you are impatient, try using the attached patch. > > I think it fixes the se

Re: Prototyping new packages

2010-04-16 Thread William Immendorf
On Fri, Apr 16, 2010 at 6:48 AM, William Immendorf wrote: > I think you should just be patient, Bruce. Wait for 2.6.33.3 to come > out, and hopefully your system will boot up again. Or if you are impatient, try using the attached patch. I think it fixes the segfault issue. -- William Immendorf T

Re: Prototyping new packages

2010-04-16 Thread William Immendorf
On Fri, Apr 16, 2010 at 1:03 AM, Bruce Dubbs wrote: > Actually, I was able to get the new system to come up with 2.6.33.2. > When I do make defconfig && make, the system boots without finding my > ethernet card.  That's because I need the Intel e1000e driver, but the > default configuration is usi

Re: Prototyping new packages

2010-04-15 Thread Jeremy Huntwork
On Apr 16, 2010, at 2:03 AM, Bruce Dubbs wrote: > I can't recommend the 2.6.33 series for the kernel until this gets > straightened out. OTOH, this may be a gcc-4.5.0 issue. I can try > building 2.6.30.2 or 2.6.32.8 with gcc-4.5.0 and see if that is any > better. If those segfault, it's the

Prototyping new packages

2010-04-15 Thread Bruce Dubbs
I've been working with some new packages: GCC-4.5.0 Perl-5.12.0 Grep-2.6.3 Kbd-1.15.2 Linux-2.6.33.2 Psmisc-22.11 mpc-0.8.1 All seem to build with some massaging of the instructions gcc Chapter 5 (both instances) needs to add: tar -xf mpc-0.8.1.tar.gz mv mpc-0.8.1 mpc Perl Chapter 5 needs to