unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Timothy Sample <samplet@ngyro.com>
Cc: guix-devel@gnu.org
Subject: Re: Help needed: Updating GHC to 8.4.3
Date: Tue, 28 Aug 2018 18:02:42 +0200	[thread overview]
Message-ID: <87in3ubhst.fsf@elephly.net> (raw)
In-Reply-To: <87pny55hgy.fsf@ngyro.com>


Hey Tim,

thank you so much for helping with GHC!

> To summarize, there are three problems with the original patch:
>
>   1. it uses “ld.bfd” instead of “ld” (skipping the wrapper);
>   2. it references native tools instead of target tools; and
>   3. it requires certain tools to be available from “PATH”.
>
> Problems 2 and 3 affect GHC 8.0.2 too.  Problem 1 is new.  At this
> point, I’m thinking that using either “--disable-ld-override” or “LD=ld”
> might be the most reasonable approach (they do the same thing, but the
> second one is clearer IMO).  It means that GHC will look for GCC and
> friends in “PATH”, but this is how GCC itself works currently with
> “binutils”.  It has the added benefit that these will likely be the
> tools for the target platform.
>
> WDYT?

I set the LD environment variable as suggested and the package build is
getting much further.  Thank you!

I’m not too concerned about the 2nd and 3rd problems, because at least
GHC 8.4.3 will likely be good enough to build all of our Haskell
packages.

We should record the other problems as bugs on bug-guix@gnu.org.

--
Ricardo

      reply	other threads:[~2018-08-28 16:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17 15:08 Help needed: Updating GHC to 8.4.3 Ricardo Wurmus
2018-08-20 10:13 ` Ludovic Courtès
2018-08-20 10:36   ` Ricardo Wurmus
2018-08-25  5:07     ` Timothy Sample
2018-08-25 19:28       ` Timothy Sample
2018-08-26 14:29         ` Timothy Sample
2018-08-28 16:02           ` Ricardo Wurmus [this message]

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=87in3ubhst.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=samplet@ngyro.com \
    /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).