public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: m mariga <ma_ariga@yahoo.co.jp>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: h8300 cannot find libgcc.a
Date: Wed, 22 Jul 2009 13:58:00 -0000	[thread overview]
Message-ID: <4A671AEE.2000101@dallaway.org.uk> (raw)
In-Reply-To: <3F8ED0BDC83C43259ADD0DDE963395DF@masahiro>

Hi

m mariga wrote:

> I asked to gcc mailing list but could not get reply.
> I tried to use GCC 4.4.0 and there was no error,so I am determined to
> use GCC 4.4.0.

[ snip ]

> I downloaded the patch file but it is for use of GCC 3.3 source.
> I also get the same purpose patch file that is for GCC 3.3.2 source.
> I append it in zip file.
> 
> I studied it and learned that I could not use it for GCC 4.4.0 source
> per se.
> I searched Internet for newer patch corresponding to GCC 4.4.0 or at
> least to GCC 4.3.2 but could not find one.
> Couldn't it be possible that you send me the newer patch corresponding
> to GCC 4.4.0 or at least to GCC 4.3.2 ?

I am not aware of a corresponding patch for GCC 4.x, but the necessary
changes should be reasonably easy to make by editing the source files
manually.

Please post the patch when you get this working.

Thanks

John Dallaway

-- 
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:[~2009-07-22 13:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 14:08 [ECOS] " m mariga
2009-07-21 15:04 ` [ECOS] " John Dallaway
2009-07-22 12:28   ` m mariga
2009-07-22 13:58     ` John Dallaway [this message]
2009-07-23 21:32       ` m mariga
2009-07-24  8:34         ` John Dallaway
2009-07-28 14:40           ` m mariga
2009-08-09 23:11             ` m mariga
2009-08-17  7:42               ` John Dallaway
2009-09-04  5:54               ` [ECOS] How to set GDB Stub Options in order to run insight ? m mariga
2009-09-04  9:38                 ` [ECOS] " John Dallaway
2009-09-04 18:33                   ` m mariga
2009-09-07  9:40                     ` m mariga
2009-09-07 11:31                       ` John Dallaway
2009-09-07 16:10                         ` [ECOS] cyg_scheduler_lock and DSR's Jim Bradleigh
2009-09-11 20:37                           ` Bart Veer
2009-09-08 10:15                         ` [ECOS] Re: How to set GDB Stub Options in order to run insight ? m mariga
2009-09-28  9:54                           ` [ECOS] About h8000 eCos GDB-Stub m mariga
2009-09-30 10:06                             ` m mariga
2009-10-16 14:34                               ` [ECOS] How to connect RedBoot via Telnet running application m mariga
2009-10-16 14:42                                 ` Gary Thomas
     [not found]                                   ` <6FC88324D6C144EFB39FFE3CBF0E5B8D@masahiro>
2009-10-16 15:40                                     ` Gary Thomas
2009-10-16 16:11                                       ` m mariga
2009-10-16 16:43                                       ` m mariga
2009-10-16 16:54                                         ` Gary Thomas
2009-09-19  1:51                         ` [ECOS] Re: How to set GDB Stub Options in order to run insight ? m mariga

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=4A671AEE.2000101@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=ma_ariga@yahoo.co.jp \
    /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).