From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brett Gilio Subject: Re: Updating mono. Adding MSBuild. Date: Mon, 01 Apr 2019 14:19:23 -0500 Message-ID: <87o95ppm84.fsf@posteo.net> References: <875zs5c72r.fsf@posteo.net> <874l7o4y1p.fsf@elephly.net> <20190327122310.4c8155eb@scratchpost.org> <877echijcb.fsf@posteo.net> <87va01zdy4.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:50288) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hB2Sx-0005VV-FD for guix-devel@gnu.org; Mon, 01 Apr 2019 15:19:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hB2Sw-0007Vo-G9 for guix-devel@gnu.org; Mon, 01 Apr 2019 15:19:31 -0400 Received: from mout01.posteo.de ([185.67.36.65]:50518) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hB2Sv-0007U0-Ln for guix-devel@gnu.org; Mon, 01 Apr 2019 15:19:30 -0400 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id 33F4A160061 for ; Mon, 1 Apr 2019 21:19:27 +0200 (CEST) In-reply-to: <87va01zdy4.fsf@elephly.net> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ricardo Wurmus Cc: Guix-devel Ricardo Wurmus writes: > Brett Gilio writes: > >> Although, there is a possible issue here that needs to be >> addressed. Both Mono and Chicken produce a binary called `csi`. This is >> a naming conflict, and I do not know the Guix-way for resolving naming >> conflicts. > > This is not a problem as during the build you probably won=E2=80=99t use = Chicken > together with Mono. > >> Most distributions renamed the Chicken csi to `chicken-csi` >> and left mono to `csi`. Does Guix have namespaces for binaries we >> produce? How should I proceed here? > > The Guix way is to install these things into separate profiles. Hi all. First, thank you ricardo for your response. I have a few things that seem to be important to note. On the plus side, I got Mono-5.0 to build successfully. But, during this process of building mono-5.0 I discovered that the mono documentation is either incorrect or misleading. Their documentation states that you need to have a mono-lite binary seed or a previous version of mono to compile newer versions. This doesn't seem to be true. Regardless of whether I pass our older version of mono to build mono-5.0, it compiles a csc (C# compiler) from its own source tree that it uses to build the full mono stack. So, I am inclined to think that bootstrapping mono from an earlier version isn't necessary since that csc compiler is C code. 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 "Uni= x 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/C= MakeFiles/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? Thanks, Brett Gilio