From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] guile-native: Add patch to inhibit generation of linemarkers from cpp.
Date: Thu, 19 Nov 2009 17:21:50 -0500 [thread overview]
Message-ID: <4B05C4FE.1080609@balister.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0911191336390.7307@localhost>
I've applied this. It did not break my build on F11. If this causes
build errors, revert if necessary. Hopefully, this is not needed.
Thanks,
Philip
On 11/19/2009 01:41 PM, Robert P. J. Day wrote:
>
> Add the "-P" option to inhibit generation of linemarkers in the output
> from the preprocessor.
>
> Signed-off-by: Robert P. J. Day<rpjday@crashcourse.ca>
>
> ---
>
> i've tested this and it seems to work. after this gets applied,
> i'll submit a patch to add guile 1.8.7 to the mix. did i get the
> patch format right? two edited files, one new one.
>
>
> diff --git a/recipes/guile/files/cpp-linemarkers.patch b/recipes/guile/files/cpp-linemarkers.patch
> new file mode 100644
> index 0000000..54f58eb
> --- /dev/null
> +++ b/recipes/guile/files/cpp-linemarkers.patch
> @@ -0,0 +1,8 @@
> +--- guile.orig/libguile/guile-snarf-docs.in 2009-07-03 18:19:00.000000000 -0400
> ++++ guile/libguile/guile-snarf-docs.in 2009-11-19 12:55:32.487266268 -0500
> +@@ -23,4 +23,4 @@
> + ## Let the user override the preprocessor autoconf found.
> + test -n "${CPP+set}" || CPP="@CPP@"
> +
> +-${CPP} -DSCM_MAGIC_SNARF_DOCS "$@"
> ++${CPP} -P -DSCM_MAGIC_SNARF_DOCS "$@"
> diff --git a/recipes/guile/guile-native_1.8.5.bb b/recipes/guile/guile-native_1.8.5.bb
> index 9c2eb13..5c999db 100644
> --- a/recipes/guile/guile-native_1.8.5.bb
> +++ b/recipes/guile/guile-native_1.8.5.bb
> @@ -4,6 +4,7 @@ DEPENDS = "libtool (< 2)"
>
> SRC_URI = "http://ftp.gnu.org/pub/gnu/guile/guile-${PV}.tar.gz \
> file://configure-fix.patch;patch=1 \
> + file://cpp-linemarkers.patch;patch=1 \
> "
>
> PR = "r1"
> diff --git a/recipes/guile/guile-native_1.8.6.bb b/recipes/guile/guile-native_1.8.6.bb
> index d511807..2f87c48 100644
> --- a/recipes/guile/guile-native_1.8.6.bb
> +++ b/recipes/guile/guile-native_1.8.6.bb
> @@ -1,4 +1,5 @@
> require guile-native.inc
> SRC_URI = "http://ftp.gnu.org/pub/gnu/guile/guile-${PV}.tar.gz \
> file://configure-fix.patch;patch=1 \
> + file://cpp-linemarkers.patch;patch=1 \
> "
>
> rday
> --
>
> ========================================================================
> Robert P. J. Day Waterloo, Ontario, CANADA
>
> Linux Consulting, Training and Kernel Pedantry.
>
> Web page: http://crashcourse.ca
> Twitter: http://twitter.com/rpjday
> ========================================================================
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2009-11-19 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 18:41 [PATCH] guile-native: Add patch to inhibit generation of linemarkers from cpp Robert P. J. Day
2009-11-19 22:21 ` Philip Balister [this message]
2009-11-20 1:13 ` Robert P. J. Day
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=4B05C4FE.1080609@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.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 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.