From: Ian Lance Taylor <iant@golang.org>
To: anand akhare <anandstraight@outlook.com>
Cc: "gcc-help@gnu.org" <gcc-help@gnu.org>
Subject: Re: go support in gcc fails to compile while building gcc from source
Date: Mon, 17 Apr 2023 13:31:47 -0700 [thread overview]
Message-ID: <CAKOQZ8yZ_BxWYo7f-+0kNB7-O9DAHvWKSk9brQz26=9Df-g1Ag@mail.gmail.com> (raw)
In-Reply-To: <PSAPR03MB5702B6F874B3B806DFC8B962BE9C9@PSAPR03MB5702.apcprd03.prod.outlook.com>
On Mon, Apr 17, 2023 at 9:08 AM anand akhare via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> I am compiling gcc 10.4.0 and it works well for c and c++. To get go support, configure was given enable-langugages=c,c++,go and later make -j8 and build fails with below error
>
> ake[3]: Entering directory '/home/<username>/srcs/gcc-10.4.0/x86_64-pc-linux-gnu/libgo'
> /bin/bash: line 1: /home/<username>/srcs/gcc-10.4.0/host-x86_64-pc-linux-gnu/gcc/gccgo: No such file or directory
>
> I have masked username in log to hide it. Log still holds same as for compile. I did not investigate much on makefile though setup is quite simple. I am using ubuntu linux 22.0.4 and compiling gcc 10.4.0 source tarball taken from ftp of gcc.gnu.org and using binary installed gcc 10.4.0. Below is configure command before make :
>
> ./configure --prefix=/home/<username>/srcs/gcc-10.4.0/install --with-mpc=/home/<username>/srcs/libs/install --with-mpfr=/home/<username>/srcs/libs/install --with-gmp=/home/<username>/srcs/libs/install --enable-languages=c,c++,go
>
> There is not much issue with most things appear due to first compile without go that c and c++ worked.
>
> Pls give inputs if anything missing that compile is failing for go. Do we need go installed before building go from source?
Don't use "./configure". Run configure in a different, empty,
directory. See https://gcc.gnu.org/install/configure.html .
Ian
next prev parent reply other threads:[~2023-04-17 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 16:02 anand akhare
2023-04-17 20:31 ` Ian Lance Taylor [this message]
2023-04-18 7:52 ` anand akhare
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='CAKOQZ8yZ_BxWYo7f-+0kNB7-O9DAHvWKSk9brQz26=9Df-g1Ag@mail.gmail.com' \
--to=iant@golang.org \
--cc=anandstraight@outlook.com \
--cc=gcc-help@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).