From: Marius Bakke <mbakke@fastmail.com>
To: Josh Marshall <joshua.r.marshall.1991@gmail.com>, help-guix@gnu.org
Subject: Re: Fwd: Packaging a cmake C++ header only library requiring C++17
Date: Fri, 29 Nov 2019 15:58:00 +0100 [thread overview]
Message-ID: <87v9r2vifb.fsf@devup.no> (raw)
In-Reply-To: <CAFkJGRdMtH6SXEEGO9=p+=4s-ydQ+mnhLxOLFZ_jMug9VOPSyw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
Hi Josh,
Josh Marshall <joshua.r.marshall.1991@gmail.com> writes:
> Hello,
>
> nckd and I have gone back and forth over a few days in IRC trying to
> help me out here. I am trying to package magic-enum (
> https://github.com/Neargye/magic_enum ) which is a C++ header only
> library requiring at least C++ 17, and uses the cmake build system.
> The problem which we can't figure out is why the compiler being used
> is the default for `gcc` at 7.4 while there is explicit use and
> dependency on `gcc` 9.2 via `gcc-9`. We're stumped.
>
> Attached are the latest package definitions, build log, and cli
> invocation and output.
If you change 'inputs' to 'native-inputs', then CMake will pick up the
correct GCC, and you can remove the (arguments ...) block.
(you probably wanted -std=gnu++17 instead of -std=gnu17 too, but no need
when using GCC 9)
Pro tip: use 'guix build -f magic-enum.scm' to get the build output
right in your terminal. :-)
HTH,
Marius
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-11-29 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFkJGRfDz7iwLtVZxDoPOLgYOsPEUvpT+qarGpLTv-scJV30nw@mail.gmail.com>
2019-11-28 18:11 ` Fwd: Packaging a cmake C++ header only library requiring C++17 Josh Marshall
2019-11-29 14:58 ` Marius Bakke [this message]
2019-11-29 13:22 ` Josh Marshall
2019-11-29 14:16 ` sirgazil
2019-11-29 14:16 ` Tobias Geerinckx-Rice
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=87v9r2vifb.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=help-guix@gnu.org \
--cc=joshua.r.marshall.1991@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.