From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Re: Required packages Date: Wed, 6 Feb 2013 00:09:23 +0100 Message-ID: <201302060009.23376.andreas@enge.fr> References: <201302041952.22425.andreas@enge.fr> <201302042328.11563.andreas@enge.fr> <87ehgur9h7.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="Boundary-01=_jEZERlS8Fq6rZrK" Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36136) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U2rdt-0000NI-4n for bug-guix@gnu.org; Tue, 05 Feb 2013 18:09:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U2rdq-0001TX-LF for bug-guix@gnu.org; Tue, 05 Feb 2013 18:09:33 -0500 In-Reply-To: <87ehgur9h7.fsf@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Ludovic =?utf-8?q?Court=C3=A8s?= Cc: bug-guix@gnu.org --Boundary-01=_jEZERlS8Fq6rZrK Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Am Dienstag, 5. Februar 2013 schrieb Ludovic Court=C3=A8s: > For GCC, the situation is more complicated, because GCC has a loose tie > to Binutils and libc. For instance, it happily takes whichever =E2=80=98= ld=E2=80=99 > program is in $PATH. It=E2=80=99s more closely tied to libc, though, bec= ause we > explicitly patch its spec strings to refer to it; so at least libc > should be a propagated input of GCC. Sounds good to me. Andreas --Boundary-01=_jEZERlS8Fq6rZrK Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Am Dienstag= , 5. Februar 2013 schrieb Ludovic Court=C3=A8s:

> For GC= C, the situation is more complicated, because GCC has a loose tie

> to Bin= utils and libc. For instance, it happily takes whichever =E2=80=98ld=E2=80= =99

> progra= m is in $PATH. It=E2=80=99s more closely tied to libc, though, because we<= /p>

> explic= itly patch its spec strings to refer to it; so at least libc

> should= be a propagated input of GCC.

&nb= sp;

Sounds good= to me.

&nb= sp;

Andreas

&nb= sp;

--Boundary-01=_jEZERlS8Fq6rZrK--