Opened 10 years ago
Closed 9 years ago
#43885 closed defect (wontfix)
+arm_runtime is sometimes selected even though SDK support is not available
Reported by: | ci42 | Owned by: | jeremyhu (Jeremy Huddleston Sequoia) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.0 |
Keywords: | Cc: | cooljeanius (Eric Gallager) | |
Port: | clang-3.0 |
Description
See the attached log file.
Attachments (1)
Change History (6)
Changed 10 years ago by ci42
comment:1 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 Changed 10 years ago by ci42
Resolution: | invalid |
---|---|
Status: | closed → reopened |
I didn't selected the arm_runtime variant. I think it was selected automatically because of:
# The iOS SDK was shipped with all Xcode releases after 4.0 if {[info exists xcodeversion] && [vercmp "4.0" ${xcodeversion}] <= 0} { default_variants-append +arm_runtime }
Perhaps this test is not sufficient enough to determine if the requirements are satisfied?
comment:3 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Summary: | clang-3.0 @ 3.0_13 : build failure - /usr/include/machine/limits.h:8:10: fatal error: 'arm/limits.h' file not found #include <arm/limits.h> → +arm_runtime is sometimes selected even though SDK support is not available |
---|
Well, we don't have a way to verify the version of the installed command line tools SDK, so the xcode version is the best proxy we have. Suggestions are welcome, but a proper fix will likely need to come from base.
comment:5 Changed 9 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Resolution: | → wontfix |
---|---|
Status: | reopened → closed |
llvm-3.6 and later don't have this variant any more, so I don't think this is a problem now.
Note: See
TracTickets for help on using
tickets.
Yes. Don't use +arm_runtime if you can't satisfy the requirements.