Re: building emacs-dynamic-modules on Windows Msys64 mingw32

[Eli Zaretskii]

> From: Stephen Leake <address@hidden>
> Date: Sat, 25 Oct 2014 07:25:36 -0500
> 
> address@hidden objdump -f temacs.exe
> 
> temacs.exe:     file format pei-i386
> architecture: i386, flags 0x0000013a:
> EXEC_P, HAS_DEBUG, HAS_SYMS, HAS_LOCALS, D_PAGED
> start address 0x001372f0

The start address looks wrong (too low).

Can you show the log of the end of the build process, starting with
the link command?

I actually find this all very strange: the git repo claims to have
started in July 2014, but doesn't say which Emacs branch it was forked
off.  And I don't think we had any problems like this in July on any
of the 2 active branches.

So maybe the person who did that should chime in and explain what he
did, instead of us trying to second-guess him.

Alternatively, make a diff since the first to the last commit in this
repo, and then apply it to the current trunk.

> address@hidden objdump -fh temacs.exe
> 
> temacs.exe:     file format pei-i386
> architecture: i386, flags 0x0000013a:
> EXEC_P, HAS_DEBUG, HAS_SYMS, HAS_LOCALS, D_PAGED
> start address 0x001372f0
> 
> Sections:
> Idx Name          Size      VMA       LMA       File off  Algn
>   0 .text         001b5c09  00000fff  00000fff  000005ff  2**4
>                   CONTENTS, ALLOC, LOAD, READONLY, CODE, DATA
>   1 .data         001cdf78  001b7000  001b7000  001b6400  2**6
>                   CONTENTS, ALLOC, LOAD, DATA
>   2 .rdata        0001db10  00385000  00385000  00384400  2**6
>                   CONTENTS, ALLOC, LOAD, READONLY, DATA
>   3 .eh_frame     00033810  003a3000  003a3000  003a2000  2**2
>                   CONTENTS, ALLOC, LOAD, READONLY, DATA
>   4 .bss          00b5c480  003d7000  003d7000  00000000  2**6
>                   ALLOC
>   5 .idata        00003a8c  00f34000  00f34000  003d5a00  2**2
>                   CONTENTS, ALLOC, LOAD, DATA
>   6 .CRT          00000034  00f38000  00f38000  003d9600  2**2
>                   CONTENTS, ALLOC, LOAD, DATA
>   7 .tls          00000020  00f39000  00f39000  003d9800  2**2
>                   CONTENTS, ALLOC, LOAD, DATA
>   8 .rsrc         0000d7f4  00f3a000  00f3a000  003d9a00  2**2
>                   CONTENTS, ALLOC, LOAD, DATA
>   9 .debug_aranges 00001388  00f48000  00f48000  003e7200  2**3
>                   CONTENTS, READONLY, DEBUGGING
>  10 .debug_info   00631255  00f4a000  00f4a000  003e8600  2**0
>                   CONTENTS, READONLY, DEBUGGING
>  11 .debug_abbrev 0002590c  0157c000  0157c000  00a19a00  2**0
>                   CONTENTS, READONLY, DEBUGGING
>  12 .debug_line   000ca14e  015a2000  015a2000  00a3f400  2**0
>                   CONTENTS, READONLY, DEBUGGING
>  13 .debug_str    00011e3c  0166d000  0166d000  00b09600  2**0
>                   CONTENTS, READONLY, DEBUGGING
>  14 .debug_loc    002bd822  0167f000  0167f000  00b1b600  2**0
>                   CONTENTS, READONLY, DEBUGGING
>  15 .debug_macro  02e3ceae  0193d000  0193d000  00dd9000  2**0
>                   CONTENTS, READONLY, DEBUGGING
>  16 .debug_ranges 0005ab98  0477a000  0477a000  03c16000  2**0
>                   CONTENTS, READONLY, DEBUGGING
> 
> 
> That's very close to the temacs.exe I built from the 24.3.94 tarball; it
> has an additional section:
> 
>  17 EMHEAP        02a00000  04eaa000  04eaa000  00000000  2**2
>                   ALLOC
> 
> 
> Is there some other binutils tool that might provide more detailed info
> on what's wrong with this file?

How about 'file' (not from Binutils)?

Also, what does "od -c -N2" says about it?