From: Eli Zaretskii <eliz@gnu.org>
To: Sam Steingold <sds@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: cannot build bzr tip on mingw
Date: Tue, 03 May 2011 06:00:10 +0300 [thread overview]
Message-ID: <83pqo04hfp.fsf@gnu.org> (raw)
In-Reply-To: <BANLkTim4Q0j6FYeEY8Vv+1xXJ8VH02CwTg@mail.gmail.com>
> Date: Mon, 2 May 2011 17:13:53 -0400
> From: Sam Steingold <sds@gnu.org>
> Cc: emacs-devel@gnu.org
>
> On Mon, May 2, 2011 at 4:31 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> >> From: Sam Steingold <sds@gnu.org>
> >> Date: Mon, 02 May 2011 15:47:01 -0400
> >>
> >> $ ./configure.bat --no-debug --with-gcc --cflags -IC:/gnu/gnuwin32/include --ldflags -LC:/gnu/gnuwin32/lib --without-xpm
> >
> > Do you always configure like that, or did something change since the
> > last time you bootstrapped?
>
> this is the way I always configure.
Then something else changed on your machine, because the compiler is
now unusable:
> > What does the following command display?
> >
> > gcc -print-file-name=libmingw32.a
>
> libmingw32.a
This means it didn't find it in any of the places it knows to look.
When it finds the library, it displays its full absolute file name,
like this, for example (from my machine):
D:/usr/bin/../lib/gcc/mingw32/3.4.2/../../../libmingw32.a
You need to find out what changed on your machine lately that causes
this problem. Perhaps some environment variables or a change in
directory structure, or some Cygwin-specific change?
> > But yes, you can use GCC 4, modulo the caveats in etc/PROBLEMS.
>
> how, given that it no longer supports -mno-cygwin?
Why, by installing the native MinGW port of GCC, of course. The
Cygwin project doesn't really care about the native builds, so relying
on it for native builds is not a good idea in the long run.
next prev parent reply other threads:[~2011-05-03 3:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 19:47 cannot build bzr tip on mingw Sam Steingold
2011-05-02 20:31 ` Eli Zaretskii
2011-05-02 20:40 ` Eli Zaretskii
2011-05-02 21:13 ` Sam Steingold
2011-05-02 22:08 ` Ken Brown
2011-05-02 22:21 ` Sam Steingold
2011-05-03 2:47 ` Ken Brown
2011-05-04 21:30 ` Ken Brown
2011-05-03 0:15 ` Jason Rumney
2011-05-03 3:00 ` Eli Zaretskii [this message]
2011-05-03 11:16 ` Ken Brown
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83pqo04hfp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=sds@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).