From: "John Finley" <john@finley.com>
To: "eCos Discussion List" <ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] Building eCos
Date: Wed, 01 Mar 2000 10:24:00 -0000 [thread overview]
Message-ID: <NBBBJGLCELDOBKLDCJLHMEEDCEAA.john@finley.com> (raw)
In-Reply-To: <200003011700.e21H0Aq62955@smtp.abac.com>
> Is anyone building eCos under UNIX ?
>
> If so, is there any documentation that describes how to do this.
>
> If I try to use pkgconf.tcl to configure a build tree I just get:
>
> % gmake
> makefile:9: pkgconf/pkgconf.mak: No such file or directory
> gmake: *** No rule to make target `pkgconf/pkgconf.mak'. Stop.
>
> Robert Swindells
> GenRad Ltd
I think I tried that and decided it was a line-ending
thing. After dos2unixing all the source and make files,
that went away but a different bunch of errors started
popping up. It was as if there was a '\r' at the end of
some of the filenames, so make couldn't find them.
I never did get a full build on Unix, but didn't try
all that hard, since I'm just evaluating this stuff in
my "spare" time. I think my sources at the time were the
latest anoncvs ones (about a week ago), although I might
have been using the ones off the sourceware CD.
John
next parent reply other threads:[~2000-03-01 10:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200003011700.e21H0Aq62955@smtp.abac.com>
2000-03-01 10:24 ` John Finley [this message]
2014-04-02 19:52 kalibar6
-- strict thread matches above, loose matches on Subject: below --
2001-11-13 3:41 [ECOS] RedBoot for Assabet (strongarm) problem todd.kallam
2001-11-13 5:41 ` Jordi Colomer
2001-11-14 20:36 ` [ECOS] Building ecos RolandKane
2001-11-15 4:50 ` Julian Smart
[not found] <200003011701.JAA18830@cygnus.com>
2000-03-01 9:27 ` [ECOS] Building eCos Bart Veer
[not found] <200003011700.JAA18722@cygnus.com>
2000-03-01 9:14 ` Jonathan Larmour
2000-03-01 8:59 Robert Swindells
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=NBBBJGLCELDOBKLDCJLHMEEDCEAA.john@finley.com \
--to=john@finley.com \
--cc=ecos-discuss@sourceware.cygnus.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).