| 1 |
On Mon, Dec 18, 2017 at 3:20 PM, Walter Dnes <waltdnes@××××××××.org> wrote: |
| 2 |
> On Mon, Dec 18, 2017 at 10:20:48AM -0500, Michael Orlitzky wrote |
| 3 |
>> On 12/18/2017 10:00 AM, Walter Dnes wrote: |
| 4 |
>> > |
| 5 |
>> > I tried a couple of different mirrors. No CHOST line. The example |
| 6 |
>> > file usr/share/portage/config/make.conf.example shows... |
| 7 |
>> > |
| 8 |
>> > =========================== |
| 9 |
>> > CHOST="x86_64-pc-linux-gnu" |
| 10 |
>> > =========================== |
| 11 |
>> > |
| 12 |
>> > I could insert that, but I wonder if anything else is screwed up. |
| 13 |
>> |
| 14 |
>> This silently disappeared some time ago. It's set in the profiles now; |
| 15 |
>> for example, the file "profiles/arch/amd64/make.defaults" sets |
| 16 |
>> |
| 17 |
>> CHOST="x86_64-pc-linux-gnu" |
| 18 |
> |
| 19 |
> Thanks. That's good to know. This could've used a brief news item to |
| 20 |
> avoid scaring people. I'll file a documentation bug because |
| 21 |
> usr/share/portage/config/make.conf.example still shows an explicit CHOST |
| 22 |
> setting line. While I'm at it, I'll ask them to mention "-march=native" |
| 23 |
> in CFLAGS/CXXFLAGS. |
| 24 |
|
| 25 |
CHOST is still a valid setting in make.conf, so removing it from the |
| 26 |
example is not necessary. |
| 27 |
|
| 28 |
Setting CHOST is still necessary for archs like x86, on which you have |
| 29 |
i486, i586 and i686 variants. |
Archives