Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] libelf: Removes the package
Date: Thu, 28 Aug 2014 13:53:58 +0200	[thread overview]
Message-ID: <53FF1856.8080200@free-electrons.com> (raw)
In-Reply-To: <20140828131122.2a0d4533@free-electrons.com>

Hi Thomas,

On 28/08/2014 13:11, Thomas Petazzoni wrote:
> Dear Gregory CLEMENT,
> 
> On Thu, 28 Aug 2014 11:47:10 +0200, Gregory CLEMENT wrote:
>> The elfutils package provides a more recent version of the
>> libelf. Some packages such as ltrace need this more recent
>> version. Having two packages providing the same library leads to some
>> conflicts or dependency problems. For instance at the end we had only
>> one libelf.a when the 2 packages were selected.
>>
>> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
>> ---
>>  package/Config.in                               |     1 -
>>  package/libelf/Config.in                        |     7 -
>>  package/libelf/libelf-0.8.10-Elf64-fixups.patch | 12361 ----------------------
>>  package/libelf/libelf.mk                        |    23 -
>>  4 files changed, 12392 deletions(-)
>>  delete mode 100644 package/libelf/Config.in
>>  delete mode 100644 package/libelf/libelf-0.8.10-Elf64-fixups.patch
>>  delete mode 100644 package/libelf/libelf.mk
> 
> When removing a package, the config option of the package should be
> moved to Config.in.legacy to allow the user to be warned that he is
> using a no longer available package.

Ok a new version is coming soon.


Thanks,

Gregory
-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2014-08-28 11:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28  9:47 [Buildroot] [PATCH 0/4] Use only elfutils package to provide the libelf library Gregory CLEMENT
2014-08-28  9:47 ` [Buildroot] [PATCH 1/4] ltrace: Removes the libelf dependency Gregory CLEMENT
2014-08-28  9:58   ` Yann E. MORIN
2014-08-28  9:47 ` [Buildroot] [PATCH 2/4] avrdude: Depend on elfutils instead of libelf to get the libel library Gregory CLEMENT
2014-08-28 10:02   ` Yann E. MORIN
2014-08-28 10:04     ` Gregory CLEMENT
2014-08-28  9:47 ` [Buildroot] [PATCH 3/4] kexec-lite: Depends on elfutils instead of libelf to get the libelf library Gregory CLEMENT
2014-08-28 10:06   ` Yann E. MORIN
2014-08-28  9:47 ` [Buildroot] [PATCH 4/4] libelf: Removes the package Gregory CLEMENT
2014-08-28 11:11   ` Thomas Petazzoni
2014-08-28 11:53     ` Gregory CLEMENT [this message]
2014-08-28  9:51 ` [Buildroot] [PATCH 0/4] Use only elfutils package to provide the libelf library Gregory CLEMENT
2014-08-28  9:53   ` Yann E. MORIN
2014-08-28 10:02 ` Gregory CLEMENT

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=53FF1856.8080200@free-electrons.com \
    --to=gregory.clement@free-electrons.com \
    --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