From: Ricardo Wurmus <rekado@elephly.net>
To: Brett Gilio <brettg@posteo.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Updating mono. Adding MSBuild.
Date: Tue, 02 Apr 2019 10:17:47 +0200 [thread overview]
Message-ID: <87lg0szuqc.fsf@elephly.net> (raw)
In-Reply-To: <87o95ppm84.fsf@posteo.net>
Brett Gilio <brettg@posteo.net> writes:
> Okay, great Mono-5.0 builds successfully. So with that knowledge, I
> tried to compile the latest Mono-5.18. However, shortly after the
> configuration step it throws
>
> CMake Error: CMake was unable to find a build program corresponding to "Unix Makefiles". CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build tool.
> CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
> CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
> -- Configuring incomplete, errors occurred!
> See also
> "/tmp/guix-build-mono-5.18.1.0.drv-0/mono-5.18.1.0/mono/btls/build-shared/CMakeFiles/CMakeOutput.log".
>
> The interesting thing is that it uses the gnu-build-system to build the
> csc compiler, and I had to pass cmake as a native-input or else the
> configuration step would fail. So, does anybody know how to deal with
> this cmake issue?
Do you get the errors when using the cmake-build-system? If you need to
prepare the build you can add custom build phases.
--
Ricardo
next prev parent reply other threads:[~2019-04-02 8:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 3:46 Updating mono. Adding MSBuild Brett Gilio
2019-03-27 6:43 ` Ricardo Wurmus
2019-03-27 11:23 ` Danny Milosavljevic
2019-03-29 19:14 ` Brett Gilio
2019-03-29 19:18 ` Ricardo Wurmus
2019-04-01 19:19 ` Brett Gilio
2019-04-02 8:17 ` Ricardo Wurmus [this message]
2020-01-26 15:58 ` Pierre Neidhardt
2020-02-20 10:06 ` Pierre Neidhardt
2020-02-20 16:49 ` Pierre Neidhardt
2019-03-27 11:37 ` Danny Milosavljevic
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=87lg0szuqc.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=brettg@posteo.net \
--cc=guix-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).