Message108585
| Author |
mark.dickinson |
| Recipients |
drkirkby, mark.dickinson |
| Date |
2010年06月25日.11:18:34 |
| SpamBayes Score |
0.002799664 |
| Marked as misclassified |
No |
| Message-id |
<1277464717.12.0.247948397307.issue9069@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
So perhaps the cause is simply that copysign isn't being declared for David's Python builds? If that were the case, I'd expect to see some gcc warnings in the Python build output, something like:
warning: implicit declaration of function `copysign'
David, are there any such warnings?
Looking at /usr/include/math.h in my OpenSolaris VM, I see (with irrelevant bits omitted):
#if defined(__EXTENSIONS__) || defined(_XOPEN_SOURCE) || \
!defined(_STRICT_STDC) && !defined(_POSIX_C_SOURCE)
#if defined(__EXTENSIONS__) || !defined(_XOPEN_SOURCE)
extern double copysign __P((double, double));
#endif
#endif
Assuming that this is the cause, it would be interesting to know which of these defines differs between my OpenSolaris VM and David's machines.
(e.g., the 'hawk' machine, since this seems closest in spec to what I'm working with). |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年06月25日 11:18:37 | mark.dickinson | set | recipients:
+ mark.dickinson, drkirkby |
| 2010年06月25日 11:18:37 | mark.dickinson | set | messageid: <1277464717.12.0.247948397307.issue9069@psf.upfronthosting.co.za> |
| 2010年06月25日 11:18:34 | mark.dickinson | link | issue9069 messages |
| 2010年06月25日 11:18:34 | mark.dickinson | create |
|