Re: CVSup vs inttypes.h,v

2002-01-07 Thread Peter Wemm

Julian Elischer wrote:
 Well it's a pitty whoever moved it didn't grep for
 it.. my builds fail because of it.

It is present as src/include/inttypes.h.  You have stale .depend files
or are doing something silly like make -DNOCLEAN.

peter@daintree[5:45pm]~src-151 find . -type f -print | grep -v CVS | grep -v compile 
| grep -v obj | xargs grep sys/inttypes.h
./share/man/man5/types.5:#include sys/inttypes.h  /* includes 
machine/ansi.h */
./sys/dev/bktr/bktr_core.c:#include sys/inttypes.h/* uintptr_t */

The first is a stale doc bug, the latter is in
#if defined(__NetBSD__) || defined(__OpenBSD__).

ie: PEBKAC :-)

 On Mon, 31 Dec 2001, Mike Makonnen wrote:
 
  It's been moved to the Attic.  From what I can gather most of what was in t
here was moved to sys/sys/stdint.h and whatever files *it* includes.
  
  
  
  Cheers,
  mikem
  
  
  
  On Mon, 31 Dec 2001 21:32:17 -0800 (PST)
  Julian Elischer [EMAIL PROTECTED] wrote:
  
   
   CVSup is refusing to give me a inttypes.h,v in sys/sys
   
   I sup from cvsup14 as it's very close.
   How do I work out where the problem is?
   
   
   
   
   To Unsubscribe: send mail to [EMAIL PROTECTED]
   with unsubscribe freebsd-current in the body of the message
  
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with unsubscribe freebsd-current in the body of the message
  
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message
 
 

Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5


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



Re: CVSup vs inttypes.h,v

2002-01-01 Thread John Polstra

In article [EMAIL PROTECTED],
Julian Elischer  [EMAIL PROTECTED] wrote:
 
 CVSup is refusing to give me a inttypes.h,v in sys/sys
 
 I sup from cvsup14 as it's very close.
 How do I work out where the problem is?

Give me some details (supfile + command line), and I'll help you figure
it out.

John
-- 
  John Polstra
  John D. Polstra  Co., Inc.Seattle, Washington USA
  Disappointment is a good sign of basic intelligence.  -- Chögyam Trungpa


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



Re: CVSup vs inttypes.h,v

2002-01-01 Thread Julian Elischer

Well it's a pitty whoever moved it didn't grep for
it.. my builds fail because of it.


On Mon, 31 Dec 2001, Mike Makonnen wrote:

 It's been moved to the Attic.  From what I can gather most of what was in there was 
moved to sys/sys/stdint.h and whatever files *it* includes.
 
 
 
 Cheers,
 mikem
 
 
 
 On Mon, 31 Dec 2001 21:32:17 -0800 (PST)
 Julian Elischer [EMAIL PROTECTED] wrote:
 
  
  CVSup is refusing to give me a inttypes.h,v in sys/sys
  
  I sup from cvsup14 as it's very close.
  How do I work out where the problem is?
  
  
  
  
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with unsubscribe freebsd-current in the body of the message
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message
 


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



Re: CVSup vs inttypes.h,v

2002-01-01 Thread Mike Barcroft

Julian Elischer [EMAIL PROTECTED] writes:
 Well it's a pitty whoever moved it didn't grep for
 it.. my builds fail because of it.

I did indeed grep for occurences of it and fixed them.  The only
remaining instance appears in sys/dev/bktr/bktr_core.c which is in a
`#if defined(__NetBSD__) || defined(__OpenBSD__)' section.  If you are
interested in the types that used to be defined there, they are now in
sys/stdint.h.

Best regards,
Mike Barcroft

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



CVSup vs inttypes.h,v

2001-12-31 Thread Julian Elischer


CVSup is refusing to give me a inttypes.h,v in sys/sys

I sup from cvsup14 as it's very close.
How do I work out where the problem is?




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