public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Vaprel" <imasde@vaprel.es>
To: help-gcc@gnu.org
Subject: RE: cross (m68k) compiler troubles
Date: Tue, 04 Jan 2000 07:10:00 -0000	[thread overview]
Message-ID: <84t1pk$20g$1@talia.mad.ttd.net> (raw)
In-Reply-To: <Pine.GSO.4.05.10001040528310.1632-100000@mats>

Hello Frank,

I've just read your msg. and I'd be interested
in your mini-mini-HOWTO about to build a m68k cross-gcc. Would you
care to send me this doc. I'm designing a prototype with a M68332 and
I would like to learn someting about to build a cross-gcc.

Many thanks in advace,

Mario Navarro
@:-)


Frank Meurer <frank@mats.gmd.STOP-UCE.de> escribió en el mensaje de noticias
Pine.GSO.4.05.10001040528310.1632-100000@mats...

> Hello,
> I've build a Linux-i386 to Linux-m68k cross-gcc some days ago without
> problems.
> I've made a mini-mini-HOWTO and will send it to you.
>
> Frank
>



WARNING: multiple messages have this Message-ID

From: "Vaprel" <imasde@vaprel.es>
To: help-gcc@gnu.org
Subject: RE: cross (m68k) compiler troubles
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <84t1pk$20g$1@talia.mad.ttd.net> (raw)
Message-ID: <20000401000000.if3yjGFZVNAlty-ylqADhNl2zm1v0SS-B5413a9w2jQ@z> (raw)
In-Reply-To: <Pine.GSO.4.05.10001040528310.1632-100000@mats>

Hello Frank,

I've just read your msg. and I'd be interested
in your mini-mini-HOWTO about to build a m68k cross-gcc. Would you
care to send me this doc. I'm designing a prototype with a M68332 and
I would like to learn someting about to build a cross-gcc.

Many thanks in advace,

Mario Navarro
@:-)


Frank Meurer <frank@mats.gmd.STOP-UCE.de> escribió en el mensaje de noticias
Pine.GSO.4.05.10001040528310.1632-100000@mats...

> Hello,
> I've build a Linux-i386 to Linux-m68k cross-gcc some days ago without
> problems.
> I've made a mini-mini-HOWTO and will send it to you.
>
> Frank
>



  reply	other threads:[~2000-01-04  7:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-03 15:46 Jeff Singer
2000-01-03 20:35 ` Frank Meurer
2000-01-04  7:10   ` Vaprel [this message]
2000-01-05 12:42     ` Frank Meurer
2000-04-01  0:00       ` Frank Meurer
2000-04-01  0:00     ` Vaprel
2000-04-01  0:00   ` Frank Meurer
2000-01-06 13:06 ` Jeff Singer
2000-04-01  0:00   ` Jeff Singer
2000-04-01  0:00 ` Jeff Singer

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='84t1pk$20g$1@talia.mad.ttd.net' \
    --to=imasde@vaprel.es \
    --cc=help-gcc@gnu.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).