public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: "Yuan, Sai (NSN - CN/Cheng Du)" <sai.yuan@nsn.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: How to install 32 bit gcc on 64 bit RHEL5.1
Date: Tue, 12 Aug 2008 12:01:00 -0000	[thread overview]
Message-ID: <48A159DA.6030400@redhat.com> (raw)
In-Reply-To: <174CED94DD8DC54AB888B56E103B11870ABDB2@CNBEEXC007.nsn-intra.net>

Please don't top-post.

Yuan, Sai (NSN - CN/Cheng Du) wrote:
> Oh! I didn't install a 32-bit cross assembler. Where can i get this stuff?

It's all part of GNU Binutils.

> I didn't use "-m32" because it also compile in Clearcase environment. It's not easy for me to add this flag.

You have got to be joking!  Are you telling me that Clearcase is so
unspeakably awful that you cannot control any compiler flags?

Are you telling me that you cannot use a shell script to exec gcc
with the -m32 flag?

Andrew.


> -----Original Message-----
> From: ext Andrew Haley [mailto:aph@redhat.com]
> Sent: Tue 8/12/2008 5:00 PM
> To: Yuan, Sai (NSN - CN/Cheng Du)
> Cc: gcc-help@gcc.gnu.org
> Subject: Re: How to install 32 bit gcc on 64 bit RHEL5.1
>  
> Yuan, Sai (NSN - CN/Cheng Du) wrote:
> 
>> It caused me to doubt whether it can install 32 bit gcc on 64 bit Linux. Btw, the version i want to install is 32bit gcc 4.1.2.
>> Could you please help me?
> 
> It's complaining that you haven't installed a 32-bit cross assembler.
> I guess that's right, is it?  You didn't build cross-binutils for i386?
> 
> Why are you doing such a strange thing?  gcc will already generate 32-bit
> code with "gcc -m32".
> 
> Andrew.
> 
> 

  reply	other threads:[~2008-08-12  9:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12  9:00 Yuan, Sai (NSN - CN/Cheng Du)
2008-08-12  9:07 ` Andrew Haley
2008-08-12  9:38   ` Yuan, Sai (NSN - CN/Cheng Du)
2008-08-12 12:01     ` Andrew Haley [this message]
2008-08-12 13:12       ` Vardhan, Sundara (GE Infra, Energy)

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=48A159DA.6030400@redhat.com \
    --to=aph@redhat.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=sai.yuan@nsn.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).