unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Deniz Dogan <deniz.a.m.dogan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Building Emacs with GnuTLS on Windows
Date: Fri, 29 Apr 2011 10:10:19 +0200	[thread overview]
Message-ID: <BANLkTinA28JrG1rDizEc7HNMsiZ1+3aTDA@mail.gmail.com> (raw)
In-Reply-To: <83vcxy6rn2.fsf@gnu.org>

2011/4/28 Eli Zaretskii <eliz@gnu.org>:
>> Date: Thu, 28 Apr 2011 23:22:01 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>>
>> > From: Deniz Dogan <deniz.a.m.dogan@gmail.com>
>> > Date: Thu, 28 Apr 2011 20:40:03 +0200
>> > Cc: help-gnu-emacs@gnu.org
>> >
>> > >> Line 161:
>> > >> error Unknown architecture type "$(PROCESSOR_ARCHITECTURE)"
>> > >
>> > > Weird.  What does the command below display if you type it from the
>> > > shell prompt in the same window where you invoked `make':
>> > >
>> > >   set PROCESSOR_ARCHITECTURE
>> > >
>> >
>> > Actually, the problem has gone away now after pulling in the most
>> > recent changes.
>> >
>> > Anyways, in case you want to know:
>> > PROCESSOR_ARCHITECTURE=AMD64
>>
>> How could it have gone, if AMD64 is not covered by nt/gmake.defs?  I
>> don't see any changes committed lately that could have fixed that.
>
> This MSDN page:
>
>  http://msdn.microsoft.com/en-us/library/aa384274(v=vs.85).aspx
>
> gives a clue: when a 32-process runs on 64-bit Windows, Windows
> "fixes" its environment such that PROCESSOR_ARCHITECTURE gets the
> value "x86" expected by 32-bit Windows processes.
>
> So the question now becomes: how come GNU Make, which is supposed to
> be a 32-bit executable, got a value that is not x86?  What did you do
> differently at those previous attempts to build Emacs?
>

I didn't think that PROCESSOR_ARCHITECTURE would change after
configuring/making, so the results I got last time were from a "clean"
cmd.exe.  Sorry about that.  The "real" value is x86.

However, I'm having even more problems.  This time, when I bootstrap I get this:

c:/mingw/bin/../lib/gcc/mingw32/4.5.2/../../../../mingw32/bin/ld.exe:
cannot find -lC:/gnutls/lib
c:/mingw/bin/../lib/gcc/mingw32/4.5.2/../../../../mingw32/bin/ld.exe:
cannot find -lC:/gnutls/bin
collect2: ld returned 1 exit status
make[2]: *** [oo-spd/i386/temacs.exe] Fel 1
make[2]: Leaving directory `c:/repos/emacs-trunk/src'
make[1]: *** [bootstrap-temacs] Fel 2
make[1]: Leaving directory `c:/repos/emacs-trunk/src'
make: *** [bootstrap-gmake] Fel 2


Any ideas?

-- 
Deniz Dogan



  reply	other threads:[~2011-04-29  8:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 21:55 Building Emacs with GnuTLS on Windows Deniz Dogan
2011-04-28  2:56 ` Eli Zaretskii
2011-04-28  7:09   ` Deniz Dogan
2011-04-28  7:13     ` Deniz Dogan
2011-04-28 11:23     ` Eli Zaretskii
2011-04-28 18:40       ` Deniz Dogan
2011-04-28 20:22         ` Eli Zaretskii
2011-04-28 20:35           ` Eli Zaretskii
2011-04-29  8:10             ` Deniz Dogan [this message]
2011-04-29  9:09               ` Eli Zaretskii

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=BANLkTinA28JrG1rDizEc7HNMsiZ1+3aTDA@mail.gmail.com \
    --to=deniz.a.m.dogan@gmail.com \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).