| Ticket UUID: | 764634 | ||
| Title: | 64bit support for Tru64Unix 5.1A | ||
| Type: | Bug | Created on: | 2003-07-02 14:51:59 |
| Submitter: | mmokrejs | Assigned to: | stwo |
| Subsystem: | 52. Portability Support | Severity: | |
| Priority: | 5 Medium | Last modified: | 2003-12-03 21:17:36 |
| Status: | Open | Closed by: | mdejong |
| Resolution: | Remind | Closed on: | 2003-09-12 06:27:41 |
| Version: | obsolete: 8.5a0 | ||
| Description: | ||||
I there a chance toinclude 64bit support for this platfom? checking for ranlib... ranlib checking if 64bit support is requested... yes checking if 64bit Sparc VIS support is requested... no checking system version (for dynamic loading)... OSF1-V5.1 checking for dlopen in -ldl... no checking for ar... ar configure: WARNING: "64bit support being disabled -- don\'t know magic for this platform" checking for build with symbols... no checking sys/ioctl.h usability... yes serow# uname -a OSF1 serow.gsf.de V5.1 1885 alpha alpha unknown Tru64 serow# I've checked current cvs. | ||||
| User Comments: | ||||
dkf added on 2003-07-02 22:11:18:
Logged In: YES user_id=79902 I thought that platform was more of the variety "always 64-bit whatever you do", unlike most others (where 64-bit-ness is just a compile-time option.) mmokrejs added on 2003-07-02 23:16:35:
Logged In: YES user_id=696559 Actually, I should say I used: ./configure --prefix=/software/@sys/usr --enable-threads --enable-64bit by dafault the --enable-64bit isn't turned on, so I've never seen the warning before. mdejong added on 2003-07-02 23:24:27:
Logged In: YES user_id=90858 I was under the impression that --enable-64bit was only used for some Solaris systems and perhaps IRIX where 64 bit vs 32 bit ABI were an option. At any rate, someone with access to such a platform would need to create a patch and test it out. mmokrejs added on 2003-07-02 23:30:38:
Logged In: YES user_id=696559 http://testdrive.hp.com and make yourself an account on Tru64Unix, if you have time. ;) furukawa added on 2003-08-08 12:02:50:
Logged In: YES user_id=49637 As you may have already noticed, the 64bit support is enabled by default on alpha/tru64 at least since tcl/tk-8.0. You don't need to specify --enable-64bit on this platform. for example, % expr 0x4000000000000000 4611686018427387904 % expr 1<<62 4611686018427387904 % format %x [expr 1<<62] 4000000000000000 % package require Thread 2.5 % format %x [thread::id] 3ffc01b6000 On this platform, a thread id is 64bit integer (pointer). So without 64bit support, thread cannot be used. :-) k. furukawa. mdejong added on 2003-09-12 13:27:41:
Logged In: YES user_id=90858 I am going to close this bug report since it seems the user is passing --enable-64bit when it is not needed. If there continues to be a problem with the configure script please let us know by reopening this bug report. dkf added on 2003-09-12 16:52:39:
Logged In: YES user_id=79902 Perhaps on those platforms where 64-bit is always on we should silently ignore the option? (Actually, we would want to have the option be enabled by default on those platforms, but that's probably much harder to do. And I don't know if any of the platforms in that situation could handle --disable-64bit in a meaningful way!) nobody added on 2003-09-15 23:09:55:
Logged In: NO Hi, yes please fix configure not to complain on this "option" when 64-bit platform. dkf added on 2003-09-16 02:43:11:
Logged In: YES user_id=79902 I think that's a fair request, Mo. Either make configure not complain or make it complain that the feature is enabled by default on the target platform. OTOH, moaning that it can't be done on a patently 64-bit system is a bit obtuse... mmokrejs added on 2003-12-03 21:17:36:
Logged In: YES user_id=696559 Still getting same WARNING: message with tcl8.4.5 on Tru64Unix 5.1A. | ||||
