From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] cc-tool: pass -latomic in LIBS
Date: Sun, 20 Aug 2017 15:54:06 +0200 [thread overview]
Message-ID: <20170820155406.1884dcfd@windsurf> (raw)
In-Reply-To: <20170820133416.11231-1-thomas.petazzoni@free-electrons.com>
Hello,
On Sun, 20 Aug 2017 15:34:15 +0200, Thomas Petazzoni wrote:
> .../0003-Makefile.am-do-not-overwrite-LIBS.patch | 49 ++++++++++++++++++++++
This patch has been submitted to some "upstream" at
https://github.com/dashesy/cc-tool/pull/4. The real upstream at
SourceForge seems to be dead, while this repo has seen commits last
year.
While at it, I also submitted another patch we had on cc-tool:
https://github.com/dashesy/cc-tool/pull/5.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-08-20 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 13:34 [Buildroot] [PATCH 1/2] cc-tool: pass -latomic in LIBS Thomas Petazzoni
2017-08-20 13:34 ` [Buildroot] [PATCH 2/2] cc-tool: add patch fixing boost.m4 logic for static linking Thomas Petazzoni
2017-08-20 13:54 ` Thomas Petazzoni
2017-08-20 13:54 ` Thomas Petazzoni [this message]
2017-08-23 21:24 ` [Buildroot] [PATCH 1/2] cc-tool: pass -latomic in LIBS Thomas Petazzoni
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=20170820155406.1884dcfd@windsurf \
--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