all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Reza Housseini <reza.housseini@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: gcc-4.7 and gcc-4.8 compilation failure in x64
Date: Tue, 29 Mar 2022 18:39:33 +0000	[thread overview]
Message-ID: <E-ATnd5PbHZc85PAiG8gwlrTmgA7Pw8I_if6-8HrmlqK42ioIrCDFpEJpe9oJaOkvjZsJ75Bw5h7iTMJwGOe1KoiNLn-6uoSSiAZ9Juu0UE=@elenq.tech> (raw)
In-Reply-To: <a7f33d9f-fab9-1e43-1c2a-b0e78c6fd492@gmail.com>


> Hi Ekaitz
>
> Not that I am in any position to answer the question, but could you
>
> share a little bit more context?
>
> Did the error occur when you were compiling gcc-4.7 or do programs
>
> compiled with this compiler have this issue?
>
> What path led you to gcc-4.7? Can you share your compilation settings? etc..
>
> Kind regards,
>
> Reza



The failure appears on the compilation on the gcc-4.7 and gcc-4.8 packages.

If you make a `manifest.scm` that looks like this:

(use-modules (gnu packages gcc))
(packages->manifest (list gcc-4.7))

And you try to compile that using `guix build -m manifest.scm` the compilation fails. The same happens when choosing 4.8.

I'm on x64.

Hope that clarifies a little bit.



  reply	other threads:[~2022-03-29 18:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 14:15 bug#54626: gcc-4.7 and gcc-4.8 compilation failure in x64 Ekaitz Zarraga
2022-03-29 17:53 ` Reza Housseini
2022-03-29 18:39   ` Ekaitz Zarraga [this message]
2022-03-29 19:01     ` Ekaitz Zarraga
2022-03-30 19:27       ` Reza Housseini
2022-03-30 19:32         ` Ekaitz Zarraga
2022-03-30 19:40           ` Reza Housseini
2022-03-30 19:43             ` Ekaitz Zarraga
2022-04-01  8:43       ` Ludovic Courtès
2022-03-31 19:17 ` bug#54626: " Ekaitz Zarraga

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='E-ATnd5PbHZc85PAiG8gwlrTmgA7Pw8I_if6-8HrmlqK42ioIrCDFpEJpe9oJaOkvjZsJ75Bw5h7iTMJwGOe1KoiNLn-6uoSSiAZ9Juu0UE=@elenq.tech' \
    --to=ekaitz@elenq.tech \
    --cc=guix-devel@gnu.org \
    --cc=reza.housseini@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.