| Anonymous | Login | Signup for a new account | 10-31-2025 13:57 PDT |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0001311 | [Resin] | minor | always | 08-23-06 07:58 | 08-31-06 09:26 | ||||
| Reporter | bdoperations | View Status | public | ||||||
| Assigned To | ferg | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Product Version | 3.0.21 | ||||||
| Summary | 0001311: Configure script does not recognize IBM jdk 1.5 64bit | ||||||||
| Description |
The way the configure script verifies if you are running java in 64-bit mode is by using grep and searching for '64-bit'. This only works with Sun's JDK and not with IBM. The pertinent version line for SUN looks like this: Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_06-b05, mixed mode) The pertinent version line for IBM looks like this: IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux amd64-64 j9vmxa6423-20060504 (JIT enabled) The grep command in the configure script should look like this to take into account both versions of Java: grep -E "(64-Bit|amd64-64)" $tmpname 1> /dev/null |
||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
|
|
|||||||||
 Relationships |
|
| There are no notes attached to this issue. |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 08-23-06 07:58 | bdoperations | New Issue | |
| 08-31-06 09:26 | ferg | Assigned To | => ferg |
| 08-31-06 09:26 | ferg | Status | new => closed |
| 08-31-06 09:26 | ferg | Resolution | open => fixed |
| 08-31-06 09:26 | ferg | Fixed in Version | => 3.0.22 |
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
27 total queries executed. 25 unique queries executed. |  |
