public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nils@shkoo.com
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/5450: __i386__ not defined on unixsware
Date: Tue, 22 Jan 2002 02:56:00 -0000	[thread overview]
Message-ID: <20020122105602.18339.qmail@sources.redhat.com> (raw)

The following reply was made to PR other/5450; it has been noted by GNATS.

From: nils@shkoo.com
To: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
        gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: other/5450: __i386__ not defined on unixsware
Date: Tue, 22 Jan 2002 03:51:20 -0700 (MST)

 yes,
 
 this fixes the problem.
 
 thanks,
 
 -nils
 
 On 22 Jan 2002 rodrigc@gcc.gnu.org wrote:
 
 > Synopsis: __i386__ not defined on unixsware
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: rodrigc
 > State-Changed-When: Mon Jan 21 23:13:18 2002
 > State-Changed-Why:
 >     Does the problem go away if you patch gcc/config/i386/sysv4.h
 >     with the following?  It is similar to the last line
 >     of sysv5.h.
 >     
 >     
 >     
 >     Index: sysv4.h
 >     ===================================================================
 >     RCS file: /cvs/gcc/gcc/gcc/config/i386/sysv4.h,v
 >     retrieving revision 1.11.4.2
 >     diff -u -r1.11.4.2 sysv4.h
 >     --- sysv4.h     2001/05/22 17:13:48     1.11.4.2
 >     +++ sysv4.h     2002/01/22 07:10:06
 >     @@ -212,3 +212,6 @@
 >                "addl\t$_GLOBAL_OFFSET_TABLE_+[.-.LPR%=],%0"
 >       \
 >                : "=d"(BASE))
 >      #endif
 >     +
 >     +#undef CPP_SPEC
 >     +#define CPP_SPEC "%(cpp_cpu)"
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5450
 > 
 


             reply	other threads:[~2002-01-22 10:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-22  2:56 nils [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-22 15:04 rodrigc
2002-01-21 23:13 rodrigc
2002-01-21 22:06 nils

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=20020122105602.18339.qmail@sources.redhat.com \
    --to=nils@shkoo.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).