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.

On 9/29/05, eric <[EMAIL PROTECTED]> wrote:
> [ Note: I don't like doing this. I would rather use a snapshot and   ]
> [ just get -current, but I have the Adaptec bullshit on this machine ]
> [ and need a kernel that support aac(4).                             ]
>
> I'm going from 3.6 to 3.7, and just trying to get the fscking adaptec
> controller working.
>
> Following information found in release(8), I wind up with this:
>
> 1. Reboot new GENERIC.MP kernel. Works fine.
> 2. Clean up /usr/obj/*
> 3. I have to upgrade my compiler.
>
> # gcc -v
> Reading specs from /usr/lib/gcc-lib/i386-unknown-openbsd3.6/2.95.3/specs
> gcc version 2.95.3 20010125 (prerelease, propolice)
>
> Alas, /usr/obj/gnu/egcs/gcc/ isn't found on this machine. Do I need to
> rebuild all my 3.6-STABLE sources first? Then upgrade the 2.x compile, then
> move to 3.x?
>
> If I follow instructions in the FAQ and try and compile gcc 3.x, I get this
> far.
>
> # rm -r /usr/obj/gnu/usr.bin/gcc/*
> # cd /usr/src/gnu/usr.bin/gcc
> # make -f Makefile.bsd-wrapper clean
> # make -f Makefile.bsd-wrapper obj
> # make -f Makefile.bsd-wrapper depend
> # make -f Makefile.bsd-wrapper
>
> [snip]
>
> /usr/src/gnu/usr.bin/gcc/gcc/unwind-dw2-fde-glibc.c:139: error: `PT_LOOS'
> undeclared (first use in this function)
> /usr/src/gnu/usr.bin/gcc/gcc/unwind-dw2-fde-glibc.c:139: error: (Each
> undeclared identifier is reported only once
> /usr/src/gnu/usr.bin/gcc/gcc/unwind-dw2-fde-glibc.c:139: error: for each
> function it appears in.)
> /usr/src/gnu/usr.bin/gcc/gcc/unwind-dw2-fde-glibc.c: In function
> `_Unwind_Find_FDE':
> /usr/src/gnu/usr.bin/gcc/gcc/unwind-dw2-fde-glibc.c:283: warning: implicit
> declaration of function `dl_iterate_phdr'
> *** Error code 1
>
> Stop in /usr/src/gnu/usr.bin/gcc/obj (line 208 of libgcc.mk).
> *** Error code 1
>
> Stop in /usr/src/gnu/usr.bin/gcc/obj (line 2160 of Makefile).
> *** Error code 1
>
> Stop in /usr/src/gnu/usr.bin/gcc (line 84 of
> /usr/src/gnu/usr.bin/gcc/Makefile.bsd-wrapper).
> #
>
> Thanks for hitting me with a cluestick. MANTRA: don't buy adaptec. don't buy
> adaptec. don't buy adaptec.

Reply via email to