From: Dennis Grevenstein <dennis.grevenstein@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: building gcc 3.0.4 on mips-dec-osf1: where are CPP definitions set?
Date: Wed, 22 Mar 2023 20:19:37 +0100 [thread overview]
Message-ID: <F9AEBC48-DD67-43C7-B54E-90B523BC4675@gmail.com> (raw)
In-Reply-To: <CAH6eHdSWjyBLkrCYwTueqxi7DQJAoZhNdqr8tE63FwAwi24DmQ@mail.gmail.com>
Hi,
> Am 21.03.2023 um 01:04 schrieb Jonathan Wakely <jwakely.gcc@gmail.com>:
>
>> I’ve got an unusual problem. I have on old DECstation (MIPS R3000
>> based) running the infamous OSF/1. I got gcc-2.7.2.3 compiled and
>> working and I am now trying to upgrade to 3.0.4.
>> One problem I found is that gcc-3.0.4 no longer defines
>> #define __LANGUAGE_C__ 1
>> and a number of header files depend on it.
>> It still defines
>> #define __LANGUAGE_C 1
>> but of course that is not the same.
>> gcc-2.7.2.3 still defined it correctly. I assume that this is just an
>> error in some file, but I can’t find where these defines are set.
>
> I think it's a call to builtin_define in gcc/config/mips/mips.h
this is correct and I eventually got gcc-3.0.4 compiled.
However, the resulting gcc doesn’t fully work. It can go through
stage2 and it can build some apps like GNU sed, but will produce
binaries that fail with a Signal 11 with some other apps.
I think I would rather go back to gcc-2.7.2.3.
thank you anyway…
regards,
Dennis
next prev parent reply other threads:[~2023-03-22 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 23:46 Dennis Grevenstein
2023-03-21 0:04 ` Jonathan Wakely
2023-03-22 19:19 ` Dennis Grevenstein [this message]
2023-03-23 17:16 ` Dennis Grevenstein
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=F9AEBC48-DD67-43C7-B54E-90B523BC4675@gmail.com \
--to=dennis.grevenstein@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.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).