From: Danny Milosavljevic <dannym@scratchpost.org>
To: guix-devel@gnu.org
Subject: Re: WIP pypy3.3 - tests still fail? Anyone see why?
Date: Sat, 8 Oct 2016 10:09:11 +0200 [thread overview]
Message-ID: <20161008100911.7b481a42@scratchpost.org> (raw)
In-Reply-To: <20161007121231.5f00a462@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 17 bytes --]
and the patch...
[-- Attachment #2: pypy3.3-fix-compiler.patch --]
[-- Type: text/x-patch, Size: 1385 bytes --]
--- /tmp/sysconfig_pypy.py 2016-09-14 00:38:36.325334296 +0200
+++ pypy3.3-v5.2.0-alpha1-src/lib-python/3/distutils/sysconfig_pypy.py 2016-09-14 00:37:55.068908258 +0200
@@ -123,6 +123,19 @@
optional C speedup components.
"""
if compiler.compiler_type == "unix":
+ varnames = ["CC", "CXX", "LDSHARED", "CPP", "LDFLAGS", "CFLAGS", "CPPFLAGS", "AR", "ARFLAGS", "OPT", "CFLAGS", "CCSHARED", "SHLIB_SUFFIX"]
+ cfg = get_config_vars()
+ g = {}
+ for varname in varnames:
+ g[varname] = os.environ.get(varname) or cfg.get(varname)
+ cc = g["CC"] or "cc"
+ cpp = g["CPP"] if "CPP" in os.environ else ("{} -E".format(g["CC"]))
+ cc_cmd = "{} {}".format(g["CC"], g["CFLAGS"] or "")
+ ccshared = g["CCSHARED"] or ""
+ cxx = g["CXX"]
+ ldshared = "{} -shared {} {} {}".format(g["LDSHARED"] or g["CC"], os.environ.get("LDFLAGS", ""), os.environ.get("CFLAGS", ""), os.environ.get("CPPFLAGS", ""))
+ archiver = "{} {}".format(g["AR"], g["ARFLAGS"])
+ compiler.set_executables(preprocessor=cpp, compiler=cc_cmd, compiler_so=cc_cmd + " " + ccshared, compiler_cxx=cxx, linker_so=ldshared, linker_exe=cc, archiver=archiver)
compiler.compiler_so.extend(['-O2', '-fPIC', '-Wimplicit'])
compiler.shared_lib_extension = get_config_var('SO')
if "CPPFLAGS" in os.environ:
next prev parent reply other threads:[~2016-10-08 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 10:12 WIP pypy3.3 - tests still fail? Anyone see why? Danny Milosavljevic
2016-10-08 8:09 ` Danny Milosavljevic [this message]
2016-10-08 17:27 ` Danny Milosavljevic
2016-10-09 6:51 ` Leo Famulari
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=20161008100911.7b481a42@scratchpost.org \
--to=dannym@scratchpost.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).