------=_Part_36001_915501862.1549794526114-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Subject: Re: collect2: fatal error: cannot find 'ld' Date: Sun, 10 Feb 2019 11:45:03 +0100 (CET) Message-ID: References: <> <87wom9kp1q.fsf@elephly.net> <<87wom9kp1q.fsf@elephly.net>> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_36180_551712987.1549795503501" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:51103) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gsmbi-0007z8-T1 for help-guix@gnu.org; Sun, 10 Feb 2019 05:45:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gsmbh-0006K0-UR for help-guix@gnu.org; Sun, 10 Feb 2019 05:45:06 -0500 Received: from w1.tutanota.de ([81.3.6.162]:60554) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gsmbh-0006He-7c for help-guix@gnu.org; Sun, 10 Feb 2019 05:45:05 -0500 In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Znavko Cc: Help Guix ------=_Part_36180_551712987.1549795503501 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Sorry. The file extension was the solution: $ mv c c.c $ gcc c.c $ ./a.out 4096 Feb 10, 2019, 10:28 AM by znavko@tutanota.com: > Installation of gcc-toolchain did not help. > > $ guix package -I |grep gcc > gcc-toolchain=C2=A0=C2=A0=C2=A0 8.2.0=C2=A0=C2=A0=C2=A0 out=C2=A0=C2=A0= =C2=A0 /gnu/store/xwk99qi92pm3zqd95mvjx4mkdmg8plpk-gcc-toolchain-8.2.0 > > $ gcc c > c: file not recognized: file format not recognized > collect2: error: ld returned 1 exit status > > $ cat c > #include > #include > > int main(void) > { > =C2=A0=C2=A0=C2=A0 struct stat stats; > > =C2=A0=C2=A0=C2=A0 if (!stat("/", &stats)) > =C2=A0=C2=A0=C2=A0 { > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 printf("%u\n", stats.st_blksiz= e); > =C2=A0=C2=A0=C2=A0 } > } > > > > Feb 9, 2019, 2:35 PM by > rekado@elephly.net >= : > >> >> znavko@tutanota.com >> writes: >> >>> Hi! I compile this >>> https://stackoverflow.com/questions/6161823/dd-h= ow-to-calculate-optimal-blocksize >>> <>>> https://stackoverflow.c= om/questions/6161823/dd-how-to-calculate-optimal-blocksize >>> > >>> >>> and get this: >>> >>> $ gcc c.c >>> collect2: fatal error: cannot find 'ld' >>> compilation terminated. >>> >>> $ whereis ld >>> ld: >>> >>> $ gcc --version >>> gcc (GCC) 8.2.0 >>> >>> How to solve this? >>> >> >> I=E2=80=99m assuming that you installed the =E2=80=9Cgcc=E2=80=9D packag= e. Don=E2=80=99t do that. >> Install =E2=80=9Cgcc-toolchain=E2=80=9D instead. >> >> guix package -r gcc -i gcc-toolchain >> >> --=20 >> Ricardo >> > > ------=_Part_36180_551712987.1549795503501 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Sorry. The file extension was the s= olution:

$ mv c c.c

$ gcc c.c

$ ./a.out
4096

Fe= b 10, 2019, 10:28 AM by znavko@tutanota.com:

Installation o= f gcc-toolchain did not help.

$ guix package -I |gr= ep gcc
gcc-toolchain =    8.2.0    out    /gnu/store/xwk99= qi92pm3zqd95mvjx4mkdmg8plpk-gcc-toolchain-8.2.0

$ g= cc c
c: file not recognize= d: file format not recognized
collect2: error: ld returned 1 exit status

$ ca= t c
#include <sys/stat.= h>
#include <stdio.h= >

int main(void)
{
= ;   struct stat stats;

   = if (!stat("/", &stats))
    {
&n= bsp;       printf("%u\n", stats.st_blksize);<= br>
    }
}

Feb 9, 2019, 2:35 PM by rekado@= elephly.net:

znavko@tutanota.com writes:
Hi! I compile this https://stackov= erflow.com/questions/6161823/dd-how-to-calculate-optimal-blocksize <= https://st= ackoverflow.com/questions/6161823/dd-how-to-calculate-optimal-blocksize= >

and get thi= s:

$ gcc c.c
=
collect2: fatal error: cannot find 'ld'
=
compilation terminated.
$ whereis ld
ld:

$ gcc --version
gcc (GCC) 8.2.0
How to solve this?

I=E2=80=99m assuming that you i= nstalled the =E2=80=9Cgcc=E2=80=9D package. Don=E2=80=99t do that.
Install =E2=80=9Cgcc-toolchain=E2=80=9D instead.
<= /div>

