Re: potential future proofing fix for aicasm build.

2013-05-02 Thread Konstantin Belousov
On Thu, May 02, 2013 at 10:57:23AM -0700, Xin Li wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 05/02/13 00:19, Dimitry Andric wrote: > > On May 1, 2013, at 18:44, Alfred Perlstein > > wrote: > >> I took a shot at fixing this issue with building aicasm as part > >> of "buildker

Re: potential future proofing fix for aicasm build.

2013-05-02 Thread Xin Li
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/02/13 00:19, Dimitry Andric wrote: > On May 1, 2013, at 18:44, Alfred Perlstein > wrote: >> I took a shot at fixing this issue with building aicasm as part >> of "buildkernel" of an older 9.0 src on a machine running HEAD. >> >> aicasm.o: In

Re: potential future proofing fix for aicasm build.

2013-05-02 Thread Dimitry Andric
On 2013-05-02 13:55, Steven Hartland wrote: From: "Dimitry Andric" On 2013-05-02 11:54, Steven Hartland wrote: From: "Dimitry Andric" ... I think what I did was the following:- 1. make buildkernel KERNCONF=MYCONF -j10 # failed due to aicasm And this is what I cannot reproduce. Works just

Re: potential future proofing fix for aicasm build.

2013-05-02 Thread Steven Hartland
- Original Message - From: "Dimitry Andric" On 2013-05-02 11:54, Steven Hartland wrote: From: "Dimitry Andric" ... Well, a way to reproduce the problem would be nice. I tried running "make buildkernel" in a stable/9 tree on a 10.0 machine, and building aicasm went just fine. So

Re: potential future proofing fix for aicasm build.

2013-05-02 Thread Dimitry Andric
On 2013-05-02 11:54, Steven Hartland wrote: From: "Dimitry Andric" ... Well, a way to reproduce the problem would be nice. I tried running "make buildkernel" in a stable/9 tree on a 10.0 machine, and building aicasm went just fine. So it works for me... I think what I did was the following

Re: potential future proofing fix for aicasm build.

2013-05-02 Thread Steven Hartland
- Original Message - From: "Dimitry Andric" On 2013-05-02 09:47, Steven Hartland wrote: I just remembered I had an issue with aicasm when compiling our kernel that didn't have ahc or ahd on an 8.3 box. The fix was to manually delete the kernel obj directory before compiling after do

Re: potential future proofing fix for aicasm build.

2013-05-02 Thread Dimitry Andric
On 2013-05-02 09:47, Steven Hartland wrote: I just remembered I had an issue with aicasm when compiling our kernel that didn't have ahc or ahd on an 8.3 box. The fix was to manually delete the kernel obj directory before compiling after doing a full make buildworld. For some reason there was so

Re: potential future proofing fix for aicasm build.

2013-05-02 Thread Steven Hartland
make buildkernel wasn't cleaning out, could you be suffering from a similar issue? - Original Message - From: "Dimitry Andric" To: "Alfred Perlstein" Cc: Sent: Thursday, May 02, 2013 8:19 AM Subject: Re: potential future proofing fix for aicasm build. On

Re: potential future proofing fix for aicasm build.

2013-05-02 Thread Dimitry Andric
On May 1, 2013, at 18:44, Alfred Perlstein wrote: > I took a shot at fixing this issue with building aicasm as part of > "buildkernel" of an older 9.0 src on a machine running HEAD. > > aicasm.o: In function `__getCurrentRuneLocale': > /usr/include/runetype.h:96: > undefined reference to `_Thre

Re: potential future proofing fix for aicasm build.

2013-05-01 Thread Alfred Perlstein
On 5/1/13 2:38 PM, Brooks Davis wrote: On Wed, May 01, 2013 at 09:44:54AM -0700, Alfred Perlstein wrote: Hey folks, I took a shot at fixing this issue with building aicasm as part of "buildkernel" of an older 9.0 src on a machine running HEAD. aicasm.o: In function `__getCurrentRuneLocale': >

Re: potential future proofing fix for aicasm build.

2013-05-01 Thread Brooks Davis
On Wed, May 01, 2013 at 09:44:54AM -0700, Alfred Perlstein wrote: > Hey folks, > > I took a shot at fixing this issue with building aicasm as part of > "buildkernel" of an older 9.0 src on a machine running HEAD. > > aicasm.o: In function `__getCurrentRuneLocale': > > /usr/include/runetype.h:96

potential future proofing fix for aicasm build.

2013-05-01 Thread Alfred Perlstein
Hey folks, I took a shot at fixing this issue with building aicasm as part of "buildkernel" of an older 9.0 src on a machine running HEAD. aicasm.o: In function `__getCurrentRuneLocale': > /usr/include/runetype.h:96: undefined reference to `_ThreadRuneLocale' The issue seems to be two-fold:

Re: potential future proofing fix for aicasm build.

2013-05-01 Thread Alfred Perlstein
On 5/1/13 9:57 AM, Steven Hartland wrote: I don't believe aicasm is actually needed if you don't have a driver which requires e.g. ahd or ahc. It would be good to get that fixed too. True, but a challenge I don't currently have time for. I'm about to kick-off a universe build with my changes i

Re: potential future proofing fix for aicasm build.

2013-05-01 Thread Steven Hartland
tial future proofing fix for aicasm build. Hey folks, I took a shot at fixing this issue with building aicasm as part of "buildkernel" of an older 9.0 src on a machine running HEAD. aicasm.o: In function `__getCurrentRuneLocale': > /usr/include/runetype.h:96: undefined refer

potential future proofing fix for aicasm build.

2013-05-01 Thread Alfred Perlstein
Hey folks, I took a shot at fixing this issue with building aicasm as part of "buildkernel" of an older 9.0 src on a machine running HEAD. aicasm.o: In function `__getCurrentRuneLocale': > /usr/include/runetype.h:96: undefined reference to `_ThreadRuneLocale' The issue seems to be two-fold: 1