Paul Pruett wrote: > I have received several assurances that > -current may have resolved some weirds > for i386 on amd64 processors... > > With hesitation I could try jumping to current > instead of stable amd64. > > I have used -current on productin before, > but only after verifying the ports could > make w/o fubars
That's really not much of a test. The porting people do exactly that for you. If -current is broke in such a way that it can't build ports, they usually spot it. Use a package. > > Either amd64 stable or i386 current > I'll still should remake the ports to match, > especially openldap and cyrus-imapd and > verify. :( For reference, a machine I have managed to consistently demonstrate the i386-on-amd64 hang after less than ten minutes of "make build" has completed 158 (and counting) builds in a non-stop loop. I think -current will be much better for you than -release/stable. (one problem with this kind of testing: I'm not sure when to end it! :) At this point in the release cycle, if you have problems with -current, you are going to have problems with 4.1 unless you report them, so I'd suggest testing. :) Nick. (proud owner of his first amd64, which has been stuck running i386 code almost since assembly...) (damn. just about had a heart attack there as the build output stopped for a few seconds (in perl) after typing that...not used to seeing any pause in this thing's output! :)
