From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Felipe Moura Oliveira <moura.fmo@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Fail in build gcc 4.2 to use in x86_64-linux-gnu Ubuntu 5.4.0-6ubuntu1~16.04.12
Date: Wed, 19 Aug 2020 07:51:03 +0100 [thread overview]
Message-ID: <CAH6eHdS5KMibWNypOdno9H5xV7Acwvr2YrMpYL9ajiA=DhVbHQ@mail.gmail.com> (raw)
In-Reply-To: <CAFMGK3bhbmEnmuPy0ALyVaevN-H1w__yWMnk_Np+i1vz0ex8gw@mail.gmail.com>
On Wed, 19 Aug 2020 at 00:15, Felipe Moura Oliveira via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> Hi all.
>
> I need gcc 4.2 to compile old project.
> I tried to build gcc 4.2 in several ways and with several configurations
> and at the end I had the same error log.
> I'm stuck in it for about 3 days T_T.
> My process:
> 1 - cloned gcc repository and change to branch gcc-4.2.
> 2 - created dir in parallel with code.
> 3 - run *sudo ../gcc-4.2.0/configure --enable-languages=c,c++
> --disable-stage1-checking --disable-multilib --disable-werror
> --disable-bootstrap*
Why are you using sudo?
> 4 - I open Makefile and change :
>
> CC = gcc
> CXX = g++
>
> to
>
> CC = gcc -fgnu89-inline
> CXX = g++ -fgnu89-inline
>
> (https://unix.stackexchange.com/questions/219708/arch-compiling-toplev-o-fails-in-gcc-install)
>
> Because I had same behavior.
>
> 5 - sudo make -j1
Don't build as root! That's very silly.
>
> After 10 minutes my build crash with msg:
> ...
> ../../gcc-4.2.0/gcc/config/i386/i386.h:155: error: storage class
> specified for parameter ‘x86_partial_reg_dependency’
It looks to me like your sources are corrupt somehow. This line is not
a function parameter.
prev parent reply other threads:[~2020-08-19 6:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 23:11 Felipe Moura Oliveira
2020-08-19 6:51 ` Jonathan Wakely [this message]
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='CAH6eHdS5KMibWNypOdno9H5xV7Acwvr2YrMpYL9ajiA=DhVbHQ@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=moura.fmo@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).