gcc4,amd64 - mk.conf?

2010-05-30 Thread Dorian Büttner
Marco's instructions, pointed to from the undeadly article, mentions to set COMPILER_VERSION=gcc4 in mk.conf, as opposed to current.html which does not list this step. Does it make any difference having it in mk.conf or not? Propably this would have been explixitely mentioned in the

Re: gcc4,amd64 - mk.conf?

2010-05-30 Thread Rolf Sommerhalder
Does it make any difference having it in mk.conf or not? At the moment, I am looking into the same question. Yesterday, I went through the compiler upgrade steps on an i386-current machine. Probably, I have ended up with a gcc3-compiled gcc4 on my i386 system, although I had thought I had

Re: gcc4,amd64 - mk.conf?

2010-05-30 Thread Nicholas Marriott
You only need it if you are building on an arch which hasn't moved to gcc4 yet (that is, not amd64 or sparc64). On Sun, May 30, 2010 at 11:30:15AM +0200, Dorian B?ttner wrote: Marco's instructions, pointed to from the undeadly article, mentions to set COMPILER_VERSION=gcc4 in mk.conf, as

Re: gcc4,amd64 - mk.conf?

2010-05-30 Thread Rolf Sommerhalder
if this solves the compile error I had encoutered while building the userland, Yes, it did. After setting COMPILER_VERSION=gcc4 in /etc/mk.conf, re-compiling gcc4 with itself just to be on the safe side, then the builds of the kernel, userland, and finally xenocara were successful. This just