From: Chris Marusich <cmmarusich@gmail.com>
To: 46253-close@debbugs.gnu.org
Cc: "Léo Le Bouter" <lle-bout@zaclys.net>
Subject: bug#46253: powerpc64le: gcc-final: "configure: error: cannot compute sizeof (long long)"
Date: Thu, 04 Feb 2021 00:26:50 -0800 [thread overview]
Message-ID: <87sg6cme5x.fsf@gmail.com> (raw)
In-Reply-To: <871rdyon1v.fsf@gmail.com> (Chris Marusich's message of "Tue, 02 Feb 2021 01:07:24 -0800")
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
Hi,
This is fixed in the following commit:
https://git.savannah.gnu.org/cgit/guix.git/commit/?h=wip-ppc64le&id=ffcc950261c829e76f2faf6c8ea03d3fc56a20e1
The problem was in the config.log, but I didn't see it at first:
"powerpc64le-guix-linux-gnu-ld: cannot find -lstdc++"
Léo mentioned that it was probably a linking problem, and when I checked
his commits in his own Git repository, I found this, which solved the
problem:
https://gitlab.com/lle-bout/guix/-/commit/070e06e8be6090a7682288c24b5686f1b578c001
However, that commit would have changed the way we link gcc-final with
libstdc++ on all architectures. I have made a similar change that
accomplishes the same thing, but only for powerpc64le-linux (or other
Guix system types beginning with "powerpc64"). On existing Guix system
types, we will continue to link the same as before.
Using commit ffcc950261c829e76f2faf6c8ea03d3fc56a20e1, I was successful
in building gcc-final. I'm closing this bug report.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2021-02-04 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 9:07 bug#46253: powerpc64le: gcc-final: "configure: error: cannot compute sizeof (long long)" Chris Marusich
2021-02-04 8:26 ` Chris Marusich [this message]
2021-02-07 0:53 ` Chris Marusich
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sg6cme5x.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=46253-close@debbugs.gnu.org \
--cc=lle-bout@zaclys.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).