emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#48216: closed ([CORE-UPDATES] host-inputs for wrong architecture whe


From: GNU bug Tracking System
Subject: bug#48216: closed ([CORE-UPDATES] host-inputs for wrong architecture when building for i686 on x86_64)
Date: Mon, 05 Jul 2021 10:14:03 +0000

Your message dated Mon, 05 Jul 2021 12:12:55 +0200
with message-id <87a6n1ul08.fsf@gnu.org>
and subject line Re: bug#48216: [CORE-UPDATES] host-inputs for wrong 
architecture when building for i686 on x86_64
has caused the debbugs.gnu.org bug report #48216,
regarding [CORE-UPDATES] host-inputs for wrong architecture when building for 
i686 on x86_64
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
48216: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=48216
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [CORE-UPDATES] host-inputs for wrong architecture when building for i686 on x86_64 Date: Tue, 4 May 2021 11:25:32 +0300
I'm trying to see if the rust bootstrap process works on core-updates
and I was unable to build for i686-linux on x86_64 linux. I failed to
build xz, due to some assembly optimizations. It turns out that instead
of using i686 binaries it was using x86_64 binaries and targeting i686,
while passing flags saying it was i686.

It seems there are some other things which need another look. From the
PATH variable:
(ins)efraim@3900XT ~/workspace/guix-core-updates$ file 
/gnu/store/yf4y60dyvb5qca8ram5pvxp7ba7x0z2a-xz-5.2.5/bin/xz
/gnu/store/yf4y60dyvb5qca8ram5pvxp7ba7x0z2a-xz-5.2.5/bin/xz: ELF 64-bit LSB 
executable, x86-64, version 1 (SYSV), dynamically linked, interpreter 
/gnu/store/xd4jlar0rjsvc921b32kn40vn01638hc-glibc-2.33/lib/ld-linux-x86-64.so.2,
 for GNU/Linux 2.6.32, stripped
(ins)efraim@3900XT ~/workspace/guix-core-updates$ file 
/gnu/store/1g3vhzaw78fi04q630swrz4s9yn4wsj2-grep-3.6/bin:/gnu/store/vrdmi9lnd663np8y5hcpxvgkl35v5sby-coreutils-8.32
/gnu/store/1g3vhzaw78fi04q630swrz4s9yn4wsj2-grep-3.6/bin:/gnu/store/vrdmi9lnd663np8y5hcpxvgkl35v5sby-coreutils-8.32:
 cannot open 
`/gnu/store/1g3vhzaw78fi04q630swrz4s9yn4wsj2-grep-3.6/bin:/gnu/store/vrdmi9lnd663np8y5hcpxvgkl35v5sby-coreutils-8.32'
 (No such file or directory)

The ones listed in the environmental file at the base of the build
listed x86_64 binaries.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

Attachment: 63r37flw2gv4cbna7jb69b4n8c41n6-xz-5.2.5.drv.bz2
Description: Binary data

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- Subject: Re: bug#48216: [CORE-UPDATES] host-inputs for wrong architecture when building for i686 on x86_64 Date: Mon, 05 Jul 2021 12:12:55 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Hello!

Efraim Flashner <efraim@flashner.co.il> skribis:

> I'm trying to see if the rust bootstrap process works on core-updates
> and I was unable to build for i686-linux on x86_64 linux. I failed to
> build xz, due to some assembly optimizations. It turns out that instead
> of using i686 binaries it was using x86_64 binaries and targeting i686,
> while passing flags saying it was i686.

That’s embarrassing.  I think this was fixed by
98c075c24e26798ef52ab66641faa7b0aa87726b.

Let me know if anything’s amiss!

Ludo’.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]