From: Federico Beffa <beffa@ieee.org>
To: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 3/3] gnu: Add ghc.
Date: Sun, 22 Mar 2015 21:31:46 +0100 [thread overview]
Message-ID: <CAKrPhPNQf66zQtBB-vUNa_9QBZ8m8SmtggMBRNuXm70f5YTK9w@mail.gmail.com> (raw)
Mark H Weaver <mhw@netris.org> writes:
> All attempts to build ghc on i686 have failed, according to Hydra.
>
> http://hydra.gnu.org/job/gnu/master/ghc-7.8.4.i686-linux/all
> http://hydra.gnu.org/build/331946/log/tail-reload
>
> Would you be willing to take a look?
I've already had a look last week-end, but I've not found a fix yet.
The error message
configure: error: cannot determine current directory
is the same that I was getting before patching the file
ghc-7.8.4/utils/ghc-pwd/dist-install/build/tmp/ghc-pwd
in the binary distribution for x86_64.
ldd on that file for the i386 executable gives (from a Debian shell):
linux-gate.so.1 => (0xf779c000)
librt.so.1 => /lib32/librt.so.1 (0xf777b000)
libutil.so.1 => /lib32/libutil.so.1 (0xf7777000)
libdl.so.2 => /lib32/libdl.so.2 (0xf7773000)
libgmp.so.10 => not found
libm.so.6 => /lib32/libm.so.6 (0xf774d000)
libHSdirectory-1.2.1.0-ghc7.8.4.so => not found
libHSunix-2.7.0.1-ghc7.8.4.so => not found
libHSbytestring-0.10.4.0-ghc7.8.4.so => not found
libHStime-1.4.2-ghc7.8.4.so => not found
libHSold-locale-1.0.0.6-ghc7.8.4.so => not found
libHSdeepseq-1.3.0.2-ghc7.8.4.so => not found
libHSarray-0.5.0.0-ghc7.8.4.so => not found
libHSfilepath-1.3.0.2-ghc7.8.4.so => not found
libHSbase-4.7.0.2-ghc7.8.4.so => not found
libHSinteger-gmp-0.5.1.0-ghc7.8.4.so => not found
libHSghc-prim-0.3.1.0-ghc7.8.4.so => not found
libHSrts-ghc7.8.4.so => not found
libffi.so.6 => not found
libc.so.6 => /lib32/libc.so.6 (0xf75e5000)
libpthread.so.0 => /lib32/libpthread.so.0 (0xf75ca000)
/lib/ld-linux.so.2 (0xf779d000)
while for x86_64 gives:
linux-vdso.so.1 => (0x00007fff94fe8000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fe65ca09000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007fe65c806000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fe65c602000)
libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 (0x00007fe65c392000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fe65c110000)
libHSdirectory-1.2.1.0-ghc7.8.4.so => not found
libHSunix-2.7.0.1-ghc7.8.4.so => not found
libHSbytestring-0.10.4.0-ghc7.8.4.so => not found
libHStime-1.4.2-ghc7.8.4.so => not found
libHSold-locale-1.0.0.6-ghc7.8.4.so => not found
libHSdeepseq-1.3.0.2-ghc7.8.4.so => not found
libHSarray-0.5.0.0-ghc7.8.4.so => not found
libHSfilepath-1.3.0.2-ghc7.8.4.so => not found
libHSbase-4.7.0.2-ghc7.8.4.so => not found
libHSinteger-gmp-0.5.1.0-ghc7.8.4.so => not found
libHSghc-prim-0.3.1.0-ghc7.8.4.so => not found
libHSrts-ghc7.8.4.so => not found
libffi.so.6 => not found
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fe65bd80000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007fe65bb63000)
/lib64/ld-linux-x86-64.so.2 (0x00007fe65cc29000)
All haskell libraries are found with the help of the ghc build system and I
patch the hardcoded interpreter with
(system* "patchelf" "--set-interpreter"
(string-append (assoc-ref inputs "libc")
(glibc-dynamic-linker)))
I'm not sure about the difference between "linux-vdso.so.1" and
"linux-gate.so.1". As far as I understand they are the gateway into the
kernel for system calls, but have zero experience with that.
Any help would be appreciated.
Regards,
Fede
next reply other threads:[~2015-03-22 20:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 20:31 Federico Beffa [this message]
2015-03-25 21:20 ` [PATCH 3/3] gnu: Add ghc Ludovic Courtès
2015-03-28 19:15 ` Federico Beffa
2015-03-31 19:31 ` Mark H Weaver
-- strict thread matches above, loose matches on Subject: below --
2015-02-26 19:54 Federico Beffa
2015-03-01 12:44 ` Federico Beffa
2015-03-01 14:55 ` Ludovic Courtès
2015-03-02 6:29 ` Mark H Weaver
2015-03-02 11:09 ` Federico Beffa
2015-03-03 12:24 ` Ludovic Courtès
2015-03-05 8:26 ` Federico Beffa
2015-03-08 21:36 ` Ludovic Courtès
2015-03-21 23:21 ` Mark H Weaver
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=CAKrPhPNQf66zQtBB-vUNa_9QBZ8m8SmtggMBRNuXm70f5YTK9w@mail.gmail.com \
--to=beffa@ieee.org \
--cc=guix-devel@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).