Ticket #33 (closed Defect: fixed)

Opened 1 year ago

Last modified 2 months ago

Wrong architecture detected on 64bit distro

Reported by: isak Assigned to: taj
Priority: Medium Milestone: 1.2.5
Component: main Version: 1.2.3
Severity: Normal Keywords: 64bit
Cc:

Description

This probably hits other distros aswell, but a guy running Suse 10.2 64bit reported this on IRC:

i wanted to report a bug, but the super-intuitive webpage requieres you to login and doesn't give you the ability to do it

i've tried to install a autopackage and when opening/running it a text window opens and shows the following error: 

Selection B --> OK to download and install support code now? (Y/n):
Attempting download of http://autopackage.org/downloads/latest/x86_64/autopackage.tar.bz2 ...
--03:04:42-- http://autopackage.org/downloads/latest/x86_64/autopackage.tar.bz2
HTTP Anforderung gesendet, warte auf Antwort... 404 Not Found
03:04:42 FEHLER 404: Not Found.
Download failed

Change History

06/29/07 09:58:50 changed by isak

This ticket is related to #10 (although this is more specific, and could (should) be fixed before #10)

06/29/07 23:31:14 changed by taj

If we detect a 64 bit machine, we could try and detect the 32 bit compat libs, and then install the 32 bit code. If they're not installed then just give an error saying "install compat libs".

How can we detect the compat libs? Should stuff "just work" if they're installed?

- Taj

07/01/07 15:06:15 changed by isak

From what I understand of 32bit support under e.g. amd64, you have two things that takes care of the compatibility:

  • The libc compat package which contains a 32-linker (/lib/ld-linux.so.2) aswell as the basic libs (libc, libm, libdl etc.). It is this linker that actually enables 32bit programs to start.
  • The ia32-libs package containing other common libraries in 32-bit format, like glib, X11, GL, PAM.

After that, I'm not sure if a program's all required libs need to exist in a 32bit version. That would really be a problem for many desktop apps.

12/29/07 11:59:06 changed by taj

Now that we have a warning (ticket #45), can we just make a symlink between x86_64 -> x86 on the server?

12/29/07 16:34:45 changed by isak

Taj and I discussed this on IRC already, but putting it here for future reference.

Yes, putting a symlink (or http redirect) is probably the best solution since it

a) Instantly "fixes" the problem for existing packages, and

b) Allows us to provide true x86_64 packages in the future and then remove the symlink.

(Another solution would be to modify the stub to understand that x86_64 + 32bit compat libs == x86)

05/13/08 15:23:20 changed by isak

  • status changed from new to closed.
  • resolution set to fixed.

I've added a symlink so x86_64 packages will download the 32bit support code

05/13/08 15:23:46 changed by isak

  • milestone set to 1.2.5.