Re: Unassociated shell command when building kernel

2005-04-23 Thread madsen 
 If there is an old one, it's in the object tree.  But maybe there isn't,
 keep reading for my guess.

Do you know how to get at the old one? Or know where there are instructions
on how to do so?

 2)  If that isn't the problem, how can I find out what is?
 
 I'm thinking a perusal of /usr/src/UPDATING ... but IANAE.

I've checked it.  There's nothing there that I've seen that seems to 
help out.  If there is, I've passed it and didn't understand its
significance.

 Dave Madsen ---dcm
 
 My guess: it's likely your make is out of date.  See /usr/ports/UPDATING,
 entry 20040728.  If your world is older than that date, it's almost
 certainly the issue.  OTOH, if you're building kernels often (say,
 monthly?) and your world is last July or earlier, I'd have thought
 the problem to be older than one month.
 
 Are you also regularly building world?  They really need to
 be kept m/l in sync.

I build world and kernel about once a week.  I've been getting this
error for a while, and thought it might go away if I gave it some time,
like other errors have done in the past.  It hasn't.

 Now, I could be wrong, and often am; but it's worth thinking
 about, and seems quite possible.

Thanks for your assistance!  (You're the only one who's responded!)

 
 Kevin Kinsey
 
Dave Madsen ---dcm
adsenmay atay ijitvay otday omcay
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Unassociated shell command when building kernel

2005-04-21 Thread madsen 
I've been cvsup'ing the kernel regularly (standard-supfile) for
quite a while.  About maybe a month or so ago, when trying to do a
kernel build, I get what appear to be make errors with the error
message Unassociated shell command.

(A copy of the pertinent lines from the build log are below).

The final advice from the script seems to be
Run make -f rescue.mk to build crunched binary., but I 
cannot find rescue.mk anywhere.  Perhaps that's my problem, but
I do not know, and I don't know enough about the kernel build system
to know how to debug this situation.

1)  If the problem is a missing rescue.mk, how/where can I get a 
shiny new one?  And secondly, what happened to the old one?  Could 
an update have munged it? 

2)  If that isn't the problem, how can I find out what is?

3)  Is there an FM that I can RT on how the kernel build system is
put together?  Something that's more detailed than newbie but less
detailed than kernel developer?  Right now, it's a black box and I'd
like to grey it up a little.

4)  In a perhaps associated issue, after cvsup'ing ports, make fetchindex
and portupgrade also get the same error message.  

Dave Madsen ---dcm
adsenmay atay ijitvay otday omcay


Build log excerpt:

