unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: phodina <phodina@protonmail.com>, help-guix <help-guix@gnu.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>, "Marius Bakke" <marius@gnu.org>
Subject: Re: gcc-toolchain-4.8 build failure
Date: Fri, 06 Jan 2023 16:35:31 +0100	[thread overview]
Message-ID: <87k01zisl8.fsf@gmail.com> (raw)
In-Reply-To: <Yz5m_PfGs0wn8wTimN4swbA1U8RNGgi6f1Gu3n9tjWvIJrtz53uZDrvtgo3sPaBcYVoBf4ZCbvkHLhASNd7M9SKNc4q1Xvx46MJsQvY_m5E=@protonmail.com>

Hi Petr,

On Mon, 26 Dec 2022 at 09:07, phodina via <help-guix@gnu.org> wrote:

> So I grabbed the gcc-toolchain-4.8 and found out it's broken and
> doesn't build without errors. [1]

Note gcc-4.7 is also failing,

    http://ci.guix.gnu.org/build/98496/details

but gcc-4.9 builds fine,

    http://ci.guix.gnu.org/build/98527/details


Well, I guess gcc-toolchain@4.8 is built using gcc-toolchain@10 and
probably some incompatibilities.  Well, my attempt is failing…
similarly.

--8<---------------cut here---------------start------------->8---
$ guix build -e '(@@ (gnu packages gcc) gcc-4.8)'   \
       --with-c-toolchain=gcc-4.8=gcc-toolchain@4.9 \
       --no-grafts

[...]

cfns.gperf: At global scope:
cfns.gperf:101:1: error: ‘const char* libc_name_p(const char*, unsigned int)’ redeclared inline with ‘gnu_inline’ attribute
cfns.gperf:26:14: note: ‘const char* libc_name_p(const char*, unsigned int)’ previously declared here
--8<---------------cut here---------------end--------------->8---

Bah, I do not know. :-)


Cheers,
simon


      reply	other threads:[~2023-01-06 16:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26  9:07 gcc-toolchain-4.8 build failure phodina via
2023-01-06 15:35 ` Simon Tournier [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

  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=87k01zisl8.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=ludo@gnu.org \
    --cc=marius@gnu.org \
    --cc=phodina@protonmail.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).