public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gthomas@cambridge.redhat.com>
To: Victor Tarasov <victor.tarasov@idealx.com>
Cc: eCos Discussion <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Hello_eCos_World on iPAQ.
Date: Tue, 24 Apr 2001 05:54:00 -0000	[thread overview]
Message-ID: <XFMail.20010424055627.gthomas@cambridge.redhat.com> (raw)
In-Reply-To: <3AE5384E.779252B@idealx.com>

Note: email which is not sent to the discussion list (or at least copied to it)
will be automatically discarded from now on.  Please use the list.

On 24-Apr-2001 Victor Tarasov wrote:
> Thank you very much for the attention.
> 
> Gary Thomas wrote:
> 
>> This is probably not what you really wanted to do.  You'll need to build
>> a separate configuration just for the 'hello' program, like this (in a
>> directory just for this):
>>   % mkdir /tmp/ipaq_ecos
>>   % cd /tmp/ipaq_ecos
>>   % ecosconfig new ipaq
>>   % ecosconfig tree
>>   % make
> 
> I tried this sequence also. During the compilation of the libraries it looks for:
>>packages/devs/touch/arm/ipaq/current/src/ipaq_ts.c:57: cyg/fileio/fileio.h: No
> such file or directory
> 
> The only fileio.h that I found in the CVS distribution is
> packages/io/fileio/current/include/fileio.h,
> so, I added it manually to the install directory, but afterwards it looks for
> pkgconf/io_fileio.h
> That one, I have not found in the CVS distribution.
> 

Yes, there was a problem here.  This can be fixed by adding the command
  % ecosconfig add fileio
just before the 'ecosconfig tree' line.

> 
>> > PS: How can I recompile RedBoot for iPAQ?
>> > "RedBoot" template with the imported configuration
>> > $ECOS_REPOSITORY/packages/hal/arm/sa11x0/ipaq/current/misc/redboot_Compaq.ecm
>> > (also redboot_rom.ecm)
>> > gives the binaries that are not working on the iPAQ.
>> > The templates "all", "default" and "stubs" give the error during
>> > compilation.
>>
>> Why do you want to recompile RedBoot?
> 
> It's  some kind of  desparate action:
> before to dive deeply into the investigation of eCos and its configuration options
> ,
> I would like to have something  that was compiled and is working on iPAQ.
> (That's why I was asking you for the configuration for the building of  the
> ipaq_Compaq.bin,
> that you sent me recently. In the CVS the ECMs for ipaq were not updated.)

There were no changes required to that file for the fixes I made.  Here's how
to build that file:
  % ecosconfig new ipaq redboot
  % ecosconfig import $ECOS_REPOSITORY/packages/hal/arm/sa11x0/ipaq/current/misc/redboot_Compaq.ecm
  % ecosconfig tree
  % make
The resulting file 'install/bin/redboot.bin' is what is distributed as "redboot.Compaq".

       reply	other threads:[~2001-04-24  5:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3AE5384E.779252B@idealx.com>
2001-04-24  5:54 ` Gary Thomas [this message]
2001-04-24  9:47   ` Jonathan Larmour
2001-04-26  7:30     ` Victor Tarasov
2001-04-26 17:28       ` Gary Thomas
2001-04-30  1:36         ` Victor Tarasov
2001-04-30  5:02           ` Gary Thomas
2001-04-30  8:39             ` Victor Tarasov
2001-04-23 10:04 Victor Tarasov
2001-04-23 10:21 ` Gary Thomas
2001-04-23 10:42 ` 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=XFMail.20010424055627.gthomas@cambridge.redhat.com \
    --to=gthomas@cambridge.redhat.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=victor.tarasov@idealx.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).