From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Wang Nan <wangnan0@huawei.com>, David Ahern <dsahern@gmail.com>,
"Peter Zijlstra" <peterz@infradead.org>,
Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
Petri Gynther <pgynther@google.com>, Jiri Olsa <jolsa@kernel.org>,
osh Poimboeuf <jpoimboe@redhat.com>,
"Namhyung Kim" <namhyung@kernel.org>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH] tools lib: Reinstate strlcpy() header guard with __UCLIBC__
Date: Fri, 19 Aug 2016 13:09:51 -0700 [thread overview]
Message-ID: <45c665be-5965-32d9-b32b-b55c0cd29435@synopsys.com> (raw)
In-Reply-To: <20160819192302.GA20810@kernel.org>
On 08/19/2016 12:23 PM, Arnaldo Carvalho de Melo wrote:
> .
> But one question: when you test build, do you have any extra devel
> packages installed besides what is in this prebuilt toolchain tarball?
No - not when doing this with minimal cross tools - we do have Buildroot where
libelf and zlib as cross devel packages.
> I'll add at least zlib and elfutils to the mix, building it in the
> docker image creation process, and then testing with/without
> NO_LIBELF=1, as I do to other cross-building images:
But that won't work with tools you got now - I can have someone provide you
prebuilt tools off of Buildroot with those packages included. Or if you could be
arsed that is really easy to do off upstream buildroot :-)
>
>> Thx a bunch for doing this Arnaldo - CROSS build and uclibc had a tendency to
>> break here and there so this will catch errors early.
> Hopefully this is something of the past :-)
Cool stuff - thx once again !
-Vineet
next prev parent reply other threads:[~2016-08-19 20:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 20:00 Vineet Gupta
2016-08-18 14:07 ` Arnaldo Carvalho de Melo
2016-08-18 16:03 ` Vineet Gupta
2016-08-18 16:17 ` Arnaldo Carvalho de Melo
2016-08-19 14:22 ` Arnaldo Carvalho de Melo
2016-08-19 18:01 ` Vineet Gupta
2016-08-19 19:23 ` Arnaldo Carvalho de Melo
2016-08-19 20:09 ` Vineet Gupta [this message]
2016-08-19 21:10 ` Arnaldo Carvalho de Melo
2016-08-19 21:27 ` Vineet Gupta
2016-08-19 21:42 ` Arnaldo Carvalho de Melo
2016-08-19 23:02 ` Arnaldo Carvalho de Melo
2016-08-22 18:01 ` Alexey Brodkin
2016-08-22 18:08 ` Arnaldo Carvalho de Melo
2016-08-18 16:28 ` [PATCH v2] " Vineet Gupta
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=45c665be-5965-32d9-b32b-b55c0cd29435@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=pgynther@google.com \
--cc=wangnan0@huawei.com \
/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
all inboxes | Powered by JetHome®