From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0003544]: Installation of tftp-hpa fails
Date: Sun, 1 Jun 2008 11:55:52 -0700 [thread overview]
Message-ID: <fbe2ec75cf627b7e8bc913232af68521@bugs.uclibc.org> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=3544
======================================================================
Reported By: KHAksnes
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 3544
Category: Architecture Specific
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 06-01-2008 11:55 PDT
Last Modified: 06-01-2008 11:55 PDT
======================================================================
Summary: Installation of tftp-hpa fails
Description:
in.tftpd isn't always installed correctly. The following rule fragment from
package/tftpd/tftpd.mk looks suspect as ! binds tighter than -o at least in
the shells I have been testing.
@if [ ! -f $(TFTP_HPA_DIR)/$(TFTP_HPA_BINARY) -o $(TARGET_DIR)/$(TFTP_HP
A_TARGET_BINARY) \
-ot $(TFTP_HPA_DIR)/$(TFTP_HPA_BINARY) ]; then \
set -x; \
rm -f $(TARGET_DIR)/$(TFTP_HPA_TARGET_BINARY); \
cp -a $(TFTP_HPA_DIR)/$(TFTP_HPA_BINARY)
$(TARGET_DIR)/$(TFTP_HPA_TA
RGET_BINARY); fi
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
06-01-08 11:55 KHAksnes New Issue
06-01-08 11:55 KHAksnes Status new => assigned
06-01-08 11:55 KHAksnes Assigned To => buildroot
======================================================================
reply other threads:[~2008-06-01 18:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fbe2ec75cf627b7e8bc913232af68521@bugs.uclibc.org \
--to=bugs@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox