All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] Use only elfutils package to provide the libelf library
Date: Thu, 28 Aug 2014 11:51:30 +0200	[thread overview]
Message-ID: <53FEFBA2.3030106@free-electrons.com> (raw)
In-Reply-To: <1409219230-17443-1-git-send-email-gregory.clement@free-electrons.com>

On 28/08/2014 11:47, Gregory CLEMENT wrote:
> Hi,
> 
> The libelf is currently provided by 2 packages libelf and
> elfutils. The first package provides an old version of the libelf
> which is no more compatible with a recent version of ltrace. Having
> both libraries could lead to the link on the wrong one during the
> build. It is what happened for ltrace.
> 
> To avoid this kind of issue, this patch set switch the dependecy from
> libelf to elfutils and finally removed the elfutils package.
> 
> I built and fully tested ltrace on ARM.
> I built and just ran avrdude on ARM.
> I didn't build kexec-lite.
> 
> Thanks,
> 
> Gregory
> 
> Gregory CLEMENT (4):
>   ltrace: Removes the libelf dependency
>   avrdude: Depend on elfutils instead of libelf to get the libel library
>   kexec-lite: Depends on elfutils instead of libelf to get the libelf
>     library
>   libelf: Removes the package

It seems that this last patch was too heavy:
"Is being held until the list moderator can review it for approval.

The reason it is being held:

    Message body is too big: 383953 bytes with a limit of 300 KB"

Is there a smarter way to create this patch with git?
Actually I am sure there is a smarter way (we can do everything with
git :) )but I don't know it.

> 
>  package/Config.in                               |     1 -
>  package/avrdude/Config.in                       |     2 +-
>  package/avrdude/avrdude.mk                      |     2 +-
>  package/kexec-lite/Config.in                    |     2 +-
>  package/kexec-lite/kexec-lite.mk                |     2 +-
>  package/libelf/Config.in                        |     7 -
>  package/libelf/libelf-0.8.10-Elf64-fixups.patch | 12361 ----------------------
>  package/libelf/libelf.mk                        |    23 -
>  package/ltrace/Config.in                        |     1 -
>  package/ltrace/ltrace.mk                        |     2 +-
>  10 files changed, 5 insertions(+), 12398 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
> 


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

  parent reply	other threads:[~2014-08-28  9:51 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
2014-08-28  9:51 ` Gregory CLEMENT [this message]
2014-08-28  9:53   ` [Buildroot] [PATCH 0/4] Use only elfutils package to provide the libelf library 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=53FEFBA2.3030106@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 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.