public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jlarmour@redhat.com
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/3992: Build failures for all non-native mips targets
Date: Fri, 10 Aug 2001 22:16:00 -0000	[thread overview]
Message-ID: <20010811050739.19080.qmail@sourceware.cygnus.com> (raw)

>Number:         3992
>Category:       libstdc++
>Synopsis:       Build failures for all non-native mips targets
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Aug 10 22:16:04 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Jonathan Larmour
>Release:        gcc-3_0-branch
>Organization:
>Environment:
linux host, mips-tx39-elf target, for example.
All non-SGI MIPS targets would be affected.
>Description:
Building libstdc++-v3 for a non-SGI MIPS target such as
mips-tx39-elf results in a build failure such as:

/home/jlarmour/sourceware/gcc/build/mipstx39-elf/mips-tx39-elf/libstdc++-v3/include/mips-tx39-elf/bits/atomicity.h:33:21: sgidefs.h: No such file or directory

This is because config/cpu/mips/bits/atomicity.h includes
<sgidefs.h> unconditionally. This file AFAIK only exists
on SGI systems. Not on newlib targets, nor probably 
Linux/MIPS. 
>How-To-Repeat:
configure --target mips-tx39-elf
make
>Fix:

Probably the easiest fix is simply to reflect the current
reality:

Index: configure.target
===================================================================
RCS file: /cvs/gcc/gcc/libstdc++-v3/configure.target,v
retrieving revision 1.14.2.7
diff -u -5 -p -r1.14.2.7 configure.target
--- configure.target	2001/07/26 05:01:52	1.14.2.7
+++ configure.target	2001/08/11 04:03:05
@@ -37,11 +37,11 @@ case "${target_cpu}" in
     cpu_include_dir="config/cpu/i386"
     ;;
   i486 | i586 | i686 | i786)
     cpu_include_dir="config/cpu/i486"
     ;;
-  mips*)
+  mips*-*-irix*)
     cpu_include_dir="config/cpu/mips"
     ;;
   powerpc | rs6000)
     cpu_include_dir="config/cpu/powerpc"
     ;;


So the generic case will pick up the rest.

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-08-10 22:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-10 22:16 jlarmour [this message]
2001-08-24 17:26 bkoz
2002-02-24  7:45 rodrigc

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=20010811050739.19080.qmail@sourceware.cygnus.com \
    --to=jlarmour@redhat.com \
    --cc=gcc-gnats@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).