public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Vaughan Daly \(Mpos\)" <vaughan@mpos.net>
To: "Trenton D. Adams" <tadams@extremeeng.com>,
	"'Jonathan Larmour'" <jlarmour@redhat.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] GCC Build error
Date: Fri, 03 Aug 2001 17:28:00 -0000	[thread overview]
Message-ID: <003701c11c7b$b2af1ba0$cb4369ca@ocsdev99> (raw)
In-Reply-To: <000201c11c2c$ad284200$090110ac@TRENT>

HI Trenton

Thanks for the reply, I think that I should have been a little more
informative, as to what OS etc I use. I was compiling under WIN2K. Pretty
strange. The page that Jonathan pointed me to, seems to have sorted out the
problem. It appears to be a formatting error in one of the files of some
sort. Anyway, it compiles fine now.

Thanks for all the help and pointers.

Vaughan

----- Original Message -----
From: "Trenton D. Adams" <tadams@extremeeng.com>
To: "'Jonathan Larmour'" <jlarmour@redhat.com>; "'Vaughan Daly (Mpos)'"
<vaughan@mpos.net>
Cc: <ecos-discuss@sources.redhat.com>
Sent: Friday, August 03, 2001 10:57 PM
Subject: RE: [ECOS] GCC Build error


> What the hell?  I clicked reply on this one!!! Maybe I am delusional!
>
> I had a similar problem whenever I tried compiling for cygwin under
> Windows 98.  The i386 tools compiled fine, but my cross compiler would
> not compile because of a "parse error".  It's almost as if the patch
> applied to GCC doesn't work properly when using windows 98 or something
> like that.  However, the i386 patch for GCC worked just fine.
>
> The process I used for compiling the tools was completely exactly the
> same between windows 98 and windows 2000.  I used a script so I know
> this for a fact.  It worked fine in windows 2000.
>
> Anyhow, I really have no idea because I never bothered to figure it out.
>
> Does this sound weird?  Am I possibly delusional?
>
>   > -----Original Message-----
>   > From: ecos-discuss-owner@sources.redhat.com [ mailto:ecos-discuss-
>   > owner@sources.redhat.com] On Behalf Of Jonathan Larmour
>   > Sent: Friday, August 03, 2001 7:09 AM
>   > To: Vaughan Daly (Mpos)
>   > Cc: ecos-discuss@sources.redhat.com
>   > Subject: Re: [ECOS] GCC Build error
>   >
>   > "Vaughan Daly (Mpos)" wrote:
>   > >
>   > > Hi All
>   > >
>   > > For some unknown reason to myself I can't seem to build the gcc
> cross
>   > > compiler for ecos. I keep getting the error as below, can someone
>   > please
>   > > point me in the right direction, I have gone through the build of
> the
>   > > binutils and gcc 3 times now with no difference. I need a pointer
> in
>   > the
>   > > right direction please.
>   >
>   > Probably the same problem as this:
>   > http://sources.redhat.com/ml/ecos-discuss/2001-07/msg00793.html
>   >
>   > Jifl
>   > --
>   > Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223)
>   > 271062
>   > Maybe this world is another planet's Hell -Aldous Huxley ||
>   > Opinions==mine
>
>


  reply	other threads:[~2001-08-03 17:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-03  0:45 Vaughan Daly (Mpos)
2001-08-03  6:08 ` Jonathan Larmour
2001-08-03  7:58   ` Trenton D. Adams
2001-08-03 17:28     ` Vaughan Daly (Mpos) [this message]
2001-08-03 17:28   ` Vaughan Daly (Mpos)

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='003701c11c7b$b2af1ba0$cb4369ca@ocsdev99' \
    --to=vaughan@mpos.net \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jlarmour@redhat.com \
    --cc=tadams@extremeeng.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).