From: Frank Meurer <frank@mats.gmd.STOP-UCE.de>
To: help-gcc@gnu.org
Subject: Re: cross (m68k) compiler troubles
Date: Mon, 03 Jan 2000 20:35:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.05.10001040528310.1632-100000@mats> (raw)
In-Reply-To: <387130B8.6ED34915@plex-inc.com>
On Mon, 3 Jan 2000, Jeff Singer wrote:
> Hi - I'm trying to create a cross compiler for an m68k platform from a
> celeron host. I'm having no end of trouble just getting through the
> make process without errors. I am usually able to get the binutils to
> compile completely, but get errors when making gcc for the m68k. I've
> tried several --prefix settings and other things with no luck. Usually
> the errors involve make being unable to find some file (different files
> each time) which makes me suspect I haven't specified/created the right
> directory structure for the install. Is there a de-facto/standard
> structure which the makefile assumes? Are all the errors critical? Any
> help at all would be greatly appreciated.
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
-------------------------------------------------------------------------
We have joy, we have fun, we have Linux on our SUN.
Sending unsolicited commercial email to this address may be a violation
of the Washington State Consumer Protection Act, chapter 19.86 RCW.
Das Verschicken unverlangter kommerzieller email an diese Adresse ist
verboten (LG Traunstein, 2 HK O 3755/97 vom 14.10.1997, CR 1998, 171f).
WARNING: multiple messages have this Message-ID
From: Frank Meurer <frank@mats.gmd.STOP-UCE.de>
To: help-gcc@gnu.org
Subject: Re: cross (m68k) compiler troubles
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.05.10001040528310.1632-100000@mats> (raw)
Message-ID: <20000401000000.yVJ7q9x6gWZZ8PemzZwH5fKgcLLBelXEF6P3sf8a_SU@z> (raw)
In-Reply-To: <387130B8.6ED34915@plex-inc.com>
On Mon, 3 Jan 2000, Jeff Singer wrote:
> Hi - I'm trying to create a cross compiler for an m68k platform from a
> celeron host. I'm having no end of trouble just getting through the
> make process without errors. I am usually able to get the binutils to
> compile completely, but get errors when making gcc for the m68k. I've
> tried several --prefix settings and other things with no luck. Usually
> the errors involve make being unable to find some file (different files
> each time) which makes me suspect I haven't specified/created the right
> directory structure for the install. Is there a de-facto/standard
> structure which the makefile assumes? Are all the errors critical? Any
> help at all would be greatly appreciated.
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
-------------------------------------------------------------------------
We have joy, we have fun, we have Linux on our SUN.
Sending unsolicited commercial email to this address may be a violation
of the Washington State Consumer Protection Act, chapter 19.86 RCW.
Das Verschicken unverlangter kommerzieller email an diese Adresse ist
verboten (LG Traunstein, 2 HK O 3755/97 vom 14.10.1997, CR 1998, 171f).
next prev parent reply other threads:[~2000-01-03 20:35 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 [this message]
2000-01-04 7:10 ` Vaprel
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=Pine.GSO.4.05.10001040528310.1632-100000@mats \
--to=frank@mats.gmd.stop-uce.de \
--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).