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 2857] New: OBJDUMP definition is missing from TARGET_CONFIGURE_OPTS
Date: Thu, 25 Nov 2010 18:34:54 +0000 (UTC)	[thread overview]
Message-ID: <bug-2857-163@https.bugs.busybox.net/> (raw)

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

           Summary: OBJDUMP definition is missing from
                    TARGET_CONFIGURE_OPTS
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: mroberto at cpti.cetuc.puc-rio.br
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created attachment 2737
  --> https://bugs.busybox.net/attachment.cgi?id=2737
Patch to fix the missing OBJDUMP definition issue.

The OBJDUMP was missing from TARGET_CONFIGURE_OPTS.

In my case, I had problems when installing a package of my own that had a linux
kernel module. The call to objdump would fail.

This patch adds it to the proper place in package/Makefile.in.

-- 
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.

             reply	other threads:[~2010-11-25 18:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25 18:34 bugzilla at busybox.net [this message]
2010-11-27 21:40 ` [Buildroot] [Bug 2857] OBJDUMP definition is missing from TARGET_CONFIGURE_OPTS 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=bug-2857-163@https.bugs.busybox.net/ \
    --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.