public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Zorrilla Mikel Joseba" <MJZorrilla@ikerlan.es>
To: "David LONY" <david.lony@pragmadev.com>,
		<ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] eCos in Windows
Date: Wed, 16 May 2007 07:35:00 -0000	[thread overview]
Message-ID: <CD298C1118B2474D82316D2DA7D2D41B651934@korreo.ikerlan.es> (raw)

I can not do ecosconfig new pc for example, the warning is always

>David LONY says
>
>I have the same warning when I make a : ecosconfig list But I can compile eCos without any problem...
>These warnings prevents you to compile eCos or not?
>
>David


>Zorrilla Mikel Joseba a écrit :
>  
>
>
> I did it as,
>
> export ECOS_REPOSITORY=/cygdrive/d/eCos/ecos-2.0/packages
>
> David LONY says
>
> Hi,
>
> Do you export the ECOS_REPOSITORY variable ?
> If not, you have to export this variable in your .bashrc file (for 
> instance or directly in your cygwin bash)
>
> Best regards
> David
>
> Zorrilla Mikel Joseba a écrit :
>   
>> 	Hello, I installed eCos with Cygwin in a Windows XP. All the 
>> instalations seems to be ok, but when I try to use the configtool or 
>> when I use ecosconfig, it says me that it doesn't find some packages.
>> I send you a picture to you you the problem.
>>
>> 	What can I do?
>>
>> 	Thank you very much, Mikel.
>>   
>>




--
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:[~2007-05-16  7:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16  7:35 Zorrilla Mikel Joseba [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-05-15 12:49 Zorrilla Mikel Joseba
2007-05-15 13:14 ` David LONY

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=CD298C1118B2474D82316D2DA7D2D41B651934@korreo.ikerlan.es \
    --to=mjzorrilla@ikerlan.es \
    --cc=david.lony@pragmadev.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).