From: Jonathan Larmour <jlarmour@redhat.com>
To: "adon@walkersun" <adon@walkersun.com>
Cc: ecos-discuss@sources.redhat.com, Alex Mathews <alexma@crosstor.com>
Subject: Re: [ECOS] download fail over I386 target
Date: Fri, 15 Sep 2000 11:05:00 -0000 [thread overview]
Message-ID: <39C264D8.FB1E3C6F@redhat.com> (raw)
In-Reply-To: <000801c01f3d$5ca558a0$46bf41cb@homeadon>
"adon@walkersun" wrote:
>
> But I still got problem with math package while I build default
> template. And when I enable the serial port I also got make error for flow1.
We need more information to go on. I assume that this is the PC target
then? What exact build errors are you seeing - please cut and paste the
relevant portion of the build output.
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault
next prev parent reply other threads:[~2000-09-15 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-15 3:32 adon@walkersun
2000-09-15 7:17 ` Alex Mathews
2000-09-15 10:50 ` adon@walkersun
2000-09-15 11:05 ` Jonathan Larmour [this message]
2000-09-15 11:08 ` Alex Mathews
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=39C264D8.FB1E3C6F@redhat.com \
--to=jlarmour@redhat.com \
--cc=adon@walkersun.com \
--cc=alexma@crosstor.com \
--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).