Well the compiler issue was pretty simple for me, follow the compiler upgrade faq here:
http://www.openbsd.org/faq/faq5.html#NewCompiler But make sure you first compile gcc 3 from 3.6 source code (by adding i386 to the gcc3 list in bsd.own.mk file in /usr/share/mk) and then recompile 3.6 source code completely. Then recompile the gcc 3 compiler using 3.7 source code, and recompile the 3.7 source from there (3.7 uses gcc 3 by default for i386). This following thread from April helped me out as well: http://marc.theaimsgroup.com/?t=111418335600005&r=1&w=2 On 9/29/05, eric <[EMAIL PROTECTED]> wrote: > On Thu, 2005-09-29 at 13:40:36 -0400, Jason Crawford proclaimed... > > > I ran into the same issue myself, as I have a server with the aac raid > > card, and no way to upgrade from 3.6 to 3.7 (I'm running 3.8-release > > on it now). Reading the archives and various upgrade faq's on > > OpenBSD's website, I found a method that worked for me, but no > > guarantees for anyone else. First, I made sure my 3.6 source was fully > > up to date with the OPENBSD_3_6 tag, then I compiled gcc3 from the > > openbsd 3.6 sources, which involved me changing around the bsd.own.mk > > file in /usr/share/mk to remove i386 from the list of gcc2 archs. You > > run through the new compiler faq, which is compiling gcc3 twice, first > > to get a workable gcc3 compiler from gcc2, then to recompile gcc3 with > > gcc3 you just did. Next I ran through the entire make build in 3.6 > > using the gcc3 compile, the change to bsd.own.mk automatically makes > > it compile the right version of everything to use the gcc3 compiler. > > It failed for me on texinfo (or something in the gnu directory), but I > > just ran through the rest of the make build process by hand. Then I > > installed all the binaries, having to do the parts after gnu by hand > > since the one app failed, so now I was running 3.6 with gcc3 binaries. > > Next I moved /usr/src to /usr/src.old and grabbed OpenBSD 3.7 source > > into /usr/src (also move /usr/obj to /usr/obj.old and a new /usr/obj > > for 3.7 source). Then I compiled the new gcc3 compiler in 3.7 (later > > version) twice like the faq says for new compilers, and then compiled > > the 3.7 kernel with aac support, rebooted, and recompiled my system. > > One part that I was unclear about was whether I tried to recompile > > some parts of 3.7 before rebooting into the kernel, or whether i > > rebooted into the kernel before compiling the system, which could make > > a big difference. I can do some more research if you wish, but again > > this is a completely unsupported method of upgrade, and I don't > > guarantee that this will work for anyone other than myself. The > > process of upgrading source from 3.7 to 3.8 was much easier than 3.6 > > to 3.7, mostly because there wasn't a huge compiler change. > > If you can let me know if there was anything else I'd appreciate it. I just > need to get over the compiler hump. No support is expected, by the way. > > Thanks a bunch. > > - Eric
