[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45c665be-5965-32d9-b32b-b55c0cd29435@synopsys.com>
Date: Fri, 19 Aug 2016 13:09:51 -0700
From: Vineet Gupta <Vineet.Gupta1@...opsys.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
CC: Wang Nan <wangnan0@...wei.com>, David Ahern <dsahern@...il.com>,
"Peter Zijlstra" <peterz@...radead.org>,
Alexey Brodkin <Alexey.Brodkin@...opsys.com>,
Adrian Hunter <adrian.hunter@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Arnaldo Carvalho de Melo" <acme@...hat.com>,
Petri Gynther <pgynther@...gle.com>,
Jiri Olsa <jolsa@...nel.org>,
osh Poimboeuf <jpoimboe@...hat.com>,
"Namhyung Kim" <namhyung@...nel.org>,
"linux-snps-arc@...ts.infradead.org"
<linux-snps-arc@...ts.infradead.org>
Subject: Re: [PATCH] tools lib: Reinstate strlcpy() header guard with
__UCLIBC__
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
Powered by blists - more mailing lists