Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9356] gdb package
Date: Fri, 14 Oct 2016 21:47:54 +0000	[thread overview]
Message-ID: <bug-9356-163-FKQRlvNVhM@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9356-163@https.bugs.busybox.net/>

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

Peter Korsgaard <jacmet@uclibc.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #3 from Peter Korsgaard <jacmet@uclibc.org> ---
I take it you refer to the recent issue installing gdb(server)? That is now
fixed in git by:

commit 8ae8d1162d92f14a0445fc497f473fde0aee6c3c
Author: Peter Korsgaard <peter@korsgaard.com>
Date:   Fri Oct 14 19:32:43 2016 +0200

    gdb: unbreak host/target install step

    Commit 12306a81f8edc (gdb: get rid of host-texinfo dependency) tried to
    append MAKEINFO=true to the host/target make install arguments, but as the
    default values for these are only added when (host-)autotools-package is
    evaluated (and only if empty), this effectively drops the default values
and
    we ended up without the 'install' target and nothing got installed.

    To fix this, specify the full install arguments.

    Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2016-10-14 21:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14 12:02 [Buildroot] [Bug 9356] New: gdb bugzilla at busybox.net
2016-10-14 12:22 ` [Buildroot] [Bug 9356] gdb package bugzilla at busybox.net
2016-10-14 13:02 ` bugzilla at busybox.net
2016-10-14 15:18 ` bugzilla at busybox.net
2016-10-14 21:47 ` bugzilla at busybox.net [this message]

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-9356-163-FKQRlvNVhM@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox