From: "Grant Likely" <grant.likely@secretlab.ca>
To: dhlii@dlasys.net
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: ARCH=ppc strncmp undefined
Date: Sun, 27 Apr 2008 14:24:49 -0600 [thread overview]
Message-ID: <fa686aa40804271324i71a93a1bv93ad278b960f0c9d@mail.gmail.com> (raw)
In-Reply-To: <4814D35C.9070608@dlasys.net>
On Sun, Apr 27, 2008 at 1:26 PM, David H. Lynch Jr. <dhlii@dlasys.net> wrote:
> After pulling and rebasing to 2.6.25, I get strncmp is undefined
> when I try to link the kernel.
>
> I have not chased this down as just added strncmp into
> arch/ppc/lib/string.S
>
> But I would guess this is a side effect of changes to accomidate
> migration to ARCH=powerpc.
> There appear to be a number of remaining arch/ppc BSP's that need
> strncmp and therefore
> will not build in 2.6.25.
There is a patch to fix this bug:
http://ozlabs.org/pipermail/linuxppc-dev/2008-April/055094.html
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
prev parent reply other threads:[~2008-04-27 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 19:26 ARCH=ppc strncmp undefined David H. Lynch Jr.
2008-04-27 20:24 ` Grant Likely [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=fa686aa40804271324i71a93a1bv93ad278b960f0c9d@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=dhlii@dlasys.net \
--cc=linuxppc-embedded@ozlabs.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).