public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Rodrigo Dominguez" <roddomi@hotmail.com>
To: "'Andrew Haley'" <aph@redhat.com>
Cc: "'Martin Guy'" <martinwguy@yahoo.it>, 	<gcc-help@gcc.gnu.org>
Subject: RE: GCC 3.3 binary for XScale
Date: Fri, 29 Feb 2008 16:15:00 -0000	[thread overview]
Message-ID: <BAY129-DAV179A22EF0CFF98E52F8C44B9140@phx.gbl> (raw)
In-Reply-To: <47C82954.2010505@redhat.com>


 

> -----Original Message-----
> From: Andrew Haley [mailto:aph@redhat.com] 
> Sent: Friday, February 29, 2008 10:49 AM
> To: Rodrigo Dominguez
> Cc: 'Martin Guy'; gcc-help@gcc.gnu.org
> Subject: Re: GCC 3.3 binary for XScale
> 
> Rodrigo Dominguez wrote:
> >> -----Original Message-----
> >> From: Andrew Haley [mailto:aph@redhat.com] 
> >> Sent: Friday, February 29, 2008 8:37 AM
> >> To: Rodrigo Dominguez
> >> Cc: 'Martin Guy'; gcc-help@gcc.gnu.org
> >> Subject: Re: GCC 3.3 binary for XScale
> >>
> >> Rodrigo Dominguez wrote:
> >>> Martin,
> >>>
> >>> This would install gcc on my host, not on my target.
> >> Not if you typed it on your target.
> > 
> > There's no 'yum' command in Embedded Linux.
> > 
> >>> My host is a machine running Fedora Core 8. My target is an 
> >> embedded board
> >>> with an XScale/ARM processor running Embedded Linux 2.6.
> >> Why didn't you say so?  I thought you were running Fedora on your
> >> target.
> >>
> >>> I am looking for the gcc 3.3 binaries that can run on my target.
> >> Where did you get Embedded Linux 2.6 for your target from?
> > 
> > I am using DULG ELDK which comes with gcc 4.0.
> > Why? Why does it matter?
> 
> Is the problem that you don't have gcc 3.3 on your target, or 
> that you don't
> have *any* gcc on your target?  This really important.  According to
> http://www.denx.de/wiki/view/DULG/ELDKPackages#Section_3.8.2. 
> there is a gcc package
> for the target.

As I mentioned on my first post, "It is important for me that the version is
3.3". I am currently running an application on the target that does binary
manipulation at run-time (sort of like JIT compilation). This application
allows me to write instrumentation code. However, the instrumentation code
and the application must be compiled using the same compiler version. This
is why I need gcc 3.3.

> 
> There are two ways to get gcc running on your target.  The easy way is
> to get a binary from whoever supplied your target OS.  If 
> they don't have
> one, you're going to have to build it.  If you have gcc 4.0 
> on your target,
> just use that to build gcc 3.3.

I think I will have to download gcc's source code and build it. I was trying
to avoid this since building gcc 3.3 takes time and I thought some one could
have done this already.

Thanks for your help :)

Rodrigo
 
> 
> I don't know what the real problem is, because you haven't told us.
> 
> Andrew.
> 

  reply	other threads:[~2008-02-29 16:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27 23:39 Rodrigo Dominguez
2008-02-28 11:06 ` Andrew Haley
2008-02-28 15:56   ` Rodrigo Dominguez
2008-02-28 12:27 ` Martin Guy
2008-02-28 16:17   ` Rodrigo Dominguez
2008-02-28 17:02     ` Andrew Haley
2008-02-29 13:34       ` Rodrigo Dominguez
2008-02-29 14:32         ` Andrew Haley
2008-02-29 15:49           ` Rodrigo Dominguez
2008-02-29 16:06             ` Andrew Haley
2008-02-29 16:15               ` Rodrigo Dominguez [this message]
2008-02-29 13:15     ` Martin Guy

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=BAY129-DAV179A22EF0CFF98E52F8C44B9140@phx.gbl \
    --to=roddomi@hotmail.com \
    --cc=aph@redhat.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=martinwguy@yahoo.it \
    /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).