public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Cyril Fischer <fischerc@itam.cas.cz>
To: egcs@egcs.cygnus.com
Subject: mips-sgi-irix6.5 installation
Date: Mon, 29 Mar 1999 07:47:00 -0000	[thread overview]
Message-ID: <36FF67D8.7ED63C35@itam.cas.cz> (raw)

Hi, I am not able to successfully compile egcs-1.1.2 on sgi indy (R4000
cpu).  The compilation stops when assembling the libstdc++.so for
-mabi=64. (due to the non-existent  64 bit library libm.so) As we have
32-bit cpu, we do not use 64 bit mode. How can I prevent the -mabi=64
step of the build procedure? I would like to avoid the manual editing of
makefiles.

Thanks,
Cyril

WARNING: multiple messages have this Message-ID

From: Cyril Fischer <fischerc@itam.cas.cz>
To: egcs@egcs.cygnus.com
Subject: mips-sgi-irix6.5 installation
Date: Wed, 31 Mar 1999 23:46:00 -0000	[thread overview]
Message-ID: <36FF67D8.7ED63C35@itam.cas.cz> (raw)
Message-ID: <19990331234600.SxH4OI9EOFnYZc0lcklZU4YvRf7PunEJzz1aXnJq1gg@z> (raw)

Hi, I am not able to successfully compile egcs-1.1.2 on sgi indy (R4000
cpu).  The compilation stops when assembling the libstdc++.so for
-mabi=64. (due to the non-existent  64 bit library libm.so) As we have
32-bit cpu, we do not use 64 bit mode. How can I prevent the -mabi=64
step of the build procedure? I would like to avoid the manual editing of
makefiles.

Thanks,
Cyril


             reply	other threads:[~1999-03-29  7:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-29  7:47 Cyril Fischer [this message]
1999-03-29 10:15 ` Lee Iverson
1999-03-31 23:46   ` Lee Iverson
1999-03-31 23:46 ` Cyril Fischer
1999-04-09  0:54 ` Jeffrey A Law
1999-04-09 12:58   ` Alexandre Oliva
1999-04-09 20:31     ` Jeffrey A Law
1999-04-10  6:38       ` [conditional multilib patch] " Alexandre Oliva
1999-04-11 23:01         ` Jeffrey A Law
1999-04-30 23:15           ` Jeffrey A Law
1999-04-30 23:15         ` Alexandre Oliva
1999-04-30 23:15       ` Jeffrey A Law
1999-04-30 23:15     ` Alexandre Oliva
1999-04-30 23:15   ` Jeffrey A Law

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=36FF67D8.7ED63C35@itam.cas.cz \
    --to=fischerc@itam.cas.cz \
    --cc=egcs@egcs.cygnus.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).