All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5378] dropbear Makefile broken
Date: Mon, 10 Sep 2012 20:05:14 +0000 (UTC)	[thread overview]
Message-ID: <20120910200515.20F1A995FD@busybox.osuosl.org> (raw)
In-Reply-To: <bug-5378-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=5378

--- Comment #5 from Mike Frysinger <vapier@gentoo.org> 2012-09-10 20:05:14 UTC ---
(In reply to comment #1)

it would be better to fix Makefile.in itself and then send the fix upstream

(In reply to comment #2)

make has implicit rules to handle "-lfoo" in its dependency list.  so dropbear
does this:

dropbearobjs=$(COMMONOBJS) $(CLISVROBJS) $(SVROBJS) @CRYPTLIB@
...
dropbear: $(dropbearobjs)

this expands into:
dropbear: ... -lcrypt

and make executes its implicit code to try and find /usr/lib/libcrypt.a.  if
you don't have that, it'll fail.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  parent reply	other threads:[~2012-09-10 20:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 12:21 [Buildroot] [Bug 5378] New: dropbear Makefile broken bugzilla at busybox.net
2012-07-19 12:22 ` [Buildroot] [Bug 5378] " bugzilla at busybox.net
2012-08-21 12:04 ` bugzilla at busybox.net
2012-09-10 11:05 ` bugzilla at busybox.net
2012-09-10 19:53 ` bugzilla at busybox.net
2012-09-10 20:05 ` bugzilla at busybox.net [this message]
2012-09-10 20:52 ` bugzilla at busybox.net
2013-12-11 17:16 ` bugzilla at busybox.net

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=20120910200515.20F1A995FD@busybox.osuosl.org \
    --to=bugzilla@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.