Opened 13 years ago
Closed 13 years ago
#31418 closed defect (fixed)
pypy shouldn't need gcc45
| Reported by: | macporter90210@… | Owned by: | jmroot (Joshua Root) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.3 |
| Keywords: | Cc: | ||
| Port: | pypy |
Description
At one point pypy couldn't compile with the standard gcc-4.2 included in OSX, and so it needs gcc45 port if gcc-4.0 is not available (as in Lion). That problem is now fixed, and gcc-4.2 is sufficient for pypy. Please remove the unnecessary dependency on gcc45 especially as most other ports use versions 4.2, 4.4, 0r 4.0 anyway.
Change History (4)
comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Keywords: | gcc dependency pypy removed |
|---|---|
| Owner: | changed from macports-tickets@… to jmr@… |
comment:2 Changed 13 years ago by jmroot (Joshua Root)
comment:3 Changed 13 years ago by macporter90210@…
Well, its just that I installed pypy with the following patch to the Portfile, thus installing pypy without gcc45. It worked and I have a working pypy port. I am on Lion.
45c45 < configure.compiler gcc-4.0 --- > configure.compiler gcc-4.2
comment:4 Changed 13 years ago by jmroot (Joshua Root)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
The default gc root finder is now shadowstack rather than asmgcc on non-Linux platforms, so that should theoretically remove the incompatibilities with certain compiler versions. In my testing however, using gcc-4.2 still breaks the build. Clang, OTOH, seems to work.
So, the gcc45 dependency is gone for 1.7 (r87473).
Replying to macporter90210@…:
Can you provide a source for this statement? I couldn't find anything on the web site to indicate this, the 1.6 code still defaults to gcc-4.0 and has comments warning against using 4.2 or llvm, and there are issues with gcc-4.2 even on other platforms according to mailing list messages from as recently as August.