public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kai Ruottu <karuottu@mbnet.fi>
To: kiran Pakala <kiran.pakala@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: crosscompiler host = i686 linux-gnu(athlon) ,target = dec alpha  (for producing tru64 alpha binaries)
Date: Fri, 07 Jul 2006 13:14:00 -0000	[thread overview]
Message-ID: <44AE60CD.2080308@mbnet.fi> (raw)
In-Reply-To: <53947dfa0607061801j29e8ef10ue039e88358175f3d@mail.gmail.com>

kiran Pakala kirjoitti:
> Dear Sir/Madam
>
> I have been struggling to find a easy to use document for cross
> compiler that produces tru64 alpha binaries on my i686 athlon
> linux-gnu workstation.I have tried Dan kegel's crosstool but it has
> somthing for alpha but not dec alpha.Please help me out.
 There seems to be some kind of misunderstanding...   In a rather
long private email I tried to explain Kiran that it would be better
first to tell what on earth he really needs: to produce "binaries"
(only "objects", '.o' files), or "executables" ('.exe' on windows,
binary files with the 'x' right on Unix).  Without first telling this
simple thing, it would be quite hard to get any progress with this
thing...  But that seemingly failed miserably.

 Producing a full crosscompiler for 'alpha-dec-osf*' was discussed
recently on this maillist. And it  being impossible  for some time
because the GNU binutils don't work with these targets.  Native
GCCs could be  fully possible when they can use the native DEC
(HP/Compaq) binutils.  And especially they have the native C
library there!   A crosscompiler maker can thing GCC having
"everything" for a "compiler", also the GNU docs try to tell this
kind of "misinformation" without maybe nobody else but me
caring about this :-(    A newbie  usually thinks a compiler
being something like MSVC or BCC on Windoze.  Or the Cygwin
and  MinGW on the Windoze...  Or the  "GCC" on Linux...  That
the Linux's "glibc" is not a part of "GCC" seems to be something
totally weird!

 So could someone beside me try to tell these ugly facts about
GCC to Kiran so that he/she could understand it?  Maybe he
thinks me being a madman/wackoo when claiming things like
these...

 The "cross compiler that produces tru64 alpha binaries on my
i686 athlon linux-gnu workstation" is far from being clear.  And
not telling whether he/she has the required C library for the
target or what could be the goal anyway, can really make one
becoming that madman/wackoo after trying vain to tell any
facts about "producing binaries" with GCC :-)

      reply	other threads:[~2006-07-07 13:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07  1:01 kiran Pakala
2006-07-07 13:14 ` Kai Ruottu [this message]

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=44AE60CD.2080308@mbnet.fi \
    --to=karuottu@mbnet.fi \
    --cc=gcc-help@gcc.gnu.org \
    --cc=kiran.pakala@gmail.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).