From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libatomic_ops: Remove duplicate targets
Date: Tue, 14 Feb 2012 23:22:17 +0100 [thread overview]
Message-ID: <201202142322.18176.arnout@mind.be> (raw)
In-Reply-To: <4F38DB27.5090707@imgtec.com>
On Monday 13 February 2012 10:43:03 Markos Chandras wrote:
> Hi,
>
> Please review the attached patch. libatomic_ops refuses to install
> because the build system overwrites newly installed targets.
I don't see how the duplicates could be a problem... install (or
install-sh) will just overwrite it the second time. It has to,
otherwise running 'make install' a second time would fail. Basically,
it works for me.
> The patch
> removes these targets from the Makefiles and runs autoreconf to
> regenerate the build system. If you need me to send the patch as a
> separate file please let me know. I haven't send this to upstream yet
> but I plan to do so.
Of course, this is still relevant to send upstream.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120214/82bfc27e/attachment.html>
next prev parent reply other threads:[~2012-02-14 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 9:43 [Buildroot] [PATCH] libatomic_ops: Remove duplicate targets Markos Chandras
2012-02-14 22:22 ` Arnout Vandecappelle [this message]
2012-02-15 11:09 ` Markos Chandras
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=201202142322.18176.arnout@mind.be \
--to=arnout@mind.be \
--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