From: "oliver munz @ s p e a g" <munz@speag.ch>
To: "Marco Aurélio da Cruz" <marco@daruma.com.br>,
ecos-discuss@sourceware.org
Subject: Re: [ECOS] eCos and GCC 4.1.0
Date: Mon, 27 Mar 2006 17:38:00 -0000 [thread overview]
Message-ID: <039401c651c0$bdc8ec30$5a188481@haus.hellmutstrasse.ch> (raw)
In-Reply-To: <44280312.3010300@daruma.com.br>
Go to the "ecos" directory (where the packages is located).
and do:
cvs -d :pserver:anoncvs@ecos.sourceware.org:/cvs/ecos diff -u packages >
packages.01.diff
You then get all modifications in the packages.01.diff
----- Original Message -----
From: "Marco Aurélio da Cruz" <marco@daruma.com.br>
To: <ecos-discuss@sourceware.org>
Sent: Monday, March 27, 2006 5:21 PM
Subject: Re: [ECOS] eCos and GCC 4.1.0
> I've read some messages about doing this but I'm not aware how to...
>
> I edited my local /packages/kernel/current/include files, changed the
> /packages/kernel/current/ChangLog but I'm not able to generate the diff
> file. I'm so newbie with CVS and patches...
>
> Marco
>
> Andrew Lunn wrote:
>> On Fri, Mar 24, 2006 at 03:33:37PM -0300, Marco Aur?lio da Cruz wrote:
>>
>>> Hi.
>>> I've downloaded the ecos-trunk-20060319 snapshot from eCoscentric and
>>> tried to compile it on arm-elf-gcc 4.1.0.
>>>
>>> I got the errors below:
>>>
>>> .../include/cyg/kernel/sched.hxx:181: error: extra qualification
>>> 'Cyg_Scheduler::' on member 'thread_entry'
>>> .../include/cyg/kernel/thread.hxx:315: error: extra qualification
>>> 'Cyg_Thread::' on member 'reinitialize'
>>>
>>> I edited the files in /packages/kernel/current/include and removed the
>>> qualifiers. So it compiled OK.
>>>
>>> sched.hxx
>>>
>>> from:
>>> /// perform thread startup housekeeping/
>>> void Cyg_Scheduler::thread_entry( Cyg_Thread *thread );
>>>
>>> to:
>>> /// perform thread startup housekeeping/
>>> void thread_entry( Cyg_Thread *thread );
>>>
>>>
>>> thread.hxx
>>>
>>> from:
>>> /// Re-initialize the thread back to it's initial state./
>>> void Cyg_Thread::reinitialize();
>>>
>>> to:
>>> /// Re-initialize the thread back to it's initial state./
>>> void reinitialize();
>>>
>>>
>>> Regards
>>>
>>> Marco Cruz
>>>
>>
>> Please could you produce a proper patch, with ChangeLog entries.
>>
>> Thanks
>> Andrew
>>
>>
>>
>>
>
> --
> Marco Aurélio da Cruz
>
> Depto. de Automação
> Divisão de Tecnologia
> Daruma Urmet S.A.
> Tel.: +55 12 3609-5105
> Fax: +55 12 3609-5156
> Web: http://www.daruma.com.br
>
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-03-27 17:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 18:49 Marco Aurélio da Cruz
2006-03-26 22:54 ` Andrew Lunn
2006-03-27 16:40 ` Marco Aurélio da Cruz
2006-03-27 17:38 ` oliver munz @ s p e a g [this message]
2006-03-28 0:30 ` Marco Aurélio da Cruz
2006-03-28 12:38 ` Jonathan Larmour
2007-12-14 9:47 ` [ECOS] eCos and GCC 4.1.1 venumadhav
2007-12-14 10:29 ` Andrew Lunn
[not found] ` <CBE0A8E1D067704EA75C8D910F98B93D01E611E7@HYD-MKD-MBX01.wipro.com>
2007-12-17 18:39 ` [ECOS] Ecos " Andrew Lunn
2007-12-14 10:38 ` [ECOS] eCos " Paul D. DeRocco
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='039401c651c0$bdc8ec30$5a188481@haus.hellmutstrasse.ch' \
--to=munz@speag.ch \
--cc=ecos-discuss@sourceware.org \
--cc=marco@daruma.com.br \
/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).