Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: ding@gnus.org
Subject: Re: emacs23 broken on master (gnus-compat problems)
Date: Tue, 07 Feb 2012 22:38:57 +0100	[thread overview]
Message-ID: <87ipjis4r2.fsf@gnus.org> (raw)
In-Reply-To: <m2ipjijrg8.fsf@igel.home> (Andreas Schwab's message of "Tue, 07 Feb 2012 21:53:27 +0100")

Andreas Schwab <schwab@linux-m68k.org> writes:

>     * configure.in: Invoke $CPP with -P when creating Makefile and
>     src/Makefile.  Without this, gcc 4.4.2 converts each
>     backslash-newline pair in the input to a bare newline, yielding
>     invalid Make files.

Thanks.  The patch didn't apply, but I just added the -P and fixed up
some crt1 issues in the Makefiles, and now it compiles.

-- 
(domestic pets only, the antidote for overdose, milk.)
  http://lars.ingebrigtsen.no  *  Sent from my Rome



  reply	other threads:[~2012-02-07 21:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-04  9:51 Steinar Bang
2012-02-06 23:44 ` Lars Ingebrigtsen
2012-02-06 23:48   ` Lars Ingebrigtsen
2012-02-07  6:06     ` Steinar Bang
2012-02-07 10:14       ` Steinar Bang
2012-02-07 20:29       ` Lars Ingebrigtsen
2012-02-07 20:52         ` Steinar Bang
2012-02-07 20:57           ` Steinar Bang
2012-02-07 21:03             ` Steinar Bang
2012-02-07 21:20               ` Steinar Bang
2012-02-07 21:39                 ` Andreas Schwab
2012-02-07 21:49                   ` Lars Ingebrigtsen
2012-02-07 21:39                 ` Lars Ingebrigtsen
2012-02-07 21:58                   ` Steinar Bang
2012-02-07 20:53         ` Andreas Schwab
2012-02-07 21:38           ` Lars Ingebrigtsen [this message]
2012-02-08  0:34       ` Carson Chittom
2012-02-07  6:01   ` Steinar Bang

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=87ipjis4r2.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@gnus.org \
    --cc=schwab@linux-m68k.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 NNTP newsgroup(s).