unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: Emacs master build failing on RHEL 6.8
Date: Wed, 8 May 2019 07:42:24 -0400	[thread overview]
Message-ID: <CAFyQvY0mkvD_6T+Ww1d7cL494c7+HHBG5_NbVBfM37+yH8YL9Q@mail.gmail.com> (raw)
In-Reply-To: <83mujxijjn.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 730 bytes --]

On Wed, May 8, 2019 at 1:48 AM Eli Zaretskii <eliz@gnu.org> wrote:

> The way it looks after preprocessing by cpp.  The procedure to produce
> that is as follows:
>
>   . Go to src and type "make image.o -W image.c V=1
>

You might have expected, but when I ran that command, I got the same error:
http://ix.io/1Iog



>   . Copy-paste the GCC command that the above displays, but replace -c
>     with -E and "-o image.o" with "-o image.ii",


I did that, but there was no "-o image.o", so I just redirected the output
to image.ii.


> then press Enter
>   . Posit image.ii here.
>

Here it is:
https://gist.githubusercontent.com/kaushalmodi/ff2b0377a7e7d508247d874295a81c3b/raw/3a93ce939e17d34945ecc1058d7e7ce121fe2c20/image.ii

[-- Attachment #2: Type: text/html, Size: 1674 bytes --]

  parent reply	other threads:[~2019-05-08 11:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07 12:00 Emacs master build failing on RHEL 6.8 Kaushal Modi
2019-05-07 14:34 ` Eli Zaretskii
2019-05-07 14:41   ` Kaushal Modi
2019-05-07 15:13     ` Eli Zaretskii
2019-05-07 15:30       ` Stefan Monnier
2019-05-07 15:52         ` Eli Zaretskii
2019-05-07 16:01           ` Kaushal Modi
2019-05-07 18:22             ` Eli Zaretskii
2019-05-07 19:46               ` Kaushal Modi
2019-05-08  5:47                 ` Eli Zaretskii
2019-05-08  8:03                   ` Andreas Schwab
2019-05-08 11:42                   ` Kaushal Modi [this message]
2019-05-08 12:27                     ` Eli Zaretskii
2019-05-08 12:49                       ` Kaushal Modi
2019-05-08 13:05                         ` Eli Zaretskii
2019-05-08 15:07                           ` Kaushal Modi
2019-05-08 15:41                             ` Paul Eggert
2019-05-08 15:50                               ` Kaushal Modi
2020-02-14 19:49                                 ` WilliamKF
2020-02-14 20:44                                   ` Paul Eggert
2019-05-07 18:49         ` Mattias Engdegård
2019-05-08 15:57           ` Paul Eggert
2019-05-08 17:16             ` CPP indentation bikeshed (was: Emacs master build failing on RHEL 6.8) Stefan Monnier
2019-05-09  4:25               ` Paul Eggert
2019-05-07 17:37 ` Emacs master build failing on RHEL 6.8 martin rudalics
2019-05-07 18:20   ` 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=CAFyQvY0mkvD_6T+Ww1d7cL494c7+HHBG5_NbVBfM37+yH8YL9Q@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).