Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] libffi target header installation problem
Date: Mon, 26 Aug 2013 16:06:57 +0200	[thread overview]
Message-ID: <20130826160657.59266f0b@skate> (raw)
In-Reply-To: <277645944.5505869.1377525879032.JavaMail.root@openwide.fr>

Dear Nicolas M?n?gale,

On Mon, 26 Aug 2013 16:04:39 +0200 (CEST), Nicolas M?n?gale wrote:

> Well I had, for a specific reason, two folder for two different versions of libffi into $(STAGING_DIR)/usr/lib/:
> libffi-3.0.11 and libffi-3.0.10 
> This mv command was failing saying:
> "will not overwrite just-created <filename> with <sameFilename>"
> because it was trying to overwrite the .h it just moved. 

Ok, that's what can happen if you bump Buildroot and then restart the
build without doing a "make clean". We generally don't support this
kind of use case, but I agree that in this case it doesn't hurt to
specify explicitly the version, so you can certainly send a patch for
this.

Thanks,

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

      reply	other threads:[~2013-08-26 14:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1626579523.5503469.1377524132514.JavaMail.root@openwide.fr>
2013-08-26 13:41 ` [Buildroot] libffi target header installation problem Nicolas Ménégale
2013-08-26 13:44   ` Thomas Petazzoni
2013-08-26 14:04     ` Nicolas Ménégale
2013-08-26 14:06       ` Thomas Petazzoni [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=20130826160657.59266f0b@skate \
    --to=thomas.petazzoni@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