| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0000106 | Spring engine | Linux | public | 2006-03-03 18:23 | 2006-03-03 19:04 | ||||
| Reporter | justa | ||||||||
| Assigned To | tvo | ||||||||
| Priority | normal | Severity | trivial | Reproducibility | always | ||||
| Status | resolved | Resolution | fixed | ||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0000106: SCONS cannot detect CPU-type on Xeon-type machines due to bad/wrong 'detect.py' | ||||||||
| Description | Basically, scons tries to determine cpu-type based on contents taken from /proc/cpuinfo; parsing it and determining cpu capabilitied from there. However, this failed on my Xeon-EMT machine because of the following: Line 112 of rts/build/scons/detect.py reads: elif str.find("Intel(R) Xeon(R) CPU") != -1: print " found Intel Xeon w/EM64T" archflags=['-march=nocona', '-mmmx', '-msse3'] However, /proc/cpuinfo has the following as it's model-name : Intel(R) Xeon(TM) CPU 2.80GHz Note the "TM" and not "R" that detect.py seemed to be expecting. Changing this will make 'scons configure' complete it's work. No idea yet if the beast will compile cleanly, however. | ||||||||
| Tags | No tags attached. | ||||||||
| Checked infolog.txt for Errors | |||||||||
| Attached Files |
| ||||||||
 Relationships |
|
 Relationships |
| Notes |
|
| There are no notes attached to this issue. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2006-03-03 18:23 | justa | New Issue | |
| 2006-03-03 18:23 | justa | Status | new => assigned |
| 2006-03-03 18:23 | justa | Assigned To | => tvo |
| 2006-03-03 19:04 | tvo | Status | assigned => resolved |
| 2006-03-03 19:04 | tvo | Resolution | open => fixed |
| Issue History |