Re: can't build kernel: config doesn't work

2001-07-01 Thread Warner Losh

In message <[EMAIL PROTECTED]> Michael Harnois writes:
: OK, so it is my fault. Did I miss a HEADS UP on this? It certainly
: deserved one.

I didn't send one.  Maybe I should have.

Warner

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: can't build kernel: config doesn't work

2001-07-01 Thread Mike Heffner


On 01-Jul-2001 Mark Peek wrote:
| At 10:05 AM -0400 7/1/01, Mike Heffner wrote:
|>It works for me ;) Remember that the new default is:
|>
|>   /sys/${MACHINEARCH}/compile/${KERNCONF}
| 
| 
| Right, there is a new compile directory. Perhaps this needs to be 
| added to UPDATING. Anyway, did you run "cvs update -dP" on your cvs 
| tree? Or just do mkdir on the new path mentioned above.

I just did a cvsup and ran config with no arguments, and it created the right
directory for me.

Mike

-- 
  Mike Heffner 
  Fredericksburg, VA   <[EMAIL PROTECTED]>


 PGP signature


Re: can't build kernel: config doesn't work

2001-07-01 Thread Mark Peek

At 8:27 AM -0700 7/1/01, Alex Zepeda wrote:
>On Sun, Jul 01, 2001 at 08:09:14AM -0700, Mark Peek wrote:
>
>>  Right, there is a new compile directory. Perhaps this needs to be
>>  added to UPDATING. Anyway, did you run "cvs update -dP" on your cvs
>>  tree? Or just do mkdir on the new path mentioned above.
>
>It *IS* in UPDATING:
>
>Updating Information for FreeBSD current users
>
>This file is maintained and copyrighted by M. Warner Losh
><[EMAIL PROTECTED]>.  Please send new entries directly to him.  See end
>of file for further details.  For commonly done items, please see the
>COMMON ITEMS: section later in the file.
>
>20010628:
> The kernel compile module has moved from src/sys/compile/FOO
> to src/sys/${MACHINE}/compile/FOO.


Silly me, of course Warner would make sure UPDATING is correct! :-) I 
must have glossed over the cvs commit message for that change. I 
stand corrected.

Mark

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: can't build kernel: config doesn't work

2001-07-01 Thread Michael Harnois

OK, so it is my fault. Did I miss a HEADS UP on this? It certainly
deserved one.

-- 
Michael D. Harnois[EMAIL PROTECTED]
Redeemer Lutheran Church  Washburn, Iowa 
 "He who will not reason is a bigot; he who cannot is a fool; 
  and he who dares not, is a slave." -- William Drummond

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: can't build kernel: config doesn't work

2001-07-01 Thread Alex Zepeda

On Sun, Jul 01, 2001 at 08:09:14AM -0700, Mark Peek wrote:

> Right, there is a new compile directory. Perhaps this needs to be 
> added to UPDATING. Anyway, did you run "cvs update -dP" on your cvs 
> tree? Or just do mkdir on the new path mentioned above.

It *IS* in UPDATING:

Updating Information for FreeBSD current users

This file is maintained and copyrighted by M. Warner Losh
<[EMAIL PROTECTED]>.  Please send new entries directly to him.  See end
of file for further details.  For commonly done items, please see the
COMMON ITEMS: section later in the file.

20010628:
The kernel compile module has moved from src/sys/compile/FOO
to src/sys/${MACHINE}/compile/FOO.

- alex

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: can't build kernel: config doesn't work

2001-07-01 Thread Mark Peek

At 10:05 AM -0400 7/1/01, Mike Heffner wrote:
>It works for me ;) Remember that the new default is:
>
>   /sys/${MACHINEARCH}/compile/${KERNCONF}
>
>
>On 01-Jul-2001 Takeshi Ken Yamada wrote:
>|
>|   The same here, but 'config -d /sys/compile/GENERIC GENERIC'
>| did what it is supposed to do.
>|
>|   Is this a new specification of 'config', or bug?
>|  
>| From: Michael Harnois <[EMAIL PROTECTED]>
>| Subject: can't build kernel: config doesn't work
>| mdharnois> Truly bizarre. Running config does nothing, although it generates
>| the
>| mdharnois> usual messages. I tried deleting my kernel object directory after
>| an
>| mdharnois> odd failure; ran config again, it didn't even recreate the
>| directory.
>| mdharnois>


Right, there is a new compile directory. Perhaps this needs to be 
added to UPDATING. Anyway, did you run "cvs update -dP" on your cvs 
tree? Or just do mkdir on the new path mentioned above.

Mark

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: can't build kernel: config doesn't work

2001-07-01 Thread Mike Heffner

It works for me ;) Remember that the new default is:

  /sys/${MACHINEARCH}/compile/${KERNCONF}


On 01-Jul-2001 Takeshi Ken Yamada wrote:
| 
|   The same here, but 'config -d /sys/compile/GENERIC GENERIC'
| did what it is supposed to do.
| 
|   Is this a new specification of 'config', or bug?
|   
| From: Michael Harnois <[EMAIL PROTECTED]>
| Subject: can't build kernel: config doesn't work
| mdharnois> Truly bizarre. Running config does nothing, although it generates
| the
| mdharnois> usual messages. I tried deleting my kernel object directory after
| an
| mdharnois> odd failure; ran config again, it didn't even recreate the
| directory.
| mdharnois> 
| 
| To Unsubscribe: send mail to [EMAIL PROTECTED]
| with "unsubscribe freebsd-current" in the body of the message


Mike

-- 
  Mike Heffner 
  Fredericksburg, VA   <[EMAIL PROTECTED]>


 PGP signature


Re: can't build kernel: config doesn't work

2001-07-01 Thread Takeshi Ken Yamada


  The same here, but 'config -d /sys/compile/GENERIC GENERIC'
did what it is supposed to do.

  Is this a new specification of 'config', or bug?
  
From: Michael Harnois <[EMAIL PROTECTED]>
Subject: can't build kernel: config doesn't work
mdharnois> Truly bizarre. Running config does nothing, although it generates the
mdharnois> usual messages. I tried deleting my kernel object directory after an
mdharnois> odd failure; ran config again, it didn't even recreate the directory.
mdharnois> 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message