From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: [PATCH] gnu: cross-gcc-arguments: Disable libitm, libvtv and, libsanitizer. Date: Tue, 23 Feb 2016 14:14:03 +0100 Message-ID: References: <56C322C4.3040706@gmail.com> <56CC4E79.7030706@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41661) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYCnC-0002j9-W1 for guix-devel@gnu.org; Tue, 23 Feb 2016 08:14:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aYCn9-0008Dt-Po for guix-devel@gnu.org; Tue, 23 Feb 2016 08:14:18 -0500 In-Reply-To: <56CC4E79.7030706@gmail.com> 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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Manolis Ragkousis Cc: guix-devel@gnu.org Manolis Ragkousis writes: > This is a follow up to better explain what the problem is with the > sans-libc cross gcc in the (gnu packages cross-base) module. > > In the latest master if you try to build gcc-cross-sans-libc with: > > ./pre-inst-env guix build -e '((@@(gnu packages cross-base) cross-gcc) > "i686-linux-gnu")' -c8 > > gcc modules libitm, libvtv and libsanitizer fail to build with > "configure: error: C compiler cannot create executables". > > This happens because there is no libc present at that point and the > problem was introduced with commit ca7ef4d41854218c which enabled c++. I find this very odd. I=E2=80=99m the author of that commit and I did th= is to be able to build a C and C++ cross compiler for arm-none-eabi (which I still haven=E2=80=99t submitted to the ML). At no point did I see any er= rors about libitm, libvtv, or libsanitizer. My cross-compiler is made with little more than =E2=80=9C(cross-gcc "arm-none-eabi")=E2=80=9D, so I wonder why you=E2=80=99d have problems wi= th building a cross-compiler for =E2=80=9Ci686-linux-gnu=E2=80=9D. > At that stage no linking can happen so the best solution is to just > disable the modules. It does not affect anything after that. I cannot verify this as I=E2=80=99m not familiar with all this (and I can= not rebuild my cross-compiler at this point). This doesn=E2=80=99t mean I ob= ject to this change, I just don=E2=80=99t understand why we see it with =E2=80=9C= i686-linux-gnu=E2=80=9D but not with my =E2=80=9Carm-none-eabi=E2=80=9D build :-/ Could you please also add some comment above the new flags to concisely say why they are needed? That=E2=80=99s just to prevent people like me f= rom removing the flags in the future because =E2=80=9Cthey don=E2=80=99t seem= to do anything=E2=80=9D :) Thanks! ~~ Ricardo