> > On Tue, 18 Nov 2003, Brad Laue wrote: > > > On Tue, 2003-11-18 at 11:13, Ferris McCormick wrote: > > > On Tue, 18 Nov 2003, Mike Frysinger wrote: > > > > > > not trying to persecute non-x86 architectures, just clean up the pile of > > > ebuilds. > > > > > Understood completely. > > I started building 1.4.1 a while ago on my U60, and will repoort back on > > it for you. If it seems to work, I can do the same for you on that > > particular system for 1.5-r1 if you like. > > > > You should be aware, though, that right now really I am mostly playing > > with mozilla-firebird on my primary system (a U2), because there was > > a request for feedback for that variant of mozilla on sparc. > > OK, first part seems to work. mozilla-1.4.1 compiles without > incident on sparc (sparc64 at any rate; I have not checked for > sparc32 and probably won't since I have no use for it there, although > I might start up the build just to see if it will). With minimal > testing, from a user point of view it is indistinguishable from > 1.4-r3 (a good thing). I'll 'quickpkg' it up and start off a build > of 1.5-r1 for you. >
And, mozilla-1.5-r1 builds successfully (sparc64 U60 " 2.4.21-sparc-r1 #6 SMP") and at first glance seems to run OK (on U60 and on U2-SMP, same kernel after having been packaged and emerged.) As I said, I have mostly been testing mozilla-firebird-0.7 and will do more of that than looking at mozilla-1.5-r1. However, after an hour or so with 1.5-r1, it seems to be stable and to do what it is supposed to do. In particular, it hasn't killed X, nor has it been killed by the kernel (both of which have happened in the past). It does not fix the bug #33750 problem for me; your mileage may vary. But at this point, after raising such a fuss, I don't care about 1.4-r3 very much. (On the other hand, I didn't know you wanted off-brand architecture testing for 1.5-r1 :-).) I'll let you know about SS20 (sparc32) if it ever finishes building. Thanks for your response; Regards, Ferris -- Ferris McCormick (P44646, MI) <[EMAIL PROTECTED]> Phone: (703) 392-0303 Fax: (703) 392-0401 -- [EMAIL PROTECTED] mailing list
