all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Laurent Gatto <laurent.gatto@gmail.com>, 74455@debbugs.gnu.org
Subject: bug#74455: gcc-toolchain and gfortran-toolchain conflict
Date: Mon, 06 Jan 2025 20:11:08 +0100	[thread overview]
Message-ID: <871pxfycz7.fsf@gmail.com> (raw)
In-Reply-To: <CA+uNOzhaZbkznRn581=t7JCW1JYoiXftri1RkyybpR=-5u5OYQ@mail.gmail.com>

Hi,

On Thu, 21 Nov 2024 at 08:57, Laurent Gatto <laurent.gatto@gmail.com> wrote:

> But fails I add gfortran-toolchain *after* gcc-toolchain

That’s because both are “more or less” some GCC toolchain and provides
similar subset of files.  Here, the version of the both default
toolchains does not match (14 vs 11).  Since the profile is built using
the command line order, then depending on which one comes first, you
have one version or the other for some of these files.

And as you can see, the compiler is g++ version 14 but using files from
version 11…

--8<---------------cut here---------------start------------->8---
$ readlink -f /gnu/store/hhzpa2yx8cz92cgm7xjpd2pp6pk74g96-profile/include/c++/type_traits
/gnu/store/piai5ba5fx901hr7pwnz2b9vysrrjmlh-gfortran-11.4.0/include/c++/type_traits
--8<---------------cut here---------------end--------------->8---

…and bang!

If both are at 11, then it works as expected:

--8<---------------cut here---------------start------------->8---
$ cat main.cpp 
#include <iostream>

int main(void) {
    std::cout << __cplusplus;

    return 0;
}

$ guix time-machine -q --commit=1e6d1c3 \
       -- shell gcc-toolchain@11 gfortran-toolchain \
       -- g++ --version
g++ (GCC) 11.4.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ guix time-machine -q --commit=1e6d1c3 \
       -- shell gcc-toolchain@11 gfortran-toolchain \
       -- g++ main.cpp && ./a.out
201703
--8<---------------cut here---------------end--------------->8---


Well, the naive question: Does it make sense to have in the same profile
some C/C++ GCC toolchain at one version and some Fortran GCC toolchain
at another version?

Depending on the answer, I guess the fix is not the same. :-)

Cheers,
simon




  reply	other threads:[~2025-01-06 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21  7:57 bug#74455: gcc-toolchain and gfortran-toolchain conflict Laurent Gatto
2025-01-06 19:11 ` Simon Tournier [this message]
2025-01-07  9:22   ` Laurent Gatto

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=871pxfycz7.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=74455@debbugs.gnu.org \
    --cc=laurent.gatto@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.