unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Federico Beffa <beffa@ieee.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 25882@debbugs.gnu.org
Subject: bug#25882: gcc-wrapper doesn't handle response files
Date: Mon, 06 Mar 2017 18:16:50 +0100	[thread overview]
Message-ID: <871suajpfh.fsf@lupo.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87o9xepe7l.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 06 Mar 2017 17:22:38 +0100")

ludo@gnu.org (Ludovic Courtès) writes:

> Federico Beffa <beffa@fbengineering.ch> skribis:
>
>> gcc-wrapper doesn't handle compiler/linker flags passed through
>> response files.
>>
>> One package which recently started using such files is GHC (I believe
>> since 7.10.3).  For this reason we currently need to patch it.
>> However, the problem is with our tool chain wrapper and not with GHC
>> itself.
>>
>> See discussion at
>> https://lists.gnu.org/archive/html/guix-devel/2017-01/msg01981.html
>
> Given that the GHC patch is so small, I have a slight preference for
> keeping ld-wrapper unchanged and using the GHC patch.  To put it
> differently, the GHC patch is smaller and less error-prone than the
> changes that would need to be made in ld-wrapper.

I don't think that it is a good idea because any upstream change around
that code will break our package again and, going forward, we may find
other pieces of software making use of this gcc feature.  The patch is
small, but the effort to find it wasn't.

I like to fix things where the problem is, not working around it.

Fede

  reply	other threads:[~2017-03-06 17:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-26 16:58 bug#25882: gcc-wrapper doesn't handle response files Federico Beffa
2017-03-06 16:22 ` Ludovic Courtès
2017-03-06 17:16   ` Federico Beffa [this message]
2017-03-07 10:53     ` Ludovic Courtès
2017-03-08 12:57       ` Federico Beffa
2017-03-11 13:47         ` Ludovic Courtès
2017-03-12 11:36           ` Federico Beffa
2017-05-25 12:42             ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871suajpfh.fsf@lupo.i-did-not-set--mail-host-address--so-tickle-me \
    --to=beffa@ieee.org \
    --cc=25882@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).