public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Y.P.Liu." <86321019@stu.csie.ncnu.edu.tw>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Build problem "Hellow world " in i386& win2000
Date: Fri, 03 Aug 2001 13:54:00 -0000	[thread overview]
Message-ID: <20010804022955.D5D8.86321019@stu.csie.ncnu.edu.tw> (raw)
In-Reply-To: <20010802141847.0B52.86321019@stu.csie.ncnu.edu.tw>

Thanks with your help.
I use the step which you tell me
-----------------
type i386-elf-gcc -g -I/ework/ework_install/include hello.c
 -L/ework/ework_install/lib -Ttarget.ld -nostdlib
-----------------
but I still can't work it correctly.

ps. this is my error message
----------------------------------
bash.exe-2.05$ i386-elf-gcc -g -I/ework/ework_install/include hello.c -L/ework/
ework_install/lib -Ttarget.ld -nostdlib
In file included from /ework/ework_install/include/stdio.h:56,
                 from hello.c:2:
/ework/ework_install/include/cyg/infra/cyg_type.h:160: parse error before `__tmp
1'
/ework/ework_install/include/cyg/infra/cyg_type.h:160: `_name_' undeclared here
(not in a function)
/ework/ework_install/include/cyg/infra/cyg_type.h:160: warning: data definition
has no type or storage class
/ework/ework_install/include/cyg/infra/cyg_type.h:161: parse error before `__tmp
2'
/ework/ework_install/include/cyg/infra/cyg_type.h:161: initializer element is no
t constant
/ework/ework_install/include/cyg/infra/cyg_type.h:161: warning: data definition
has no type or storage class
/ework/ework_install/include/cyg/infra/cyg_type.h:162: redefinition of `__tmp1'
/ework/ework_install/include/cyg/infra/cyg_type.h:160: `__tmp1' previously defin
ed here
/ework/ework_install/include/cyg/infra/cyg_type.h:162: initializer element is no
t constant
/ework/ework_install/include/cyg/infra/cyg_type.h:162: warning: data definition
has no type or storage class
/ework/ework_install/include/cyg/infra/cyg_type.h:163: parse error before `}'
/ework/ework_install/include/cyg/infra/cyg_type.h:223: parse error before `CYG_B
YTE'
/ework/ework_install/include/cyg/infra/cyg_type.h:223: warning: data definition
has no type or storage class
/ework/ework_install/include/cyg/infra/cyg_type.h:282: parse error before `#'
/ework/ework_install/include/cyg/infra/cyg_type.h:317: stray '\' in program
/ework/ework_install/include/cyg/infra/cyg_type.h:341: warning: This file contai
ns more `}'s than `{'s.
In file included from /ework/ework_install/include/stdio.h:58,
                 from hello.c:2:
/tools/H-i686-pc-cygwin/lib/gcc-lib/i386-elf/2.95.2/include/stdarg.h:99: warning
: parameter names (without types) in function declaration
/tools/H-i686-pc-cygwin/lib/gcc-lib/i386-elf/2.95.2/include/stdarg.h:188: parse
error before `va_list'
/tools/H-i686-pc-cygwin/lib/gcc-lib/i386-elf/2.95.2/include/stdarg.h:188: warnin
g: data definition has no type or storage class
In file included from hello.c:2:
/ework/ework_install/include/stdio.h:174: parse error before `va_list'
/ework/ework_install/include/stdio.h:177: parse error before `va_list'
/ework/ework_install/include/stdio.h:181: parse error before `va_list'
/ework/ework_install/include/stdio.h:270: parse error before `va_list'
/ework/ework_install/include/stdio.h:274: parse error before `va_list'
/ework/ework_install/include/stdio.h:277: parse error before `va_list'
/ework/ework_install/include/stdio.h:281: parse error before `va_list'
/ework/ework_install/include/stdio.h:285: parse error before `va_list'
In file included from /ework/ework_install/include/stdio.h:291,
                 from hello.c:2:
/ework/ework_install/include/stdio.inl:88: parse error before `va_list'
/ework/ework_install/include/stdio.inl: In function `vfprintf':
/ework/ework_install/include/stdio.inl:90: `stream' undeclared (first use in thi
s function)
/ework/ework_install/include/stdio.inl:90: (Each undeclared identifier is report
ed only once
/ework/ework_install/include/stdio.inl:90: for each function it appears in.)
/ework/ework_install/include/stdio.inl:90: `format' undeclared (first use in thi
s function)
/ework/ework_install/include/stdio.inl:90: `arg' undeclared (first use in this f
unction)
/ework/ework_install/include/stdio.inl: At top level:
/ework/ework_install/include/stdio.inl:95: parse error before `va_list'
/ework/ework_install/include/stdio.inl: In function `vprintf':
/ework/ework_install/include/stdio.inl:97: `format' undeclared (first use in thi
s function)
/ework/ework_install/include/stdio.inl:97: `arg' undeclared (first use in this f
unction)
/ework/ework_install/include/stdio.inl: At top level:
/ework/ework_install/include/stdio.inl:102: parse error before `va_list'
/ework/ework_install/include/stdio.inl: In function `vsprintf':
/ework/ework_install/include/stdio.inl:104: `s' undeclared (first use in this fu
nction)
/ework/ework_install/include/stdio.inl:104: `format' undeclared (first use in th
is function)
/ework/ework_install/include/stdio.inl:104: `arg' undeclared (first use in this
function)
/ework/ework_install/include/stdio.inl: At top level:
/ework/ework_install/include/stdio.inl:145: parse error before `va_list'
/ework/ework_install/include/stdio.inl: In function `vscanf':
/ework/ework_install/include/stdio.inl:147: `format' undeclared (first use in th
is function)
/ework/ework_install/include/stdio.inl:147: `arg' undeclared (first use in this
function)
In file included from hello.c:2:
hello.c: At top level:
/ework/ework_install/include/stdio.h:299: warning: This file contains more `}'s
than `{'s.
bash.exe-2.05$
-------------------------------------
Is there any problem ?
-- 
Y.P.Liu. <u6321019@ncnu.edu.tw>

  reply	other threads:[~2001-08-03 13:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02  3:22 [ECOS] Build problem Y.P.Liu.
2001-08-03 13:54 ` Y.P.Liu. [this message]
2001-08-03 14:00   ` [ECOS] Build problem "Hellow world " in i386& win2000 Jonathan Larmour

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=20010804022955.D5D8.86321019@stu.csie.ncnu.edu.tw \
    --to=86321019@stu.csie.ncnu.edu.tw \
    --cc=ecos-discuss@sources.redhat.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).