From: Jeff Singer <jdsinger@plex-inc.com>
To: help-gcc@gnu.org
Subject: cross (m68k) compiler troubles
Date: Mon, 03 Jan 2000 15:46:00 -0000 [thread overview]
Message-ID: <387130B8.6ED34915@plex-inc.com> (raw)
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.
Thanks in advance,
Jeff Singer
jdsinger@plex-inc.com
WARNING: multiple messages have this Message-ID
From: Jeff Singer <jdsinger@plex-inc.com>
To: help-gcc@gnu.org
Subject: cross (m68k) compiler troubles
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <387130B8.6ED34915@plex-inc.com> (raw)
Message-ID: <20000401000000.IKNfIsowlTIgp4rdMIj2de_XhKVTT_uM3L309AoiCW4@z> (raw)
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.
Thanks in advance,
Jeff Singer
jdsinger@plex-inc.com
next reply other threads:[~2000-01-03 15:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-03 15:46 Jeff Singer [this message]
2000-01-03 20:35 ` Frank Meurer
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=387130B8.6ED34915@plex-inc.com \
--to=jdsinger@plex-inc.com \
--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).