| 1 |
On 9/4/20 12:29 am, Mike Gilbert wrote: |
| 2 |
> On Wed, Apr 8, 2020 at 7:50 AM William Kenworthy <billk@×××××××××.au> wrote: |
| 3 |
>> |
| 4 |
>> On 8/4/20 7:19 pm, Michael wrote: |
| 5 |
>>> On Tuesday, 7 April 2020 06:43:44 BST William Kenworthy wrote: |
| 6 |
>>>> Hi, |
| 7 |
>>>> |
| 8 |
>>>> I have an Odroid H2 with a Celeron J4105 processor which appears to |
| 9 |
>>>> be a Gemini Lake, Goldmont Plus architecture |
| 10 |
>>>> |
| 11 |
>>>> Any idea what CHOST this should be? |
| 12 |
>>>> |
| 13 |
>>>> BillK |
| 14 |
>>> I don't have one of those, but it is an x86_64 Quad core SoC. This should do |
| 15 |
>>> it: |
| 16 |
>>> |
| 17 |
>>> CHOST="x86_64-pc-linux-gnu" |
| 18 |
>>> |
| 19 |
>>> Useful links: |
| 20 |
>>> |
| 21 |
>>> https://wiki.gentoo.org/wiki/CHOST |
| 22 |
>>> https://wiki.gentoo.org/wiki/Safe_CFLAGS |
| 23 |
>> Hi, yes that is what the reference pages give - but I am hoping there is |
| 24 |
>> something that is evidence backed as being a better choice - what you |
| 25 |
>> quote is their example, no details on whether it matches my architecture |
| 26 |
>> or not. The installation default is "i686-pc-linux-gnu" which is a |
| 27 |
>> catch-all lowest common type. |
| 28 |
> If your installation defaults to i686-pc-linux-gnu, you picked the |
| 29 |
> wrong stage3 tarball. You want amd64, not x86. |
| 30 |
> |
| 31 |
> CHOST for amd64 is always x86_64-pc-linux-gnu. You can specialize that |
| 32 |
> by adding -march=foo to CFLAGS in make.conf. |
| 33 |
> |
| 34 |
Damn ... your right!, no wonder its not performing the way I want! |
| 35 |
|
| 36 |
BillK |
Archives