Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libgc: Remove duplicated package
Date: Fri, 27 Feb 2015 06:44:00 +0200	[thread overview]
Message-ID: <20150227044400.GO2402@tarshish> (raw)
In-Reply-To: <1424988981-9787-1-git-send-email-paguilar@paguilar.org>

Hi Pedro,

On Thu, Feb 26, 2015 at 11:16:21PM +0100, Pedro Aguilar wrote:
> Remove libgc that is a copy of bdwgc but it's not used
> by any package and gives an error when building make-4.1.
> bdwgc is a mandatory dependency for guile.

Thanks for your prompt response.

In addition to Config.in.legacy entry as Peter has mentioned, it would be nice 
to add an autobuilder reference, and a Reported-by tag. I sent v2 patch with 
these added.

> Signed-off-by: Pedro Aguilar <paguilar@paguilar.org>
> ---
>  package/Config.in                                  |  1 -
>  ...01-Fix-build-on-Linux-x86_64-under-uClibc.patch | 32 ----------------------
>  package/libgc/Config.in                            | 11 --------
>  package/libgc/libgc.mk                             | 15 ----------
>  4 files changed, 59 deletions(-)
>  delete mode 100644 package/libgc/0001-Fix-build-on-Linux-x86_64-under-uClibc.patch
>  delete mode 100644 package/libgc/Config.in
>  delete mode 100644 package/libgc/libgc.mk

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

      parent reply	other threads:[~2015-02-27  4:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 22:16 [Buildroot] [PATCH 1/1] libgc: Remove duplicated package Pedro Aguilar
2015-02-26 22:48 ` Peter Korsgaard
2015-02-27  4:44 ` Baruch Siach [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=20150227044400.GO2402@tarshish \
    --to=baruch@tkos.co.il \
    --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