From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Miroslav Lichvar <mlichvar@redhat.com>
Cc: guile-devel@gnu.org
Subject: Re: build failure just trying to build guile-1.8.7 natively
Date: Fri, 27 Nov 2009 16:07:04 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911271605550.8876@localhost> (raw)
In-Reply-To: <20091127205253.GC12075@localhost>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1218 bytes --]
On Fri, 27 Nov 2009, Miroslav Lichvar wrote:
> On Fri, Nov 27, 2009 at 09:29:19PM +0100, Ludovic Courtès wrote:
> > >> > This is caused by new cpp which inserts linemarkers where it didn't
> > >> > before.
> > >>
> > >> Interesting. Which version of cpp/gcc does that?
> > >
> > > cpp (GCC) 4.4.2 20091027
> >
> > I can’t reproduce the problem with 4.4.2 on x86_64-linux-gnu. Could it
> > be that your distro ships a version of gcc that differs from upstream’s?
>
> Possibly. It looks like it's a post 4.4.2 SVN snapshot and there are
> also some extra patches in the package.
i was the original reporter, and i can verify that adding the -P
option for linemarkers fixed the problem. this was on a fedora 12
x86_64 system with cpp-4.4.2.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next prev parent reply other threads:[~2009-11-27 21:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 17:11 build failure just trying to build guile-1.8.7 natively Robert P. J. Day
2009-11-19 17:24 ` Miroslav Lichvar
2009-11-19 18:01 ` Robert P. J. Day
2009-11-19 18:58 ` Robert P. J. Day
2009-11-27 17:56 ` Ludovic Courtès
2009-11-27 18:22 ` Miroslav Lichvar
2009-11-27 20:29 ` Ludovic Courtès
2009-11-27 20:52 ` Miroslav Lichvar
2009-11-27 21:07 ` Robert P. J. Day [this message]
2009-11-27 22:00 ` Ludovic Courtès
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.00.0911271605550.8876@localhost \
--to=rpjday@crashcourse.ca \
--cc=guile-devel@gnu.org \
--cc=mlichvar@redhat.com \
/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).