From: "John Dallaway" <jld@ecoscentric.com>
To: kjhales@catalpatechnology.com
Cc: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: newbie help
Date: Sun, 13 Jul 2008 07:30:00 -0000 [thread overview]
Message-ID: <63341.81.102.136.19.1215934157.squirrel@www.ecoscentric.com> (raw)
In-Reply-To:
kjhales wrote:
> I am investigating eCos for use in an upcoming project and I'm having
> trouble getting started. I'm using Fedora, and I'm trying to target an
> i386 system. My real target is different, but this is a good starting
> place.
[ snip ]
> -------begin output
> make -r -C hal/common/v2_0
> /home/kevin/ecos/project/test3_install/lib/extras.o
> make[1]: Entering directory
> `/home/kevin/ecos/project/test3_build/hal/common/v2_0'
> i386-elf-gcc -Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef
> -Woverloaded-virtual -g -O2 -ffunction-sections -fdata-sections
> -fno-rtti -fno-exceptions -fvtable-gc -finit-priority -nostdlib -Wl,-r
> -Wl,--whole-archive -o
> /home/kevin/ecos/project/test3_install/lib/extras.o
> /home/kevin/ecos/project/test3_install/lib/libextras.a
> make[1]: Leaving directory
> `/home/kevin/ecos/project/test3_build/hal/common/v2_0'
> tail: cannot open `+2' for reading: No such file or directory
> ---------end output
The problem lies with the use of "tail +2" within
hal/common/v2_0/cdl/hal.cdl. This syntax is no longer supported within
recent versions of the "tail" tool. You must use "tail -n +2" instead.
eCos 2.0 is now very old. I recommend that you use the eCos anonymous CVS
repository (where this problem is already resolved) instead:
http://ecos.sourceware.org/anoncvs.html
John Dallaway
eCos Maintainer
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2008-07-13 7:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=63341.81.102.136.19.1215934157.squirrel@www.ecoscentric.com \
--to=jld@ecoscentric.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=kjhales@catalpatechnology.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).