RE: Syscalls.master broken on -CURRENT?

2002-06-16 Thread Vadim Belman

On Sat, 2002-06-15 at 18:03, Robert Watson wrote:

During the compilation of usr.bin/truss this error stops world:
   
syscalls.master: line 55: syscall number out of sync at 7
line is:
   struct rusage  * rusage ) ;  }  wait4 wait_args int
   
The error is actually produced by the execution of
'/usr/src/sys/kern/makesyscalls.sh syscalls.master'
   
What I don't understand is why this same error breaks world
on one of my -CURRENT machines but not on the other machine...
  
  Try this:
  
  # cd /usr/src/usr.bin/truss
  # make clean
  # make
  
  I think you will see the error appear.
 
 s/appear/disappear/?  It basically looks like the generated include files
 aren't in sync, but it's not something I can reproduce locally.  Lots of
 make cleaning and make includes should clear this up.  If it doesn't, let
 me know, and I'll do more chasing.

I just have found source of the problem. It's broken sed, again. Having
a look into syscalls.master it's easy to spot that error take place
where lines are broken like this one:

7   MSTDBSD { int wait4(int pid, int *status, int options, \
  struct rusage *rusage); } wait4 wait_args int

As they're joned back with sed, it's easy to guess the cause...

# cd /usr/src/usr.bin/sed
# make
# make install

And it works.

-- 
/Voland Vadim Belman
http://www.lflat.org
http://www.lflat.net


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



Re: Syscalls.master broken on -CURRENT?

2002-06-16 Thread walt

walt wrote:
During the compilation of usr.bin/truss this error stops world:
   
syscalls.master: line 55: syscall number out of sync at 7
line is:
 struct rusage  * rusage ) ;  }  wait4 wait_args int
   
The error is actually produced by the execution of
'/usr/src/sys/kern/makesyscalls.sh syscalls.master'
   
What I don't understand is why this same error breaks world
on one of my -CURRENT machines but not on the other machine...
 
  Try this:
 
  # cd /usr/src/usr.bin/truss
  # make clean
  # make
 
  I think you will see the error appear.
 

And Vladim Belman saves the day:

   I just have found source of the problem. It's broken sed,
   again...

   # cd /usr/src/usr.bin/sed
   # make
   # make install
  
   And it works.

Yes!  Thank you.  Now I hope I can undo the mess I've made of my
machine in the meantime while trying to fix this ;-)



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



RE: Syscalls.master broken on -CURRENT?

2002-06-15 Thread walt

  During the compilation of usr.bin/truss this error stops world:
 
  syscalls.master: line 55: syscall number out of sync at 7
  line is:
 struct rusage  * rusage ) ;  }  wait4 wait_args int
 
  The error is actually produced by the execution of
  '/usr/src/sys/kern/makesyscalls.sh syscalls.master'
 
  What I don't understand is why this same error breaks world
  on one of my -CURRENT machines but not on the other machine...

Try this:

# cd /usr/src/usr.bin/truss
# make clean
# make

I think you will see the error appear.


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



RE: Syscalls.master broken on -CURRENT?

2002-06-15 Thread Robert Watson


On Sat, 15 Jun 2002, walt wrote:

   During the compilation of usr.bin/truss this error stops world:
  
   syscalls.master: line 55: syscall number out of sync at 7
   line is:
struct rusage  * rusage ) ;  }  wait4 wait_args int
  
   The error is actually produced by the execution of
   '/usr/src/sys/kern/makesyscalls.sh syscalls.master'
  
   What I don't understand is why this same error breaks world
   on one of my -CURRENT machines but not on the other machine...
 
 Try this:
 
 # cd /usr/src/usr.bin/truss
 # make clean
 # make
 
 I think you will see the error appear.

s/appear/disappear/?  It basically looks like the generated include files
aren't in sync, but it's not something I can reproduce locally.  Lots of
make cleaning and make includes should clear this up.  If it doesn't, let
me know, and I'll do more chasing.

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Network Associates Laboratories



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