public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christophe AUSSAGUES <chris@albatros.saclay.cea.fr>
To: gcc-help@gcc.gnu.org
Subject: M68040 GCC compiler building
Date: Mon, 10 Jan 2000 09:29:00 -0000	[thread overview]
Message-ID: <387A172D.506B5072@albatros.saclay.cea.fr> (raw)

Hello,

Before writing a bug report, I would like to be sure that our
difficulties, in building a m68k native compiler, don't come neither
from us nor from the fact that our system is an old one. So, I prefer
sending you this question in a first step.

We are trying to install the new GCC version (2.95.2) on a
Motorola-VME167 platform with a M68040 processor and an Unix-SystemV
system (note: the result of 'uname -a' is 'xxx xxx R3V7 980709 M68040').
We encounter some difficulties in making directly a native compiler for
this target machine. Our difficulties are connected with gcc/cc we use
to build the new one.

We have yet succesfully installed two old versions of GCC (the latest
one is 2.7.2) on the Motorola machine. We've also installed without any
problem the 2.95.5 GCC version on our SUN SPARCstations.

So,

 1) I would like to know if there is someone that have yet installed the
2.95.2 GCC version on such a m68040 computer, or if someone has some
advices from its experiments on m68040 computers to solve our
difficulties,


 2) We are now trying to build a M68040 native compiler FROM a
cross-compiler we will build on the SUN computers. Does anybody know if
there exists an easy way to do such an operation ? (and if so, can you
describe it to us ?...)


Thanks in advance for your help,
Christophe Aussagues.
--
mailto:chris@albatros.saclay.cea.fr

WARNING: multiple messages have this Message-ID
From: Christophe AUSSAGUES <chris@albatros.saclay.cea.fr>
To: gcc-help@gcc.gnu.org
Subject: M68040 GCC compiler building
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <387A172D.506B5072@albatros.saclay.cea.fr> (raw)
Message-ID: <20000401000000.7i6dAjG6zFFi1BTm0y98NSnorrppCAvyo5cW7zlZFgI@z> (raw)

Hello,

Before writing a bug report, I would like to be sure that our
difficulties, in building a m68k native compiler, don't come neither
from us nor from the fact that our system is an old one. So, I prefer
sending you this question in a first step.

We are trying to install the new GCC version (2.95.2) on a
Motorola-VME167 platform with a M68040 processor and an Unix-SystemV
system (note: the result of 'uname -a' is 'xxx xxx R3V7 980709 M68040').
We encounter some difficulties in making directly a native compiler for
this target machine. Our difficulties are connected with gcc/cc we use
to build the new one.

We have yet succesfully installed two old versions of GCC (the latest
one is 2.7.2) on the Motorola machine. We've also installed without any
problem the 2.95.5 GCC version on our SUN SPARCstations.

So,

 1) I would like to know if there is someone that have yet installed the
2.95.2 GCC version on such a m68040 computer, or if someone has some
advices from its experiments on m68040 computers to solve our
difficulties,


 2) We are now trying to build a M68040 native compiler FROM a
cross-compiler we will build on the SUN computers. Does anybody know if
there exists an easy way to do such an operation ? (and if so, can you
describe it to us ?...)


Thanks in advance for your help,
Christophe Aussagues.
--
mailto:chris@albatros.saclay.cea.fr

             reply	other threads:[~2000-01-10  9:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-10  9:29 Christophe AUSSAGUES [this message]
2000-04-01  0:00 ` Christophe AUSSAGUES

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=387A172D.506B5072@albatros.saclay.cea.fr \
    --to=chris@albatros.saclay.cea.fr \
    --cc=gcc-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).