public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthias Klose <doko@ubuntu.com>
To: GCJ-patches <java-patches@gcc.gnu.org>
Cc: classpath-patches@gnu.org
Subject: [patch] search for a <triplet>-pkg-config
Date: Wed, 19 Jun 2013 19:20:00 -0000	[thread overview]
Message-ID: <51C2045A.2070303@ubuntu.com> (raw)

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

This allows libjava to cross build in an environment where <triplet>-pkg-config
is available for the target architecture.  This change is already available in
pkg-config 0.26, so an alternative would be to import this file from a recent
pkg-config release.

Ok for the trunk, and 4.8?

  Matthias

[-- Attachment #2: libjava.diff --]
[-- Type: text/plain, Size: 928 bytes --]

2013-06-19  Matthias Klose  <doko@ubuntu.com>

	* pkg.m4 (PKG_CHECK_MODULES): Use AC_PATH_TOOL to check for pkg-config.
	* classpath/m4/pkg.m4 (PKG_CHECK_MODULES): Likewise.
	* configure: Regenerate.

Index: pkg.m4
===================================================================
--- pkg.m4	(revision 200211)
+++ pkg.m4	(working copy)
@@ -6,7 +6,7 @@
   succeeded=no
 
   if test -z "$PKG_CONFIG"; then
-    AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
+    AC_PATH_TOOL(PKG_CONFIG, pkg-config, no)
   fi
 
   if test "$PKG_CONFIG" = "no" ; then
Index: classpath/m4/pkg.m4
===================================================================
--- classpath/m4/pkg.m4	(revision 200211)
+++ classpath/m4/pkg.m4	(working copy)
@@ -6,7 +6,7 @@
   succeeded=no
 
   if test -z "$PKG_CONFIG"; then
-    AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
+    AC_PATH_TOOL(PKG_CONFIG, pkg-config, no)
   fi
 
   if test "$PKG_CONFIG" = "no" ; then

             reply	other threads:[~2013-06-19 19:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19 19:20 Matthias Klose [this message]
2013-06-20 13:01 ` Andrew Haley

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=51C2045A.2070303@ubuntu.com \
    --to=doko@ubuntu.com \
    --cc=classpath-patches@gnu.org \
    --cc=java-patches@gcc.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.
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).