v1 | v2 | |
---|---|---|
33 | 33 | 下線に変えられる傾向がある。私になぜかを尋ねないで欲しい。 |
34 | 34 | |
35 | ||
36 | 35 | |
37 | 36 | 原文は LKML |
38 | 37 | http://lkml.org/lkml/2004/2/21/110 |
39 | 38 | |
40 | Date Sat, 21 Feb 2004 19:12:20 -0800 (PST) |
|
41 | From Linus Torvalds <> |
|
42 | Subject Re: Intel vs AMD x86-64 |
|
39 | Date Sat, 21 Feb 2004 19:12:20 -0800 (PST)[[BR]] | |
40 | From Linus Torvalds <>[[BR]] | |
41 | Subject Re: Intel vs AMD x86-64[[BR]] | |
43 | 42 | |
44 | 43 | No. The filesystem policy _tends_ to be that dashes and spaces are turned |
… | … | |
49 | 48 | So the real name is (and has always been, as far as I can tell) x86-64. |
50 | 49 | |
50 | x86-64 だったら gccなどで | |
51 | x86-64-gnu-linux-pc | |
52 | という表記になってワケワカになるという理由はとても合理的(実用的)だと思います。 | |
53 | ||
54 | As far as I know, the real reason for the underscore in x86_64 in Linux | |
55 | is that autoconf/configure hate dashes in arch names, because of this | |
56 | notation: | |
57 | ||
58 | x86_64-gnu-linux-pc | |
59 | ||
60 | If a dash were used, the string would be unparseable without prior | |
61 | knowledge of all arch names. | |
62 | ||
51 | 63 | |
52 | 64 | == Self-build == |