From: "ariga masahiro" <ariga@link-lab.co.jp>
To: "jiang jet" <jetjiang@hotmail.com>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Why strncasecmp' undeclared
Date: Wed, 30 May 2007 11:18:00 -0000 [thread overview]
Message-ID: <000e01c7a281$b23c36c0$1c0110ac@ariga> (raw)
In-Reply-To: <BAY137-F494912C3E75596B547CC5DF2E0@phx.gbl>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; format=flowed; charset="gb2312"; reply-type=response, Size: 2517 bytes --]
Thank you jiang,
Thank you reply.
I first included <string.h>,next <strings.h> but
both resulted in same errors.
As far as I used [default] in configtool's [Packages]dropdownlist.
Although I changed to [net] in configtool's [Packages]dropdownlist,
then appeared no same errors.
Of course I still not fathomed intricasies of eCos.
If I want to know [Packages]dropdownlist more thoroughly,
where do you recommend to refer to?
Masahiro Ariga
----- Original Message -----
From: "jiang jet" <jetjiang@hotmail.com>
To: <ariga@link-lab.co.jp>
Cc: <ecos-discuss@ecos.sourceware.org>
Sent: Wednesday, May 30, 2007 2:45 PM
Subject: RE: [ECOS] Why strncasecmp' undeclared
>
>
>
>
> I love this game : embedded system @_@
> MSN:jetjiang@hotmail.com
>
>
>
>
>
>>From: "ariga masahiro" <ariga@link-lab.co.jp>
>>To: <ecos-discuss@ecos.sourceware.org>
>>Subject: [ECOS] Why strncasecmp' undeclared
>>Date: Wed, 30 May 2007 13:53:05 +0900
>>
>>Hi everyone,
>>
>>I challenged to implement eCos application.
>>
>>First of all I tried to make libtarget.a.
>>I changed Startup Type(CYG_HAL_STARTUP) "RAM".
>>I selected [default] in configtool's [Packages]dropdownlist.
>>
>>Then Bult,and encountered next errors.
>>
>> function `int match_string(const char**, const char**, int)':
>>/opt/ecos/ecos-2.0/packages/language/c/libc/time/v2_0/src/strptime.cxx:89:
>
>>`
>> strncasecmp' undeclared (first use this function)
>>/opt/ecos/ecos-2.0/packages/language/c/libc/time/v2_0/src/strptime.cxx:89:
>
>>(Each
>> undeclared identifier is reported only once for each function it
>> appears
>> in.)
>>
>>I checked strncasecmp function and learned it needs to include
>><strings.h>,
>>so I included <strings.h> in strptime.cxx,but resulted in same errors.
>
> did you include the right header files??
> it should be <string.h> not <strings.h>,
>>
>>I am puzzled.
>>Please help me out of the swamp.
>>
>>Masahiro Ariga
>>
>>
>>--
>>Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
>>and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>>
>
> _________________________________________________________________
> Ãâ·ÑÏÂÔØ MSN Explorer: http://explorer.msn.com/lccn
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-05-30 6:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 5:45 ariga masahiro
2007-05-30 6:13 ` jiang jet
2007-05-30 11:18 ` ariga masahiro [this message]
2007-05-30 11:51 ` Gary Thomas
2007-05-31 2:27 ` ariga masahiro
2007-05-31 5:42 ` ariga masahiro
2007-05-31 13:02 ` Andrew Lunn
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='000e01c7a281$b23c36c0$1c0110ac@ariga' \
--to=ariga@link-lab.co.jp \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=jetjiang@hotmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).