Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: universe II <universeii@gmx.de>
To: buildroot@busybox.net
Subject: [Buildroot] Add missing config to RPM target package
Date: Fri, 21 Aug 2015 13:26:43 +0200	[thread overview]
Message-ID: <55D70AF3.3050604@gmx.de> (raw)

Dear all,
building the RPM package for my remote target I found a misconfiguration 
of the .mk file.
If the regular expression package pcre is enabled in buildroot, rpm will 
use it. If not, nothing will be used and regular expression are not 
available, making rpm unusable. But rpm has the ability to use an 
internal pcre implementation if the external lib is not available. This 
needs to be correctly activated before building and then rpm works fine 
on the target. See the attached patch for more details.

Regards,
Andreas


diff -Naur a/package/rpm/rpm.mk b/package/rpm/rpm.mk
--- a/package/rpm/rpm.mk        2015-08-07 11:38:37.559148663 +0200
+++ b/package/rpm/rpm.mk        2015-08-21 11:13:31.679042077 +0200
@@ -34,7 +34,7 @@
  RPM_DEPENDENCIES += pcre
  RPM_CONF_OPTS += --with-pcre=external
  else
-RPM_CONF_OPTS += --with-pcre=none
+RPM_CONF_OPTS += --with-pcre=internal
  endif

  ifeq ($(BR2_PACKAGE_FILE),y)

             reply	other threads:[~2015-08-21 11:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21 11:26 universe II [this message]
2015-08-21 13:41 ` [Buildroot] Add missing config to RPM target package Vicente Olivert Riera
2015-08-24 16:25   ` universe II
2015-08-25  9:38     ` Vicente Olivert Riera
2015-08-25 19:14       ` Andreas Ehmanns
2015-08-23 18:06 ` Thomas Petazzoni
2015-08-25 19:28   ` Andreas Ehmanns
2015-08-31 14:32     ` Thomas Petazzoni
     [not found]       ` <55E89D2B.4090804@gmx.de>
2015-12-04  7:30         ` Andreas Ehmanns
2015-12-04  8:13           ` Thomas Petazzoni

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=55D70AF3.3050604@gmx.de \
    --to=universeii@gmx.de \
    --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