echo special gzip buildopts DIRPRFX=rescue/rescue/gzip/ rescue.conf
echo ln gzip gunzip rescue.conf
echo ln gzip gzcat rescue.conf
echo ln gzip zcat rescue.conf
echo progs chroot rescue.conf
echo special chroot srcdir /usr/src/rescue/rescue/../../usr.sbin/chroot 
rescue.conf
echo special chroot buildopts DIRPRFX=rescue/rescue/chroot/ rescue.conf
MAKEOBJDIRPREFIX=/usr/obj/usr/src/rescue/rescue crunchgen -fq -m rescue.mk  -c 
rescue.c rescue.conf
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 21: Unassociated shell 
command @${ECHO} testing conv=ebcdic
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 25: Unassociated shell 
command @./gen |  LC_ALL=en_US.US-ASCII ./dd conv=ebcdic 2/dev/null |  
LC_ALL=en_US.US-ASCII hexdump -C |  diff -I FreeBSD - ${.CURDIR}/ref.ebcdic
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 21: Unassociated shell 
command @${ECHO} testing conv=ibm
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 25: Unassociated shell 
command @./gen |  LC_ALL=en_US.US-ASCII ./dd conv=ibm 2/dev/null |  
LC_ALL=en_US.US-ASCII hexdump -C |  diff -I FreeBSD - ${.CURDIR}/ref.ibm
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 21: Unassociated shell 
command @${ECHO} testing conv=oldascii
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 25: Unassociated shell 
command @./gen |  LC_ALL=en_US.US-ASCII ./dd conv=oldascii 2/dev/null |  
LC_ALL=en_US.US-ASCII hexdump -C |  diff -I FreeBSD - ${.CURDIR}/ref.oldascii
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 21: Unassociated shell 
command @${ECHO} testing conv=oldebcdic
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 25: Unassociated shell 
command @./gen |  LC_ALL=en_US.US-ASCII ./dd conv=oldebcdic 2/dev/null |  
LC_ALL=en_US.US-ASCII hexdump -C |  diff -I FreeBSD - ${.CURDIR}/ref.oldebcdic
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 21: Unassociated shell 
command @${ECHO} testing conv=oldibm
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 25: Unassociated shell 
command @./gen |  LC_ALL=en_US.US-ASCII ./dd conv=oldibm 2/dev/null |  
LC_ALL=en_US.US-ASCII hexdump -C |  diff -I FreeBSD - ${.CURDIR}/ref.oldibm
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 21: Unassociated shell 
command @${ECHO} testing conv=pareven
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 25: Unassociated shell 
command @./gen |  LC_ALL=en_US.US-ASCII ./dd conv=pareven 2/dev/null |  
LC_ALL=en_US.US-ASCII hexdump -C |  diff -I FreeBSD - ${.CURDIR}/ref.pareven
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 21: Unassociated shell 
command @${ECHO} testing conv=parnone
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 25: Unassociated shell 
command @./gen |  LC_ALL=en_US.US-ASCII ./dd conv=parnone 2/dev/null |  
LC_ALL=en_US.US-ASCII hexdump -C |  diff -I FreeBSD - ${.CURDIR}/ref.parnone
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 21: Unassociated shell 
command @${ECHO} testing conv=parodd
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 25: Unassociated shell 
command @./gen |  LC_ALL=en_US.US-ASCII ./dd conv=parodd 2/dev/null |  
LC_ALL=en_US.US-ASCII hexdump -C |  diff -I FreeBSD - ${.CURDIR}/ref.parodd
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 21: Unassociated shell 
command @${ECHO} testing conv=parset
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 25: Unassociated shell 
command @./gen |  LC_ALL=en_US.US-ASCII ./dd conv=parset 2/dev/null |  
LC_ALL=en_US.US-ASCII hexdump -C |  diff -I FreeBSD - ${.CURDIR}/ref.parset
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 21: Unassociated shell 
command @${ECHO} testing conv=swab
/usr/src/rescue/rescue/../../bin/dd/Makefile, line 25: Unassociated shell 
command @./gen |  LC_ALL=en_US.US-ASCII ./dd conv=swab 2/dev/null |  
LC_ALL=en_US.US-ASCII hexdump -C |  diff -I

Re: Unassociated shell command when building kernel

2005-04-21 Thread Kevin Kinsey 
[EMAIL PROTECTED] wrote:
I've been cvsup'ing the kernel regularly (standard-supfile) for
quite a while.  About maybe a month or so ago, when trying to do a
kernel build, I get what appear to be make errors with the error
message Unassociated shell command.
(A copy of the pertinent lines from the build log are below).
The final advice from the script seems to be
Run make -f rescue.mk to build crunched binary., but I 
cannot find rescue.mk anywhere.  Perhaps that's my problem, but
I do not know, and I don't know enough about the kernel build system
to know how to debug this situation.

1)  If the problem is a missing rescue.mk, how/where can I get a 
shiny new one?  And secondly, what happened to the old one?  Could 
an update have munged it? 

 

If there is an old one, it's in the object tree.  But maybe there isn't,
keep reading for my guess.
2)  If that isn't the problem, how can I find out what is?
 

I'm thinking a perusal of /usr/src/UPDATING ... but IANAE.
3)  Is there an FM that I can RT on how the kernel build system is
put together?  Something that's more detailed than newbie but less
detailed than kernel developer?  Right now, it's a black box and I'd
like to grey it up a little.
4)  In a perhaps associated issue, after cvsup'ing ports, make fetchindex
and portupgrade also get the same error message.  

Dave Madsen ---dcm
adsenmay atay ijitvay otday omcay
 

My guess: it's likely your make is out of date.  See /usr/ports/UPDATING,
entry 20040728.  If your world is older than that date, it's almost
certainly the issue.  OTOH, if you're building kernels often (say,
monthly?) and your world is last July or earlier, I'd have thought
the problem to be older than one month.
Are you also regularly building world?  They really need to
be kept m/l in sync.
Now, I could be wrong, and often am; but it's worth thinking
about, and seems quite possible.
Kevin Kinsey
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]