From mboxrd@z Thu Jan 1 00:00:00 1970 From: Federico Beffa Subject: bug#25882: gcc-wrapper doesn't handle response files Date: Wed, 08 Mar 2017 13:57:10 +0100 Message-ID: <878togudsp.fsf@lupo.i-did-not-set--mail-host-address--so-tickle-me> References: <87o9xepe7l.fsf@gnu.org> <871suajpfh.fsf@lupo.i-did-not-set--mail-host-address--so-tickle-me> <87r329fjcq.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 ([2001:4830:134:3::10]:42069) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1clbAL-0006YA-G4 for bug-guix@gnu.org; Wed, 08 Mar 2017 07:58:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1clbAI-0005Jj-DY for bug-guix@gnu.org; Wed, 08 Mar 2017 07:58:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:47287) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1clbAI-0005Jc-9h for bug-guix@gnu.org; Wed, 08 Mar 2017 07:58:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1clbAI-0006rE-3b for bug-guix@gnu.org; Wed, 08 Mar 2017 07:58:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87r329fjcq.fsf@gnu.org> ("Ludovic =?UTF-8?Q?Court=C3=A8s?="'s message of "Tue, 07 Mar 2017 11:53:57 +0100") 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" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 25882@debbugs.gnu.org ludo@gnu.org (Ludovic Court=C3=A8s) writes: > On closer inspection, it=E2=80=99s an easy change to make. > > Could you test the attached patch with GHC? Thanks for the patch. I've tested it with GHC 8.0.2 and seems to work for it. However, this is an excerpt of the description of the use of response files from the GCC manual: --8<---------------cut here---------------start------------->8--- '@FILE' Read command-line options from FILE. The options read are inserted in place of the original @FILE option. If FILE does not exist, or cannot be read, then the option will be treated literally, and not removed. Options in FILE are separated by whitespace. A whitespace character may be included in an option by surrounding the entire option in either single or double quotes. Any character (including a backslash) may be included by prefixing the character to be included with a backslash. The FILE may itself contain additional @FILE options; any such options will be processed recursively. --8<---------------cut here---------------end--------------->8--- The patch doesn't seems to handle several things, such as missing files, recursion and use of quotes. I would suggest to try to match the expected behavior in its entirety (or at least a larger part thereof). Fede