From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Building on Windows
Date: Thu, 29 Jun 2006 01:02:14 +0300 [thread overview]
Message-ID: <u8xnhey6x.fsf@gnu.org> (raw)
In-Reply-To: <4rf5a2pbkc5tn8c73mjamhr94bejumbfnu@4ax.com> (message from Paul Moore on Wed, 28 Jun 2006 18:46:31 +0100)
> 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.
next prev parent reply other threads:[~2006-06-28 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 17:46 Building on Windows Paul Moore
2006-06-28 22:02 ` Eli Zaretskii [this message]
2006-06-28 22:58 ` Paul Moore
2006-06-28 22:07 ` Jason Rumney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u8xnhey6x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.