linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: david@gibson.dropbear.id.au (David Gibson)
To: linux-arm-kernel@lists.infradead.org
Subject: Fwd: [robh:dt/next 2/2] fdt_ro.c:undefined reference to `strnlen'
Date: Wed, 27 Jan 2016 09:38:05 +1100	[thread overview]
Message-ID: <20160126223805.GE16692@voom.fritz.box> (raw)
In-Reply-To: <alpine.LFD.2.20.1601261636510.19789@knanqh.ubzr>

On Tue, Jan 26, 2016 at 04:52:18PM -0500, Nicolas Pitre wrote:
> On Tue, 26 Jan 2016, Rob Herring wrote:
> 
> > With the latest dtc I've imported to the kernel, there is a new
> > dependency on strnlen. This is giving the ARM decompressor an error. I
> > have a couple of ideas on how to fix it:
> > 
> > - Move string related functions in dtc to separate file
> > - Add lib/string.c to the decompressor build
> > - Build the decompressor with function-sections to discard the string
> > related functions and avoid the linker error. Also, there's probably a
> > bit of other unused code that would get dropped. function-sections
> > doesn't work for the kernel in general, but may for the decompressor.
> > Nico may know.
> 
> Use of function-sections turns out to be more involved than I wish. And 
> we've put many special restrictions on the decompressor already. And 
> linking dtc (only part of it actually) into the decompressor is only for 
> legacy stuff and I'd prefer we don't spend too much time on legacy 
> stuff.  Yadda yadda.
> 
> So instead I'd simply paste a simple implementation of strnlen into 
> arch/arm/boot/compressed/string.c and be done with it.  The one in 
> lib/string.c looks dead simple for what it's worth.

I think that would be my preferred option too.

> 
> > - Don't update dtc and take the rest of the day off.
> 
> That is always an option.  Does it really need to be updated?  ;-)
> 
> 
> Nicolas

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160127/52124933/attachment.sig>

      reply	other threads:[~2016-01-26 22:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201601270337.wm7hjDwR%fengguang.wu@intel.com>
     [not found] ` <CAL_JsqJ2C=OQa5ntYH3MLQ87+=ELHAtgFpg5QNQpQ0-RgzQeiw@mail.gmail.com>
2016-01-26 21:52   ` Fwd: [robh:dt/next 2/2] fdt_ro.c:undefined reference to `strnlen' Nicolas Pitre
2016-01-26 22:38     ` David Gibson [this message]

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=20160126223805.GE16692@voom.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=linux-arm-kernel@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).