|
Viewing Issue Simple Details
[ Jump to Notes ]
|
[ View Advanced ]
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Reproducibility |
Date Submitted |
Last Update |
|
0001671 |
[SOGo] SOPE |
tweak |
always |
2012-03-10 04:36 |
2012-03-23 15:26 |
|
|
Reporter |
avoegele |
View Status |
public |
|
|
Assigned To |
ludovic |
|
Priority |
normal |
Resolution |
fixed |
|
|
Status |
resolved |
|
Product Version |
git / nightly |
|
|
Summary |
0001671: Replace "uname -p" with "uname -m" in configure script |
|
Description |
It seems that the output of "uname -p" isn't standardized. On my Debian-based laptop computer "unknown" is output. On my Slackware Linux systems I get strings like "Intel(R) Core(TM)2 Duo CPU T6670 @ 2.20GHz" and "QEMU Virtual CPU version 1.0" instead of "x86_64" and "i686".
On the other hand, "uname -m" always outputs values like "x86_64" and "i686" no matter what Linux distribution is installed.
I cannot check this myself on 64-bit SPARC and PowerPC machines as I don't have such hardware but according to Google "uname -m" outputs "sparc64" and "ppc64" on these systems.
|
|
Additional Information |
|
| Tags |
No tags attached. |
|
|
Attached Files |
 configure.diff [^] (375 bytes) 2012-03-10 04:36 [Show Content] [Hide Content]--- configure.orig 2012-01-20 01:56:02.000000000 +0100
+++ configure 2012-03-10 08:22:40.000000000 +0100
@@ -331,7 +331,7 @@
# common.make
UNAME=`uname`
if [ "X${UNAME}" = "XLinux" ];then
- UNAME=`uname -p`
+ UNAME=`uname -m`
if [ ${UNAME} = x86_64 -o ${UNAME} = sparc64 -o ${UNAME} = ppc64 ];then
cfgwrite "CGS_LIBDIR_NAME:=lib64"
else
|
|
|
Relationships 
