Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/pcre
Date: Sat, 16 Aug 2008 05:32:54 -0700 (PDT)	[thread overview]
Message-ID: <20080816123254.E7D393C827@busybox.net> (raw)

Author: jacmet
Date: 2008-08-16 05:32:54 -0700 (Sat, 16 Aug 2008)
New Revision: 23091

Log:
pcre: fix compilation when C++ support is disabled

pcre will use host g++ is no cross g++ is available, so explicitly disable
c++ support in pcre if it isn't enabled in buildroot instead.

Modified:
   trunk/buildroot/package/pcre/pcre.mk


Changeset:
Modified: trunk/buildroot/package/pcre/pcre.mk
===================================================================
--- trunk/buildroot/package/pcre/pcre.mk	2008-08-16 11:59:59 UTC (rev 23090)
+++ trunk/buildroot/package/pcre/pcre.mk	2008-08-16 12:32:54 UTC (rev 23091)
@@ -9,9 +9,10 @@
 PCRE_INSTALL_STAGING = YES
 PCRE_INSTALL_TARGET = YES
 
-PCRE_CONF_OPT = --target=$(GNU_TARGET_NAME) --host=$(GNU_TARGET_NAME) \
-        --build=$(GNU_HOST_NAME) --prefix=/usr \
-        --includedir=/usr/include
+ifneq ($(BR2_INSTALL_LIBSTDCPP),y)
+# pcre will use the host g++ if a cross version isn't available
+PCRE_CONF_OPT = --disable-cpp
+endif
 
 PCRE_DEPENDENCIES = uclibc
 

             reply	other threads:[~2008-08-16 12:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-16 12:32 jacmet at uclibc.org [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-09-17 21:33 [Buildroot] svn commit: trunk/buildroot/package/pcre jacmet at uclibc.org
2008-09-18 10:28 ` Daniel Laird
2008-09-18 10:34   ` Peter Korsgaard
2008-08-16 19:36 jacmet at uclibc.org
2008-08-16 12:32 jacmet at uclibc.org
2008-08-16 12:00 jacmet at uclibc.org

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=20080816123254.E7D393C827@busybox.net \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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