all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 57436@debbugs.gnu.org
Subject: bug#57436: Running ./configure from `guix shell -D guix --pure` errors
Date: Fri, 26 Aug 2022 13:34:42 -0600	[thread overview]
Message-ID: <CA+TvSRjULxJsEjPoVw8XrYi59QpgJZBmN7xmmCYpGsQJ1apcXA@mail.gmail.com> (raw)
In-Reply-To: <68cfad1e-5190-00b5-b0b3-de6b613129a5@telenet.be>

Thanks, Maxime!

Does the location of the `--pure` flag matter? I.e. I was running

`guix shell -D guix --pure` (suggested by the manual)

and you're suggesting

`guix shell --pure -D guix'

On Fri, Aug 26, 2022 at 1:02 PM Maxime Devos <maximedevos@telenet.be> wrote:
>
> On 26-08-2022 19:32, Katherine Cox-Buday wrote:
>
> > It gives me this error: configure: error: C++ compiler 'g++' does not
> > support the C++11 standard
> >
> > I have to run `guix shell -D guixgcc-toolchain@12.1.0  --pure` to get
> > ./configure to work.
> >
> > Since `guix shell -D` includes the development packages for Guix,
> > maybe the package needs updating?
>
> Maybe ./configure somehow picks up an old g++ from outside the "guix
> shell" environment.
>
> To avoid this, you can do `guix shell --pure -D guix'.
>
> Don't forget to add --localstatedir=/var to ./configure, especially if
> you hack on the daemon -- otherwise if you start the modified daemon
> from your git checkout, the state will go out of sync.
>
> Greetings,
> Maxime
>




  reply	other threads:[~2022-08-26 19:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26 17:32 bug#57436: Running ./configure from `guix shell -D guix --pure` errors Katherine Cox-Buday
2022-08-26 18:25 ` Liliana Marie Prikler
2022-08-26 19:02 ` Maxime Devos
2022-08-26 19:34   ` Katherine Cox-Buday [this message]
2022-08-26 20:27     ` Maxime Devos
2022-08-27 15:56   ` Katherine Cox-Buday
2022-08-29 14:01     ` zimoun
2022-09-07 18:26       ` Katherine Cox-Buday

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=CA+TvSRjULxJsEjPoVw8XrYi59QpgJZBmN7xmmCYpGsQJ1apcXA@mail.gmail.com \
    --to=cox.katherine.e@gmail.com \
    --cc=57436@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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.