guix package -r gcc = -i gcc-toolchain

--
Ricardo

------=_Part_36180_551712987.1549795503501-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: zimoun Subject: Re: collect2: fatal error: cannot find 'ld' Date: Mon, 11 Feb 2019 12:40:19 +0100 Message-ID: References: <87wom9kp1q.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]:33089) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gt9wx-0003ig-Bi for help-guix@gnu.org; Mon, 11 Feb 2019 06:40:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gt9wv-0001LE-ES for help-guix@gnu.org; Mon, 11 Feb 2019 06:40:35 -0500 Received: from mail-qt1-x830.google.com ([2607:f8b0:4864:20::830]:46999) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gt9wv-0001JC-8x for help-guix@gnu.org; Mon, 11 Feb 2019 06:40:33 -0500 Received: by mail-qt1-x830.google.com with SMTP id y20so11627422qtm.13 for ; Mon, 11 Feb 2019 03:40:31 -0800 (PST) In-Reply-To: <87wom9kp1q.fsf@elephly.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ricardo Wurmus Cc: Help Guix Hi Ricardo, On Sat, 9 Feb 2019 at 16:21, Ricardo Wurmus wrote: > > I=E2=80=99m assuming that you installed the =E2=80=9Cgcc=E2=80=9D package= . Don=E2=80=99t do that. > Install =E2=80=9Cgcc-toolchain=E2=80=9D instead. Is it because of the comment in the definition of `make-gcc-toolchain'? ;; The main raison d'=C3=AAtre of this "meta-package" is (1) to conveniently ;; install everything that we need, and (2) to make sure ld-wrapper comes ;; before Binutils' ld in the user's profile. Even if the section of Manual provides useful information, the (2) point clearly explains why "what you really want is the `gcc-toolchain' package." :-) All the best, simon From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: collect2: fatal error: cannot find 'ld' Date: Mon, 11 Feb 2019 13:01:38 +0100 Message-ID: <87r2celejh.fsf@elephly.net> References: <87wom9kp1q.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]:37376) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gtAHq-0000Mr-3C for help-guix@gnu.org; Mon, 11 Feb 2019 07:02:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gtAHp-0003Dm-5t for help-guix@gnu.org; Mon, 11 Feb 2019 07:02:09 -0500 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21137) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gtAHl-0003A5-6C for help-guix@gnu.org; Mon, 11 Feb 2019 07:02:07 -0500 In-reply-to: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: zimoun Cc: Help Guix zimoun writes: > Hi Ricardo, > > On Sat, 9 Feb 2019 at 16:21, Ricardo Wurmus wrote: >> >> I=E2=80=99m assuming that you installed the =E2=80=9Cgcc=E2=80=9D packag= e. Don=E2=80=99t do that. >> Install =E2=80=9Cgcc-toolchain=E2=80=9D instead. > > Is it because of the comment in the definition of `make-gcc-toolchain'? > > ;; The main raison d'=C3=AAtre of this "meta-package" is (1) to > conveniently > ;; install everything that we need, and (2) to make sure ld-wrapper comes > ;; before Binutils' ld in the user's profile. > > Even if the section of Manual provides useful information, the (2) > point clearly explains why "what you really want is the > `gcc-toolchain' package." :-) Yes, this is the reason. I still think that we should hide the plain gcc packages on the command line. -- Ricardo From mboxrd@z Thu Jan 1 00:00:00 1970 From: zimoun Subject: Re: collect2: fatal error: cannot find 'ld' Date: Mon, 11 Feb 2019 13:07:50 +0100 Message-ID: References: <87wom9kp1q.fsf@elephly.net> <87r2celejh.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:38346) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gtANi-0001cS-0q for help-guix@gnu.org; Mon, 11 Feb 2019 07:08:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gtANg-0005oN-3C for help-guix@gnu.org; Mon, 11 Feb 2019 07:08:13 -0500 Received: from mail-qk1-x72f.google.com ([2607:f8b0:4864:20::72f]:41835) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gtANd-0005ks-Te for help-guix@gnu.org; Mon, 11 Feb 2019 07:08:10 -0500 Received: by mail-qk1-x72f.google.com with SMTP id u188so6218437qkh.8 for ; Mon, 11 Feb 2019 04:08:03 -0800 (PST) In-Reply-To: <87r2celejh.fsf@elephly.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ricardo Wurmus Cc: Help Guix > I still think that we should hide the plain gcc packages on the command > line. I agree. I also fell in the trap. :-) Installed gcc+binutils+etc. instead of gcc-toolchain and then weird linking issue. Thank you for your confirmation. All the best, simon From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Subject: Re: collect2: fatal error: cannot find 'ld' Date: Tue, 12 Feb 2019 17:44:35 +0100 Message-ID: <87va1pgdn0.fsf@gnu.org> References: <87wom9kp1q.fsf@elephly.net> <87r2celejh.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]:39316) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gtbAn-0003zk-99 for help-guix@gnu.org; Tue, 12 Feb 2019 11:44:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gtbAl-0005iP-Ch for help-guix@gnu.org; Tue, 12 Feb 2019 11:44:40 -0500 Received: from hera.aquilenet.fr ([2a0c:e300::1]:59166) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gtbAj-0005g0-KO for help-guix@gnu.org; Tue, 12 Feb 2019 11:44:37 -0500 In-Reply-To: <87r2celejh.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 11 Feb 2019 13:01:38 +0100") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ricardo Wurmus Cc: Help Guix Ricardo Wurmus skribis: > I still think that we should hide the plain gcc packages on the command > line. Agreed. Ludo=E2=80=99. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: collect2: fatal error: cannot find 'ld' Date: Tue, 12 Feb 2019 23:23:54 +0100 Message-ID: <87tvh8ir2d.fsf@elephly.net> References: <87wom9kp1q.fsf@elephly.net> <87r2celejh.fsf@elephly.net> <87va1pgdn0.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:56754) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gth0w-00082U-7A for help-guix@gnu.org; Tue, 12 Feb 2019 17:58:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gtgir-0002Tl-Sq for help-guix@gnu.org; Tue, 12 Feb 2019 17:40:17 -0500 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21113) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gtgiq-00028r-0s for help-guix@gnu.org; Tue, 12 Feb 2019 17:40:13 -0500 In-reply-to: <87va1pgdn0.fsf@gnu.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: Help Guix --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ludovic Court=C3=A8s writes: > Ricardo Wurmus skribis: > >> I still think that we should hide the plain gcc packages on the command >> line. > > Agreed. Is this the right way to hide the package (see patch)? I searched for GCC on the command line with =E2=80=9Cguix package --search=3Dgcc=E2=80=9D = and the results did not include the plain gcc packages. --=-=-= Content-Type: text/x-patch Content-Disposition: inline; filename=0001-gnu-gcc-4.7-Hide-package.patch >From 8cbb0b446930264b7f2a771cc95534e14dde9edd Mon Sep 17 00:00:00 2001 From: Ricardo Wurmus Date: Tue, 12 Feb 2019 23:21:48 +0100 Subject: [PATCH] gnu: gcc-4.7: Hide package. * gnu/packages/gcc.scm (gcc-4.7): Wrap in "hidden-package" expression. --- gnu/packages/gcc.scm | 409 ++++++++++++++++++++++--------------------- 1 file changed, 205 insertions(+), 204 deletions(-) diff --git a/gnu/packages/gcc.scm b/gnu/packages/gcc.scm index 1f1e80dde..7f6000f03 100644 --- a/gnu/packages/gcc.scm +++ b/gnu/packages/gcc.scm @@ -139,220 +139,221 @@ where the OS part is overloaded to denote a specific ABI---into GCC (gcc-configure-flags-for-triplet triplet)) (maybe-target-tools)))))) - (package - (name "gcc") - (version "4.7.4") - (source (origin - (method url-fetch) - (uri (string-append "mirror://gnu/gcc/gcc-" - version "/gcc-" version ".tar.bz2")) - (sha256 - (base32 - "10k2k71kxgay283ylbbhhs51cl55zn2q38vj5pk4k950qdnirrlj")) - (patches (search-patches "gcc-4-compile-with-gcc-5.patch" - "gcc-fix-texi2pod.patch")))) - (build-system gnu-build-system) - - ;; Separate out the run-time support libraries because all the - ;; dynamic-linked objects depend on it. - (outputs '("out" ;commands, etc. (60+ MiB) - "lib" ;libgcc_s, libgomp, etc. (15+ MiB) - "debug")) ;debug symbols of run-time libraries - - (inputs `(("gmp" ,gmp) - ("mpfr" ,mpfr) - ("mpc" ,mpc) - ("libelf" ,libelf) - ("zlib" ,zlib))) - - ;; GCC < 5 is one of the few packages that doesn't ship .info files. - ;; Newer texinfos fail to build the manual, so we use an older one. - (native-inputs `(("perl" ,perl) ;for manpages - ("texinfo" ,texinfo-5))) - - (arguments - `(#:out-of-source? #t - #:configure-flags ,(configure-flags) - #:make-flags - ;; None of the flags below are needed when doing a Canadian cross. - ;; TODO: Simplify this. - ,(if (%current-target-system) - (if stripped? - ''("CFLAGS=-g0 -O2") - ''()) - `(let* ((libc (assoc-ref %build-inputs "libc")) - (libc-native (or (assoc-ref %build-inputs "libc-native") - libc))) - `(,@(if libc - (list (string-append "LDFLAGS_FOR_TARGET=" - "-B" libc "/lib " - "-Wl,-dynamic-linker " - "-Wl," libc - ,(glibc-dynamic-linker))) - '()) - - ;; Native programs like 'genhooks' also need that right. - ,(string-append "LDFLAGS=" - "-Wl,-rpath=" libc-native "/lib " - "-Wl,-dynamic-linker " - "-Wl," libc-native ,(glibc-dynamic-linker)) - ,(string-append "BOOT_CFLAGS=-O2 " - ,(if stripped? "-g0" "-g"))))) - - #:tests? #f - - #:phases - (modify-phases %standard-phases - (add-before 'configure 'pre-configure - (lambda* (#:key inputs outputs #:allow-other-keys) - (let ((libdir ,(libdir)) - (libc (assoc-ref inputs "libc"))) - (when libc - ;; The following is not performed for `--without-headers' - ;; cross-compiler builds. - - ;; Join multi-line definitions of GLIBC_DYNAMIC_LINKER* into a - ;; single line, to allow the next step to work properly. - (for-each - (lambda (x) - (substitute* (find-files "gcc/config" - "^(linux|gnu|sysv4)(64|-elf|-eabi)?\\.h$") - (("(#define (GLIBC|GNU_USER)_DYNAMIC_LINKER.*)\\\\\n$" _ line) - line))) - '(1 2 3)) - - ;; Fix the dynamic linker's file name. + (hidden-package + (package + (name "gcc") + (version "4.7.4") + (source (origin + (method url-fetch) + (uri (string-append "mirror://gnu/gcc/gcc-" + version "/gcc-" version ".tar.bz2")) + (sha256 + (base32 + "10k2k71kxgay283ylbbhhs51cl55zn2q38vj5pk4k950qdnirrlj")) + (patches (search-patches "gcc-4-compile-with-gcc-5.patch" + "gcc-fix-texi2pod.patch")))) + (build-system gnu-build-system) + + ;; Separate out the run-time support libraries because all the + ;; dynamic-linked objects depend on it. + (outputs '("out" ;commands, etc. (60+ MiB) + "lib" ;libgcc_s, libgomp, etc. (15+ MiB) + "debug")) ;debug symbols of run-time libraries + + (inputs `(("gmp" ,gmp) + ("mpfr" ,mpfr) + ("mpc" ,mpc) + ("libelf" ,libelf) + ("zlib" ,zlib))) + + ;; GCC < 5 is one of the few packages that doesn't ship .info files. + ;; Newer texinfos fail to build the manual, so we use an older one. + (native-inputs `(("perl" ,perl) ;for manpages + ("texinfo" ,texinfo-5))) + + (arguments + `(#:out-of-source? #t + #:configure-flags ,(configure-flags) + #:make-flags + ;; None of the flags below are needed when doing a Canadian cross. + ;; TODO: Simplify this. + ,(if (%current-target-system) + (if stripped? + ''("CFLAGS=-g0 -O2") + ''()) + `(let* ((libc (assoc-ref %build-inputs "libc")) + (libc-native (or (assoc-ref %build-inputs "libc-native") + libc))) + `(,@(if libc + (list (string-append "LDFLAGS_FOR_TARGET=" + "-B" libc "/lib " + "-Wl,-dynamic-linker " + "-Wl," libc + ,(glibc-dynamic-linker))) + '()) + + ;; Native programs like 'genhooks' also need that right. + ,(string-append "LDFLAGS=" + "-Wl,-rpath=" libc-native "/lib " + "-Wl,-dynamic-linker " + "-Wl," libc-native ,(glibc-dynamic-linker)) + ,(string-append "BOOT_CFLAGS=-O2 " + ,(if stripped? "-g0" "-g"))))) + + #:tests? #f + + #:phases + (modify-phases %standard-phases + (add-before 'configure 'pre-configure + (lambda* (#:key inputs outputs #:allow-other-keys) + (let ((libdir ,(libdir)) + (libc (assoc-ref inputs "libc"))) + (when libc + ;; The following is not performed for `--without-headers' + ;; cross-compiler builds. + + ;; Join multi-line definitions of GLIBC_DYNAMIC_LINKER* into a + ;; single line, to allow the next step to work properly. + (for-each + (lambda (x) (substitute* (find-files "gcc/config" "^(linux|gnu|sysv4)(64|-elf|-eabi)?\\.h$") - (("#define (GLIBC|GNU_USER)_DYNAMIC_LINKER([^ \t]*).*$" - _ gnu-user suffix) - (format #f "#define ~a_DYNAMIC_LINKER~a \"~a\"~%" - gnu-user suffix - (string-append libc ,(glibc-dynamic-linker))))) - - ;; Tell where to find libstdc++, libc, and `?crt*.o', except - ;; `crt{begin,end}.o', which come with GCC. - (substitute* (find-files "gcc/config" - "^gnu-user.*\\.h$") - (("#define GNU_USER_TARGET_LIB_SPEC (.*)$" _ suffix) - ;; Help libgcc_s.so be found (see also below.) Always use - ;; '-lgcc_s' so that libgcc_s.so is always found by those - ;; programs that use 'pthread_cancel' (glibc dlopens - ;; libgcc_s.so when pthread_cancel support is needed, but - ;; having it in the application's RUNPATH isn't enough; see - ;; .) - ;; - ;; NOTE: The '-lgcc_s' added below needs to be removed in a - ;; later phase of %gcc-static. If you change the string - ;; below, make sure to update the relevant code in - ;; %gcc-static package as needed. - (format #f "#define GNU_USER_TARGET_LIB_SPEC \ + (("(#define (GLIBC|GNU_USER)_DYNAMIC_LINKER.*)\\\\\n$" _ line) + line))) + '(1 2 3)) + + ;; Fix the dynamic linker's file name. + (substitute* (find-files "gcc/config" + "^(linux|gnu|sysv4)(64|-elf|-eabi)?\\.h$") + (("#define (GLIBC|GNU_USER)_DYNAMIC_LINKER([^ \t]*).*$" + _ gnu-user suffix) + (format #f "#define ~a_DYNAMIC_LINKER~a \"~a\"~%" + gnu-user suffix + (string-append libc ,(glibc-dynamic-linker))))) + + ;; Tell where to find libstdc++, libc, and `?crt*.o', except + ;; `crt{begin,end}.o', which come with GCC. + (substitute* (find-files "gcc/config" + "^gnu-user.*\\.h$") + (("#define GNU_USER_TARGET_LIB_SPEC (.*)$" _ suffix) + ;; Help libgcc_s.so be found (see also below.) Always use + ;; '-lgcc_s' so that libgcc_s.so is always found by those + ;; programs that use 'pthread_cancel' (glibc dlopens + ;; libgcc_s.so when pthread_cancel support is needed, but + ;; having it in the application's RUNPATH isn't enough; see + ;; .) + ;; + ;; NOTE: The '-lgcc_s' added below needs to be removed in a + ;; later phase of %gcc-static. If you change the string + ;; below, make sure to update the relevant code in + ;; %gcc-static package as needed. + (format #f "#define GNU_USER_TARGET_LIB_SPEC \ \"-L~a/lib %{!static:-rpath=~a/lib %{!static-libgcc:-rpath=~a/lib -lgcc_s}} \" ~a" - libc libc libdir suffix)) - (("#define GNU_USER_TARGET_STARTFILE_SPEC.*$" line) - (format #f "#define STANDARD_STARTFILE_PREFIX_1 \"~a/lib\" + libc libc libdir suffix)) + (("#define GNU_USER_TARGET_STARTFILE_SPEC.*$" line) + (format #f "#define STANDARD_STARTFILE_PREFIX_1 \"~a/lib\" #define STANDARD_STARTFILE_PREFIX_2 \"\" ~a" - libc line))) - - ;; The rs6000 (a.k.a. powerpc) config in GCC does not use - ;; GNU_USER_* defines. Do the above for this case. - (substitute* - "gcc/config/rs6000/sysv4.h" - (("#define LIB_LINUX_SPEC (.*)$" _ suffix) - (format #f "#define LIB_LINUX_SPEC \ + libc line))) + + ;; The rs6000 (a.k.a. powerpc) config in GCC does not use + ;; GNU_USER_* defines. Do the above for this case. + (substitute* + "gcc/config/rs6000/sysv4.h" + (("#define LIB_LINUX_SPEC (.*)$" _ suffix) + (format #f "#define LIB_LINUX_SPEC \ \"-L~a/lib %{!static:-rpath=~a/lib %{!static-libgcc:-rpath=~a/lib -lgcc_s}} \" ~a" - libc libc libdir suffix)) - (("#define STARTFILE_LINUX_SPEC.*$" line) - (format #f "#define STANDARD_STARTFILE_PREFIX_1 \"~a/lib\" + libc libc libdir suffix)) + (("#define STARTFILE_LINUX_SPEC.*$" line) + (format #f "#define STANDARD_STARTFILE_PREFIX_1 \"~a/lib\" #define STANDARD_STARTFILE_PREFIX_2 \"\" ~a" - libc line)))) - - ;; Don't retain a dependency on the build-time sed. - (substitute* "fixincludes/fixincl.x" - (("static char const sed_cmd_z\\[\\] =.*;") - "static char const sed_cmd_z[] = \"sed\";")) - - ;; Aarch64 support didn't land in GCC until the 4.8 series. - (when (file-exists? "gcc/config/aarch64") - ;; Force Aarch64 libdir to be /lib and not /lib64 - (substitute* "gcc/config/aarch64/t-aarch64-linux" - (("lib64") "lib"))) - - (when (file-exists? "libbacktrace") - ;; GCC 4.8+ comes with libbacktrace. By default it builds - ;; with -Werror, which fails with a -Wcast-qual error in glibc - ;; 2.21's stdlib-bsearch.h. Remove -Werror. - (substitute* "libbacktrace/configure" - (("WARN_FLAGS=(.*)-Werror" _ flags) - (string-append "WARN_FLAGS=" flags))) - - (when (file-exists? "libsanitizer/libbacktrace") - ;; Same in libsanitizer's bundled copy (!) found in 4.9+. - (substitute* "libsanitizer/libbacktrace/Makefile.in" - (("-Werror") - "")))) - - ;; Add a RUNPATH to libstdc++.so so that it finds libgcc_s. - ;; See - ;; and . - (substitute* "libstdc++-v3/src/Makefile.in" - (("^OPT_LDFLAGS = ") - "OPT_LDFLAGS = -Wl,-rpath=$(libdir) ")) - - ;; Move libstdc++*-gdb.py to the "lib" output to avoid a - ;; circularity between "out" and "lib". (Note: - ;; --with-python-dir is useless because it imposes $(prefix) as - ;; the parent directory.) - (substitute* "libstdc++-v3/python/Makefile.in" - (("pythondir = .*$") - (string-append "pythondir = " libdir "/share" - "/gcc-$(gcc_version)/python\n"))) - - ;; Avoid another circularity between the outputs: this #define - ;; ends up in auto-host.h in the "lib" output, referring to - ;; "out". (This variable is used to augment cpp's search path, - ;; but there's nothing useful to look for here.) - (substitute* "gcc/config.in" - (("PREFIX_INCLUDE_DIR") - "PREFIX_INCLUDE_DIR_isnt_necessary_here")) - #t))) - - (add-after 'configure 'post-configure - (lambda _ - ;; Don't store configure flags, to avoid retaining references to - ;; build-time dependencies---e.g., `--with-ppl=/gnu/store/xxx'. - (substitute* "Makefile" - (("^TOPLEVEL_CONFIGURE_ARGUMENTS=(.*)$" _ rest) - "TOPLEVEL_CONFIGURE_ARGUMENTS=\n")) - #t))))) - - (native-search-paths - ;; Use the language-specific variables rather than 'CPATH' because they - ;; are equivalent to '-isystem' whereas 'CPATH' is equivalent to '-I'. - ;; The intent is to allow headers that are in the search path to be - ;; treated as "system headers" (headers exempt from warnings) just like - ;; the typical /usr/include headers on an FHS system. - (list (search-path-specification - (variable "C_INCLUDE_PATH") - (files '("include"))) - (search-path-specification - (variable "CPLUS_INCLUDE_PATH") - (files '("include"))) - (search-path-specification - (variable "LIBRARY_PATH") - (files '("lib" "lib64"))))) - - (properties `((gcc-libc . ,(assoc-ref inputs "libc")))) - (synopsis "GNU Compiler Collection") - (description - "GCC is the GNU Compiler Collection. It provides compiler front-ends + libc line)))) + + ;; Don't retain a dependency on the build-time sed. + (substitute* "fixincludes/fixincl.x" + (("static char const sed_cmd_z\\[\\] =.*;") + "static char const sed_cmd_z[] = \"sed\";")) + + ;; Aarch64 support didn't land in GCC until the 4.8 series. + (when (file-exists? "gcc/config/aarch64") + ;; Force Aarch64 libdir to be /lib and not /lib64 + (substitute* "gcc/config/aarch64/t-aarch64-linux" + (("lib64") "lib"))) + + (when (file-exists? "libbacktrace") + ;; GCC 4.8+ comes with libbacktrace. By default it builds + ;; with -Werror, which fails with a -Wcast-qual error in glibc + ;; 2.21's stdlib-bsearch.h. Remove -Werror. + (substitute* "libbacktrace/configure" + (("WARN_FLAGS=(.*)-Werror" _ flags) + (string-append "WARN_FLAGS=" flags))) + + (when (file-exists? "libsanitizer/libbacktrace") + ;; Same in libsanitizer's bundled copy (!) found in 4.9+. + (substitute* "libsanitizer/libbacktrace/Makefile.in" + (("-Werror") + "")))) + + ;; Add a RUNPATH to libstdc++.so so that it finds libgcc_s. + ;; See + ;; and . + (substitute* "libstdc++-v3/src/Makefile.in" + (("^OPT_LDFLAGS = ") + "OPT_LDFLAGS = -Wl,-rpath=$(libdir) ")) + + ;; Move libstdc++*-gdb.py to the "lib" output to avoid a + ;; circularity between "out" and "lib". (Note: + ;; --with-python-dir is useless because it imposes $(prefix) as + ;; the parent directory.) + (substitute* "libstdc++-v3/python/Makefile.in" + (("pythondir = .*$") + (string-append "pythondir = " libdir "/share" + "/gcc-$(gcc_version)/python\n"))) + + ;; Avoid another circularity between the outputs: this #define + ;; ends up in auto-host.h in the "lib" output, referring to + ;; "out". (This variable is used to augment cpp's search path, + ;; but there's nothing useful to look for here.) + (substitute* "gcc/config.in" + (("PREFIX_INCLUDE_DIR") + "PREFIX_INCLUDE_DIR_isnt_necessary_here")) + #t))) + + (add-after 'configure 'post-configure + (lambda _ + ;; Don't store configure flags, to avoid retaining references to + ;; build-time dependencies---e.g., `--with-ppl=/gnu/store/xxx'. + (substitute* "Makefile" + (("^TOPLEVEL_CONFIGURE_ARGUMENTS=(.*)$" _ rest) + "TOPLEVEL_CONFIGURE_ARGUMENTS=\n")) + #t))))) + + (native-search-paths + ;; Use the language-specific variables rather than 'CPATH' because they + ;; are equivalent to '-isystem' whereas 'CPATH' is equivalent to '-I'. + ;; The intent is to allow headers that are in the search path to be + ;; treated as "system headers" (headers exempt from warnings) just like + ;; the typical /usr/include headers on an FHS system. + (list (search-path-specification + (variable "C_INCLUDE_PATH") + (files '("include"))) + (search-path-specification + (variable "CPLUS_INCLUDE_PATH") + (files '("include"))) + (search-path-specification + (variable "LIBRARY_PATH") + (files '("lib" "lib64"))))) + + (properties `((gcc-libc . ,(assoc-ref inputs "libc")))) + (synopsis "GNU Compiler Collection") + (description + "GCC is the GNU Compiler Collection. It provides compiler front-ends for several languages, including C, C++, Objective-C, Fortran, Java, Ada, and Go. It also includes runtime support libraries for these languages.") - (license gpl3+) - (supported-systems (delete "aarch64-linux" %supported-systems)) - (home-page "https://gcc.gnu.org/")))) + (license gpl3+) + (supported-systems (delete "aarch64-linux" %supported-systems)) + (home-page "https://gcc.gnu.org/"))))) (define-public gcc-4.8 (package (inherit gcc-4.7) -- 2.20.1 --=-=-= Content-Type: text/plain -- Ricardo --=-=-=-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: zimoun Subject: Re: collect2: fatal error: cannot find 'ld' Date: Fri, 22 Feb 2019 16:51:02 +0100 Message-ID: References: <87wom9kp1q.fsf@elephly.net> <87r2celejh.fsf@elephly.net> <87va1pgdn0.fsf@gnu.org> <87tvh8ir2d.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]:34294) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gxD6Z-0004Ka-If for help-guix@gnu.org; Fri, 22 Feb 2019 10:51:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gxD6Y-0003dp-R3 for help-guix@gnu.org; Fri, 22 Feb 2019 10:51:15 -0500 In-Reply-To: <87tvh8ir2d.fsf@elephly.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ricardo Wurmus Cc: Help Guix Hi Ricardo, On Tue, 12 Feb 2019 at 23:24, Ricardo Wurmus wrote: > Is this the right way to hide the package (see patch)? I searched for > GCC on the command line with =E2=80=9Cguix package --search=3Dgcc=E2=80= =9D and the results > did not include the plain gcc packages. The `hidden-package` function, is it documented somewhere? I mean more than the docstring in packages.scm. ;-) Thank you in advance for any pointer. All the best, simon From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: collect2: fatal error: cannot find 'ld' Date: Fri, 22 Feb 2019 16:55:05 +0100 Message-ID: <874l8v4y3q.fsf@elephly.net> References: <87wom9kp1q.fsf@elephly.net> <87r2celejh.fsf@elephly.net> <87va1pgdn0.fsf@gnu.org> <87tvh8ir2d.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]:36442) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gxDBe-0001G8-I7 for help-guix@gnu.org; Fri, 22 Feb 2019 10:56:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gxDBP-0002Xe-9P for help-guix@gnu.org; Fri, 22 Feb 2019 10:56:17 -0500 In-reply-to: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: zimoun Cc: Help Guix Hi Simon, > On Tue, 12 Feb 2019 at 23:24, Ricardo Wurmus wrote: > >> Is this the right way to hide the package (see patch)? I searched for >> GCC on the command line with =E2=80=9Cguix package --search=3Dgcc=E2=80= =9D and the results >> did not include the plain gcc packages. > > The `hidden-package` function, is it documented somewhere? > I mean more than the docstring in packages.scm. ;-) I don=E2=80=99t think it is documented elsewhere. It=E2=80=99s purpose is = to hide the package from the command line interface. --=20 Ricardo From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Subject: Re: collect2: fatal error: cannot find 'ld' Date: Mon, 11 Mar 2019 16:53:30 +0100 Message-ID: <87d0mxv24l.fsf@gnu.org> References: <87wom9kp1q.fsf@elephly.net> <87r2celejh.fsf@elephly.net> <87va1pgdn0.fsf@gnu.org> <87tvh8ir2d.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]:46578) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h3NGJ-0006QH-0f for help-guix@gnu.org; Mon, 11 Mar 2019 11:54:47 -0400 In-Reply-To: <87tvh8ir2d.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 12 Feb 2019 23:23:54 +0100") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ricardo Wurmus Cc: Help Guix Hello! Ricardo Wurmus skribis: > Ludovic Court=C3=A8s writes: > >> Ricardo Wurmus skribis: >> >>> I still think that we should hide the plain gcc packages on the command >>> line. >> >> Agreed. > > Is this the right way to hide the package (see patch)? I searched for > GCC on the command line with =E2=80=9Cguix package --search=3Dgcc=E2=80= =9D and the results > did not include the plain gcc packages. It still includes the =E2=80=98gcc-toolchain=E2=80=99 packages, right? > From 8cbb0b446930264b7f2a771cc95534e14dde9edd Mon Sep 17 00:00:00 2001 > From: Ricardo Wurmus > Date: Tue, 12 Feb 2019 23:21:48 +0100 > Subject: [PATCH] gnu: gcc-4.7: Hide package. > > * gnu/packages/gcc.scm (gcc-4.7): Wrap in "hidden-package" expression. Alternately you could simply add a =E2=80=98properties=E2=80=99 field (with= a comment), which would make the diff smaller. Go for it! Thanks, Ludo=E2=80=99. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: collect2: fatal error: cannot find 'ld' Date: Thu, 09 May 2019 23:20:43 +0200 Message-ID: <87r297s4t0.fsf@elephly.net> References: <87wom9kp1q.fsf@elephly.net> <87r2celejh.fsf@elephly.net> <87va1pgdn0.fsf@gnu.org> <87tvh8ir2d.fsf@elephly.net> <87d0mxv24l.fsf@gnu.org> 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]:51737) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hOqTI-0000QU-29 for help-guix@gnu.org; Thu, 09 May 2019 17:20:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hOqTH-0007bZ-4I for help-guix@gnu.org; Thu, 09 May 2019 17:20:56 -0400 In-reply-to: <87d0mxv24l.fsf@gnu.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: Help Guix Ludovic Court=C3=A8s writes: > Hello! > > Ricardo Wurmus skribis: > >> Ludovic Court=C3=A8s writes: >> >>> Ricardo Wurmus skribis: >>> >>>> I still think that we should hide the plain gcc packages on the command >>>> line. >>> >>> Agreed. >> >> Is this the right way to hide the package (see patch)? I searched for >> GCC on the command line with =E2=80=9Cguix package --search=3Dgcc=E2=80= =9D and the results >> did not include the plain gcc packages. > > It still includes the =E2=80=98gcc-toolchain=E2=80=99 packages, right? Yes. > Go for it! Done! --=20 Ricardo