Re: [be] help with 64bit install

[Jonathan Marsden]

On 11/26/2010 07:59 PM, Oreo Warpok wrote:

> I have tried to compile Bibledit 4.1 as normal. I have done this many
> times with 32bit Ubuntu and LinuxMint. But now I am trying 64bit for the
> first time.
> 
> After ./configure and make were both successful upon 
> sudo make install
> I get this:
> 
>         i386 architecture of input file `bookdata.o' is incompatible
>         with i386:x86-64 output

Basically this says that the file bookdata.o is an i386 ("32bit") object
file, but you are compiling for x86-64 ("64bit"), so it's no use.

The obvious first question is how on earth it got there -- was that file
present in the source tarball you downloaded?  If not, if it was
actually created by the build process, something is very wrong in your
(supposedly 64bit!) build process somewhere, because you seem to have
accidentally compiled bookdata.cpp into a 32bit object file, when you
wanted a 64bit object file.

It's also strange that the install target would be dealing with a .o
file at all -- the default make target should have linked all the .o
files into executables already.  Did you start this build process in a
clean unmodified bibledit-gtk source tree?

On my system, bookdata.o is definitely 64bit; running

  ./configure && make && file src/bookdata.o

outputs

  src/bookdata.o: ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV),
not stripped

What does file src/bookdata.o display on your system?

My best guess is that you have copied some .o files from a 32bit machine
across onto your new 64bit installation somehow (and also failed to do a
make clean!)?  Or attempted a cross-compilation in some fashion?

> Is there a work around for this?

Before a workaround can be developed, someone else has to duplicate the
issue :)  On my Ubuntu 10.04 Lucid 64bit desktop machine, I can do (all
on one long line):

  wget -m -nd -nH
http://download-mirror.savannah.gnu.org/releases/bibledit/source/gtk/bibledit-gtk-4.1.tar.gz
&& mkdir temp && cd temp && tar zxf ../bibledit-gtk-4.1.tar.gz && cd
bibledit-gtk-4.1 && ./configure && make

to build bibledit-gtk 4.1 from a known-clean source tree, and then

  find . -name "*.o" |xargs file |grep -v x86-64

will display just one non-64bit .o file:

./eeepc/eeepc-install-menu.o:      ELF 32-bit LSB relocatable, Intel
80386, version 1 (SYSV), not stripped

That one is in the original tarball, and is not used by the normal build
process at all (personally, I'd rather source tarballs only ever contain
source files, but I understand there are "convenience" reasons for
keeping this particular object file in there).

If you can provide a clear set of detailed step by step instructions for
duplicating this issue, preferably starting with installing a fresh copy
of Ubuntu 10.04 Lucid amd64 desktop, then I will look further into
duplicating the issue here, and then coming up with a workaround or a
fix for it.

> Would it be possible to compile a .deb version for 4.1 soon?

On whose machine?  If your machine is unable to compile the original
sources, it is unlikely it can compile them and then correctly package
them into a .deb :)

> Would installing from a deb work better?

Probably, because installing from a .deb means someone else does the
work of ensuring things will compile and link on a 64bit machine, so you
do not have to do that work yourself :)

There is already a "quick and dirty" developer test package of
bibledit-gtk 4.1 for Ubuntu.  It was created (and announced on the
bibledit-development list, I think?) about six weeks ago, after someone
(Kim?) asked for it.

Based on very minimal testing here, it seems to run OK -- but I am not
at all a real bibledit user, so I do not know how to test it well!  I've
not yet heard any feedback from any others about how well or badly these
packages work for them.  Therefore, it is *still* only in the
developer-testing PPA.

At some point (soon?) I should probably tidy up the way it was created
(it was done a bit rapidly as a quick test, and if I remember rightly it
is not yet what I would call a nice clean professional package!), and
then republish it in the main pkgcrosswire PPA for general users.

But for now, if you need it, "64bit" packages of bibledit-gtk 4.1 for
Ubuntu Lucid and Maverick do both exist, see

  https://launchpad.net/~pkgcrosswire/+archive/developer-testing/

Please let me know how well they work for you, if you try them out.
Something like

  sudo add-apt-repository ppa:pkgcrosswire/developer-testing
  sudo apt-get update
  sudo apt-get install bibledit-gtk

should do it.

However, please note that, in general, if you are not a
SWORD/xiphos/bibltime/bibledit developer or tester, using this
developer-testing PPA is discouraged -- packages there may occasionally
be broken!

Thanks,

Jonathan