[aur-general] x86_64-unknown-linux-gnu vs x86_64-pc-linux-gnu
Hi, usually I build claws-mail-git from AUR by adding --build=$(uname -m)-arch-linux-gnu to ./configure. Today I forget to add it, so I expected a default of x86_64-unknown-linux-gnu, since /etc/makepkg.conf is configured to default to it. Sometimes I build without an AUR helper, but today I used yaourt. To my surprise "x86_64-pc-linux-gnu" is used. [rocketmouse@archlinux ~]$ grep CHOST /etc/makepkg.conf* /etc/makepkg.conf:CHOST="x86_64-unknown-linux-gnu" /etc/makepkg.conf-20130715_000209.bak:CHOST="x86_64-unknown-linux-gnu" /etc/makepkg.conf.pacnew:CHOST="x86_64-pc-linux-gnu" [rocketmouse@archlinux ~]$ grep linux /etc/yaourtrc #AURURL="https://aur.archlinux.org" Why isn't "x86_64-unknown-linux-gnu" used? Seemingly I'm missing another config. Regards, Ralf
On Tue, 5 Dec 2017 09:21:12 +0100, Ralf Mardorf wrote:
Hi,
usually I build claws-mail-git from AUR by adding --build=$(uname -m)-arch-linux-gnu to ./configure.
Today I forget to add it, so I expected a default of x86_64-unknown-linux-gnu, since /etc/makepkg.conf is configured to default to it.
Sometimes I build without an AUR helper, but today I used yaourt.
To my surprise "x86_64-pc-linux-gnu" is used.
[rocketmouse@archlinux ~]$ grep CHOST /etc/makepkg.conf* /etc/makepkg.conf:CHOST="x86_64-unknown-linux-gnu" /etc/makepkg.conf-20130715_000209.bak:CHOST="x86_64-unknown-linux-gnu" /etc/makepkg.conf.pacnew:CHOST="x86_64-pc-linux-gnu" [rocketmouse@archlinux ~]$ grep linux /etc/yaourtrc #AURURL="https://aur.archlinux.org"
Why isn't "x86_64-unknown-linux-gnu" used? Seemingly I'm missing another config.
PS: While I noticed that it's time to edit my /etc/makepkg.conf after diff /etc/makepkg.conf /etc/makepkg.conf.pacnew I still don't see anything related.
On 05-12-17 09:27, Ralf Mardorf wrote:
[rocketmouse@archlinux ~]$ grep CHOST /etc/makepkg.conf* /etc/makepkg.conf:CHOST="x86_64-unknown-linux-gnu" /etc/makepkg.conf-20130715_000209.bak:CHOST="x86_64-unknown-linux-gnu" /etc/makepkg.conf.pacnew:CHOST="x86_64-pc-linux-gnu" [rocketmouse@archlinux ~]$
I still don't see anything related.
/etc/makepkg.conf.pacnew:CHOST="x86_64-pc-linux-gnu" We switched to x86_64-pc-linux-gnu when gcc 6 stopped accepting unknown. check arch-dev-public mailinglist archives of may 2016
On Tue, 5 Dec 2017 13:06:03 +0100, LoneVVolf wrote:
On 05-12-17 09:27, Ralf Mardorf wrote:
[rocketmouse@archlinux ~]$ grep CHOST /etc/makepkg.conf* /etc/makepkg.conf:CHOST="x86_64-unknown-linux-gnu" /etc/makepkg.conf-20130715_000209.bak:CHOST="x86_64-unknown-linux-gnu" /etc/makepkg.conf.pacnew:CHOST="x86_64-pc-linux-gnu" [rocketmouse@archlinux ~]$
I still don't see anything related.
/etc/makepkg.conf.pacnew:CHOST="x86_64-pc-linux-gnu"
We switched to x86_64-pc-linux-gnu when gcc 6 stopped accepting unknown. check arch-dev-public mailinglist archives of may 2016
-- $ pacman -Q linux{,-rt{,-cornflower,-pussytoes}}|awk '{print $2}' 4.14.3-1 4.13.13_rt5-1 4.11.12_rt16-1 4.14_rt1-1
On Tue, 5 Dec 2017 13:06:03 +0100, LoneVVolf wrote:
gcc 6 stopped accepting unknown
So that's the culprit. Thank you. Regards, Ralf PS: My apologies, the previous unedited mail was sent by accident.
participants (2)
-
LoneVVolf
-
Ralf Mardorf