public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "yilu@bupt.edu.cn" <yilu@bupt.edu.cn>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Re: Install gcc
Date: Fri, 06 Mar 2020 12:56:00 -0000	[thread overview]
Message-ID: <CAH6eHdRaoN_sppSAjSwe+aSVjybSLgBtG9E3nSyuWUYDG=c1AA@mail.gmail.com> (raw)
In-Reply-To: <5e624788.1c69fb81.a0d08.4515SMTPIN_ADDED_BROKEN@mx.google.com>

On Fri, 6 Mar 2020 at 12:52, yilu@bupt.edu.cn wrote:
>
> Oh...I'm so sorry. I've read these guides but I miss that I should go into the objdir to configure. Thanks!
> This time I got into the objdir and use:
> `./../gcc/configure --prefix=/usr/local/gcc --enable-languages=all --disable-multilib --disable-bootstrap`
> and I found the Makefile in my objdir directory. I try `make -j4` and found
> g++: error: gengtype-lex.c: No such file or directory
> g++: fatal error: no input files
> Could you help me with this?

See https://gcc.gnu.org/install/prerequisites.html

Flex version 2.5.4 (or later)
Necessary when modifying *.l files.
Necessary to build GCC during development because the generated output
files are not included in the version-controlled source repository.
They are included in releases.

  parent reply	other threads:[~2020-03-06 12:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5e6238c2.1c69fb81.e2203.5452SMTPIN_ADDED_BROKEN@mx.google.com>
2020-03-06 12:08 ` Jonathan Wakely
2020-03-06 12:52   ` yilu
2020-03-06 13:03     ` Henri Cloetens
     [not found]   ` <5e624788.1c69fb81.a0d08.4515SMTPIN_ADDED_BROKEN@mx.google.com>
2020-03-06 12:56     ` Jonathan Wakely [this message]
2020-03-06 13:52       ` yilu

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='CAH6eHdRaoN_sppSAjSwe+aSVjybSLgBtG9E3nSyuWUYDG=c1AA@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=yilu@bupt.edu.cn \
    /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).