plash
[Top][All Lists]
Advanced

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

Re: [Plash] wrong ELF class: ELFCLASS32


From: Mark Seaborn
Subject: Re: [Plash] wrong ELF class: ELFCLASS32
Date: Sun, 13 Jul 2008 13:20:08 +0100 (BST)

Thomas Leonard <address@hidden> wrote:

> 2008/7/11 Mark Seaborn <address@hidden>:
> > Are you running Stellarium on a Debian-based system, and if so where
> > does the non-native libqt come from?
> 
> I'm using Ubuntu. Stellarium 0.6.2 (the latest Autopackage version,
> accessed through its Zero Install feed) doesn't seem to use Qt:

OK.  I had looked it up briefly and it looked like it used Qt.  Anyhow...

> $ 0launch --wrapper=ldd http://0install.net/2006/autopackage/Stellarium.xml
>         linux-gate.so.1 =>  (0xffffe000)
>         libGLU.so.1 => /usr/lib32/libGLU.so.1 (0xf7ec7000)
>         libGL.so.1 => /usr/lib32/libGL.so.1 (0xf7e22000)
>         libSDL-1.2.so.0 => /usr/lib32/libSDL-1.2.so.0 (0xf7d93000)
...

I looked these up on packages.ubuntu.com.  All these libraries are
provided by a monster ia32-libs package, which has a 450Mb source
package.  I didn't download the source package, but I imagine it
contains tarballs for all the libraries.  This is even worse than the
glibc multiarch packages: not only are the binary packages duplicated,
the source is duplicated too.  And oddly, it is named "ia32" instead
of "i386".

I am reluctant to create special multiarch packages for Plash.  Debian
packaging causes me enough pain already without adding special cases.
The usefulness of this seems limited because:

- It's a Debian-specific problem.  Fedora does multiarch differently
AFAIK.

- The problem doesn't apply if you use plash-pkg instead of pola-run.
pola-run will need to use files from your host Debian environment,
whereas plash-pkg will unpack native packages for the chosen
architecture into a clean chroot-like environment.  plash-pkg would be
equivalent to debootstrapping an i386 chroot on an amd64 host.

- You can usually use a build for your native architecture anyway.

I don't like the idea of having to build i386 packages twice, on i386
and on amd64.  My continuous integration system has enough builds to
do already -- about 10 at the moment:
(feisty,gutsy,hardy,intrepid,lenny) * (i386,amd64)

Mark




reply via email to

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