From: Heilpern, M. <mar...@au...> - 2005-10-13 13:04:58
|
I'm seeing that a "make clean" terminated with an error. One of the commands in "dropbear_sshd-clean" is "rm -f /opt/gumstix-buildroot/build_arm_nofpu/root", and the error is that this is a directory. =20 Looking into dropbear.mk, this is happening in the clean: target, with the line: rm -f $(TARGET_DIR)/$(DROPBEAR_TARGET_BINARY) The variable TARGET_DIR is /opt/gumstix-buildroot/build_arm_nofpu/root, which looks good. The variable DROPBEAR_TARGET_BINARY is empty. _______________________________________________________ NOTE: The information in this message is intended for the personal and = confidential use of the designated recipient(s) named above. To the extent the = recipient(s) is/are bound by a non-disclosure agreement, or other agreement that contains an = obligation of confidentiality, with AuthenTec, then this message and/or any = attachments shall be considered confidential information and subject to the confidentiality = terms of that agreement. If the reader of this message is not the intended recipient = named above, you are notified that you have received this document in error, and any = review, dissemination, distribution or copying of this message is strictly prohibited. If you = have received this document in error, please delete the original message and notify the = sender immediately. Thank you. AuthenTec, Inc. http://www.authentec.com |
From: Dominic J. E. <sa...@th...> - 2005-10-13 13:21:26
|
On Thu, 13 Oct 2005, Heilpern, Mark wrote: > I'm seeing that a "make clean" terminated with an error. One of the > commands in "dropbear_sshd-clean" is "rm -f > /opt/gumstix-buildroot/build_arm_nofpu/root", and the error is that this > is a directory. > > Looking into dropbear.mk, this is happening in the clean: target, with > the line: rm -f $(TARGET_DIR)/$(DROPBEAR_TARGET_BINARY) > The variable TARGET_DIR is /opt/gumstix-buildroot/build_arm_nofpu/root, > which looks good. > The variable DROPBEAR_TARGET_BINARY is empty. I had noticed this, but never was able to find out which .mk file was causing it. Craig, et al: Changing the rm -f to rm -rf solves the problem. - d. -- Dominic J. Eidson "Baruk Khazad! Khazad ai-menu!" - Gimli ------------------------------------------------------------------------------- http://www.the-infinite.org/ |
From: Dominic J. E. <sa...@th...> - 2005-10-13 13:23:52
|
On Thu, 13 Oct 2005, Dominic J. Eidson wrote: > I had noticed this, but never was able to find out which .mk file was > causing it. > > Craig, et al: Changing the rm -f to rm -rf solves the problem. Sigh. This'll teach me to write emails too early in the morning. Nevermind. I was wrong (Although it, in typical hack-ish fashion, does work :) - d. -- Dominic J. Eidson "Baruk Khazad! Khazad ai-menu!" - Gimli ------------------------------------------------------------------------------- http://www.the-infinite.org/ |