bug-binutils
[Top][All Lists]
Advanced

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

building ZDoom with winelib - ld crash fixed but new problem arised


From: Benjamin Berkels
Subject: building ZDoom with winelib - ld crash fixed but new problem arised
Date: Mon, 07 May 2007 21:27:56 +0200
User-agent: Thunderbird 2.0.0.0 (Windows/20070326)

Hi all,

Last week I reported a crash of ld when trying to build the Windows version of ZDoom 2.1.7 under Linux with Winelib.

Nick Clifton managed to reproduce and fix the crash. Many thanks to him again for this! He reported the following about the cause of the crash:

> Anyway the problem itself appears to be that your object files are
> using 8-byte relocations, but the linker is expecting them to be using
> 12-byte relocations.  I am not sure whether this is a linker bug or a
> compiler bug, but it seems possible to remove the guesswork from the
> linker and make it determine exactly which size of relocs have been
> used.

With the patch he supplied to me (should be included in the latest binutils snapshot) I can compile and link ZDoom flawlessly, but when I try to run the executable, it stops directly with the following error message:

Inconsistency detected by ld.so: ../sysdeps/i386/dl-machine.h: 554: elf_machine_rel_relative: Assertion `((reloc->r_info) & 0xff) == 8' failed!

Nick told me the following about this error:

> This is almost certainly related to the same problem that I fixed for
> the linker.  It looks like one or more of the object files that you
> are linking in (or the object files extract from one or more of the
> libraries) is lying about its type, making the user think that it has
> relocations of a different size.

> It may well turn out to be a linker problem however.  It may be that
> the linker should not be creating the executable at all (because of
> the dodgy object files mentioned above), so be prepared to come back
> to us.

At first I thought this could be an Ubuntu specific problem, so I tried openSUSE 10.2. The problem persists there, so it's not Ubuntu specific.
Any suggestions what can be done about this?

Thanks,

Benjamin




reply via email to

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