all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andy Moreton <andrewjmoreton@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Failed to compile from last bzr repo
Date: Wed, 06 Apr 2011 13:57:58 +0100	[thread overview]
Message-ID: <vz1ipur35bd.fsf@gmail.com> (raw)
In-Reply-To: BANLkTikN3-9LW3+iZfxubEY0YwsZk4JUDg@mail.gmail.com

On Wed 06 Apr 2011, Juanma Barranquero wrote:

> On Wed, Apr 6, 2011 at 05:01, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> I think the above is much easier than any of the alternatives.
>
> Sure, and I agree with adding that change.
>
> But this method does not work if the user wants to --cflag
> -DSITELOAD_PURESIZE_EXTRA=100000
>
>> In
>> particular, setting an environment variable sounds both ugly and
>> dangerous to me (the risk of leaving it set is high).
>
> I don't like it either, but it's easier than trying to workaround the
> =-is-a-separator issue.
>
>     Juanma

Due to some changes made in the last day or so, the Win32 build no
longer bootstraps. There are two issues that need fixing up:

a) ATTRIBUTE_FORMAT() and ATTRIBUTE_FORMAT_PRINTF() are undefined.
b) careadlinkatcwd() and careadlinkat are undefined in src/sysdep.c

The missing macros in (a) can be worked around by adding a force-include
header file:

  cmd.exe /C "configure.bat ${args} --with-gcc --no-cygwin \
--cflags -I$(cygpath -wm ${srcdir}/nt) \
--cflags -include --cflags user_defines.h \
"

This forces inclusion of "nt/user_defines.h" which can then contain any
user defined macro definitions or workarounds. Incorporating something
like this into configure.bat would allow user defined macros while
avoiding the problems with quoting '='.

For MSVC based builds, I expect "--cflags /FI --cflags user_defines.h"
to work in a similar fashion.

    AndyM





  reply	other threads:[~2011-04-06 12:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04  9:46 Failed to compile from last bzr repo Bastien
2011-04-04 11:53 ` Eli Zaretskii
2011-04-04 12:22   ` Deniz Dogan
2011-04-04 12:38     ` Sean Sieger
2011-04-04 17:37       ` Eli Zaretskii
2011-04-04 21:19         ` Juanma Barranquero
2011-04-04 21:51           ` Stefan Monnier
2011-04-04 22:00             ` Juanma Barranquero
2011-04-05 13:14               ` Stefan Monnier
2011-04-05 15:39                 ` Sean Sieger
2011-04-05 16:36                   ` Juanma Barranquero
2011-04-05 16:52                     ` Eli Zaretskii
2011-04-05 22:45                       ` Juanma Barranquero
2011-04-06  3:01                         ` Eli Zaretskii
2011-04-06  3:22                           ` Juanma Barranquero
2011-04-06 12:57                             ` Andy Moreton [this message]
2011-04-06 13:32                               ` Eli Zaretskii
2011-04-06 14:18                                 ` Juanma Barranquero
2011-04-06 15:47                                   ` Eli Zaretskii
2011-04-06 16:08                                     ` Eli Zaretskii
2011-04-06 16:18                                     ` Juanma Barranquero
2011-04-05 15:41                 ` Sean Sieger
2011-04-05 20:57                   ` Stefan Monnier
2011-04-05  0:13             ` Sean Sieger
2011-04-05  2:59           ` Eli Zaretskii
2011-04-04 16:39     ` Stefan Monnier
2011-04-04 17:35     ` Eli Zaretskii
2011-04-04 16:26   ` Bastien

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=vz1ipur35bd.fsf@gmail.com \
    --to=andrewjmoreton@gmail.com \
    --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.