linux-snps-arc.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: acme@kernel.org (Arnaldo Carvalho de Melo)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH] tools lib: Reinstate strlcpy() header guard with __UCLIBC__
Date: Fri, 19 Aug 2016 20:02:10 -0300	[thread overview]
Message-ID: <20160819230210.GD20810@kernel.org> (raw)
In-Reply-To: <20160819214207.GC20810@kernel.org>

Em Fri, Aug 19, 2016 at 06:42:07PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Fri, Aug 19, 2016 at 02:27:58PM -0700, Vineet Gupta escreveu:
> > On 08/19/2016 02:10 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?
> > >> > 
> > >> > 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:
> > > Trying to build elfutils 0.166:
> > >
> > > checking whether gcc accepts -Wduplicated-cond... no
> > > checking whether gcc accepts -Wnull-dereference... no
> > > configure: WARNING: "libc does not have argp"
> > > checking for argp_parse in -largp... no
> > > configure: error: "no libargp found"
> > >
> > > ----
> > >
> > > will go errands now, will try to check what is needed to build elfutils
> > > with uclibc, ideas?
> > 
> > So back in 3.2 days I ran into these issues with elfutils - the workaround was to
> > use the standalone libelf
> > http://www.mr511.de/software/libelf-0.8.9.tar.gz.
> 
> Ok, so I'll git it a try with libelf, lets see...

Argh, give up, now it is refusing to build shared libraries:

  checking for native ELF system... no
  configure: warning: shared libraries not supported for arc-snps-linux-uclibc

And also it says ELF64 isn't support and thus GElf, some more details,
anyway.
  
> > Not sure if you will be willing to take that path.
> > 
> > OTOH, you could use standalone argp @ http://www.lysator.liu.se/~nisse/archive but
> > it seems that requires a bunch of patches too - from looking into the

> > corresponding buildroot package folder. Give this a shot - otherwise it is easier
> > to just build a custom toolchain with pre-req packages from buildroot. Or can be
> > provided if you so deem fit !

Please, if you do that, then I'll be able to test more stuff, I already
had enough fun trying to get elfutils, argp-standalone and libelf built
on this env :-\

- Arnaldo

  reply	other threads:[~2016-08-19 23:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17 20:00 [PATCH] tools lib: Reinstate strlcpy() header guard with __UCLIBC__ 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
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 [this message]
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=20160819230210.GD20810@kernel.org \
    --to=acme@kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).