Building on Windows

Building on Windows

[Paul Moore]

I'm having trouble building CVS Emacs on Windows. I'm using mingw, and
building via configure.bat then gmake, but the build is failing on some items
(movemail, for example) in the lib-src directory. I'm pretty sure that I've
built from CVS in the past, but it's a long time ago and I've forgotten what
(if anything) I did :-(

Here's the error messages from a clean build in lib-src from CVS yesterday:

gcc -o oo-spd/i386/movemail.exe  -gstabs+ -g3   oo-spd/i386/movemail.o
oo-spd/i
86/pop.o oo-spd/i386/ntlib.o oo-spd/i386/getopt.o oo-spd/i386/getopt1.o
-lwsock
2   -ladvapi32
Info: resolving __sys_nerr by linking to __imp___sys_nerr (auto-import)
Info: resolving __sys_errlist by linking to __imp___sys_errlist (auto-import)
oo-spd/i386/movemail.o: In function `main':
C:/Data/emacs/lib-src/movemail.c:345: undefined reference to `link'
fu000001.o:: undefined reference to `libmsvcrt_a_iname'
fu000003.o:: undefined reference to `libmsvcrt_a_iname'
nmth000000.o:: undefined reference to `_nm___sys_nerr'
nmth000002.o:: undefined reference to `_nm___sys_errlist'
collect2: ld returned 1 exit status
mingw32-make: *** [oo-spd/i386/movemail.exe] Error 1

Are there any known problems building on Windows? If not, should I expect
stuff in lib-src to fail, and is there a way of skipping it cleanly? Or more
likely, am I doing something dumb?

Thanks,
Paul.

Re: Building on Windows

[Eli Zaretskii]

> From: Paul Moore <pf_moore@yahoo.co.uk>
> Date: Wed, 28 Jun 2006 18:46:31 +0100
> 
> gcc -o oo-spd/i386/movemail.exe  -gstabs+ -g3   oo-spd/i386/movemail.o oo-spd/i86/pop.o oo-spd/i386/ntlib.o oo-spd/i386/getopt.o oo-spd/i386/getopt1.o -lwsock2   -ladvapi32
> Info: resolving __sys_nerr by linking to __imp___sys_nerr (auto-import)
> Info: resolving __sys_errlist by linking to __imp___sys_errlist (auto-import)
> oo-spd/i386/movemail.o: In function `main':
> C:/Data/emacs/lib-src/movemail.c:345: undefined reference to `link'
> fu000001.o:: undefined reference to `libmsvcrt_a_iname'
> fu000003.o:: undefined reference to `libmsvcrt_a_iname'
> nmth000000.o:: undefined reference to `_nm___sys_nerr'
> nmth000002.o:: undefined reference to `_nm___sys_errlist'
> collect2: ld returned 1 exit status
> mingw32-make: *** [oo-spd/i386/movemail.exe] Error 1

I don't have these problems on Windows.  I also build with MinGW.

The error message about `link' in line 345 is strange, since that line
is not supposed to be compiled on Windows.  Please see how come the
build tried to compile it on your system.

How about showing the full transcript of the build, not just the last
command?

Also, what are your versions of GCC and MinGW runtime, and what shell,
if any, do you have installed?

> Are there any known problems building on Windows?

No, not with MinGW.

> If not, should I expect stuff in lib-src to fail

No, it should all build cleanly.

> and is there a way of skipping it cleanly?

I wouldn't recommend skipping it, since these problems might hint on
some serious problem with your development environment.  The Emacs
binary could be faulty even if you succeed in building it.

Re: Building on Windows

[Jason Rumney]

Paul Moore wrote:
> Info: resolving __sys_nerr by linking to __imp___sys_nerr (auto-import)
> Info: resolving __sys_errlist by linking to __imp___sys_errlist (auto-import)
> oo-spd/i386/movemail.o: In function `main':
> C:/Data/emacs/lib-src/movemail.c:345: undefined reference to `link'
> fu000001.o:: undefined reference to `libmsvcrt_a_iname'
> fu000003.o:: undefined reference to `libmsvcrt_a_iname'
> nmth000000.o:: undefined reference to `_nm___sys_nerr'
> nmth000002.o:: undefined reference to `_nm___sys_errlist'
>   
It looks like your system libraries are incomplete.

Re: Building on Windows

[Paul Moore]

On Thu, 29 Jun 2006 01:02:14 +0300, Eli Zaretskii <eliz@gnu.org> wrote:

>I don't have these problems on Windows.  I also build with MinGW.
>
>The error message about `link' in line 345 is strange, since that line
>is not supposed to be compiled on Windows.  Please see how come the
>build tried to compile it on your system.
>
>How about showing the full transcript of the build, not just the last
>command?
>
>Also, what are your versions of GCC and MinGW runtime, and what shell,
>if any, do you have installed?

OK.

I'm using mingw runtime 3.10, and gcc 3.4.5 (mingw special). I'm on Windows XP
Pro SP2, using the CMD.EXE shell as supplied. Any tools I use, including the
graphics libraries, come from the GnuWin32 site, gnuwin32.sf.net. I'm
basically following the instructions at
http://ourcomments.org/Emacs/w32-build-emacs.html.

Aaaargh!!!!! I have just gone through the whole build process again, to
confirm the issue, and I've found the problem. The GnuWin32 package gsl
includes a header file include/config.h in the distribution. This interferes
with the local config.h used by the emacs build. Renaming this file makes the
problem go away.

Sorry for the noise. I'll report this to the gnuwin32 project.

Paul.