Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] [git commit] cramfs.mk: drop invalid -q option
From: Peter Korsgaard @ 2012-11-30  7:25 UTC (permalink / raw)
  To: buildroot

commit: http://git.buildroot.net/buildroot/commit/?id=f27ec358ef9b6ecfc0204a3e9e899a778c55bfe8
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
 fs/cramfs/cramfs.mk |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/fs/cramfs/cramfs.mk b/fs/cramfs/cramfs.mk
index 9b0141f..55f6bdb 100644
--- a/fs/cramfs/cramfs.mk
+++ b/fs/cramfs/cramfs.mk
@@ -10,7 +10,7 @@ CRAMFS_OPTS=-l
 endif
 
 define ROOTFS_CRAMFS_CMD
- $(HOST_DIR)/usr/bin/mkcramfs -q $(CRAMFS_OPTS) $(TARGET_DIR) $$@
+ $(HOST_DIR)/usr/bin/mkcramfs $(CRAMFS_OPTS) $(TARGET_DIR) $$@
 endef
 
 ROOTFS_CRAMFS_DEPENDENCIES = host-cramfs

^ permalink raw reply related

* [Buildroot] [PATCH v2] libroxml: bump version to 2.2.1
From: Peter Korsgaard @ 2012-11-30  7:15 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <1354245658-7675-1-git-send-email-blunderer@blunderer.org>

>>>>> "blunderer" == blunderer  <blunderer@blunderer.org> writes:

 blunderer> From: Tristan Lelong <tristan.lelong@blunderer.org>
 blunderer> Thank you Arnout for your quick answer.
 blunderer> I regenerated the patch according to your advice.

Committed to next with the commit message cleaned up, thanks.

-- 
Bye, Peter Korsgaard

^ permalink raw reply

* [Buildroot] [git commit] libroxml: bump version to 2.2.1
From: Peter Korsgaard @ 2012-11-30  7:14 UTC (permalink / raw)
  To: buildroot

commit: http://git.buildroot.net/buildroot/commit/?id=b17c7963890354d2cffdda2f16eeeaf4c1288e99
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

Signed-off-by: Tristan Lelong <tristan.lelong@blunderer.org>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
 ...ml-2.2.0-werror.patch => libroxml-werror.patch} |    6 +++---
 package/libroxml/libroxml.mk                       |    2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/package/libroxml/libroxml-2.2.0-werror.patch b/package/libroxml/libroxml-werror.patch
similarity index 86%
rename from package/libroxml/libroxml-2.2.0-werror.patch
rename to package/libroxml/libroxml-werror.patch
index a72f2a7..a99962f 100644
--- a/package/libroxml/libroxml-2.2.0-werror.patch
+++ b/package/libroxml/libroxml-werror.patch
@@ -7,10 +7,10 @@ Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
  Makefile |    2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
 
-Index: libroxml-2.1.0/Makefile
+Index: a/Makefile
 ===================================================================
---- libroxml-2.1.0.orig/Makefile
-+++ libroxml-2.1.0/Makefile
+--- a/Makefile
++++ b/Makefile
 @@ -41,7 +41,7 @@
  
  # options
diff --git a/package/libroxml/libroxml.mk b/package/libroxml/libroxml.mk
index 457a28a..d7ef6a4 100644
--- a/package/libroxml/libroxml.mk
+++ b/package/libroxml/libroxml.mk
@@ -2,7 +2,7 @@
 # libroxml
 #
 
-LIBROXML_VERSION = 2.2.0
+LIBROXML_VERSION = 2.2.1
 LIBROXML_SITE = http://libroxml.googlecode.com/files
 LIBROXML_INSTALL_STAGING = YES
 

^ permalink raw reply related

* [Buildroot] [git commit branch/next] libroxml: bump version to 2.2.1
From: Peter Korsgaard @ 2012-11-30  7:14 UTC (permalink / raw)
  To: buildroot

commit: http://git.buildroot.net/buildroot/commit/?id=b17c7963890354d2cffdda2f16eeeaf4c1288e99
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/next

Signed-off-by: Tristan Lelong <tristan.lelong@blunderer.org>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
 ...ml-2.2.0-werror.patch => libroxml-werror.patch} |    6 +++---
 package/libroxml/libroxml.mk                       |    2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/package/libroxml/libroxml-2.2.0-werror.patch b/package/libroxml/libroxml-werror.patch
similarity index 86%
rename from package/libroxml/libroxml-2.2.0-werror.patch
rename to package/libroxml/libroxml-werror.patch
index a72f2a7..a99962f 100644
--- a/package/libroxml/libroxml-2.2.0-werror.patch
+++ b/package/libroxml/libroxml-werror.patch
@@ -7,10 +7,10 @@ Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
  Makefile |    2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
 
-Index: libroxml-2.1.0/Makefile
+Index: a/Makefile
 ===================================================================
---- libroxml-2.1.0.orig/Makefile
-+++ libroxml-2.1.0/Makefile
+--- a/Makefile
++++ b/Makefile
 @@ -41,7 +41,7 @@
  
  # options
diff --git a/package/libroxml/libroxml.mk b/package/libroxml/libroxml.mk
index 457a28a..d7ef6a4 100644
--- a/package/libroxml/libroxml.mk
+++ b/package/libroxml/libroxml.mk
@@ -2,7 +2,7 @@
 # libroxml
 #
 
-LIBROXML_VERSION = 2.2.0
+LIBROXML_VERSION = 2.2.1
 LIBROXML_SITE = http://libroxml.googlecode.com/files
 LIBROXML_INSTALL_STAGING = YES
 

^ permalink raw reply related

* [Buildroot] [PATCH 1/2] Change Filesystem utilities heading because it has mtd utils too.
From: Peter Korsgaard @ 2012-11-30  7:13 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <1354239711-18064-1-git-send-email-cdhmanning@gmail.com>

>>>>> "Charles" == Charles Manning <cdhmanning@gmail.com> writes:

 Charles> Changing it to Filesystem and flash utilities gives far better
 Charles> navigation for mtd utils.

Committed, thanks.

-- 
Bye, Peter Korsgaard

^ permalink raw reply

* [Buildroot] [git commit] Change Filesystem utilities heading because it has mtd utils too.
From: Peter Korsgaard @ 2012-11-30  7:13 UTC (permalink / raw)
  To: buildroot

commit: http://git.buildroot.net/buildroot/commit/?id=40f175b37ad15969e297c566037fc3ffd15541b3
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

Changing it to Filesystem and flash utilities gives far better navigation
for mtd utils.

Signed-off-by: Charles Manning <cdhmanning@gmail.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
 package/Config.in |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/package/Config.in b/package/Config.in
index 5d9783a..15d7ad6 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -177,7 +177,7 @@ source "package/xterm/Config.in"
 source "package/xvkbd/Config.in"
 endmenu
 
-menu "Filesystem utilities"
+menu "Filesystem and flash utilities"
 source "package/cifs-utils/Config.in"
 source "package/cramfs/Config.in"
 source "package/dosfstools/Config.in"

^ permalink raw reply related

* [Buildroot] [Bug 5732] Error : package/alsa-lib/alsa-lib.mk
From: bugzilla at busybox.net @ 2012-11-30  7:07 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <bug-5732-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=5732

Peter Korsgaard <jacmet@uclibc.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #1 from Peter Korsgaard <jacmet@uclibc.org> 2012-11-30 07:07:43 UTC ---
Thanks, fixed in git as 2b7be2f1de3e (alsa-lib: fix static linking check)

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

^ permalink raw reply

* [Buildroot] [git commit] alsa-lib: fix static linking check
From: Peter Korsgaard @ 2012-11-30  7:05 UTC (permalink / raw)
  To: buildroot

commit: http://git.buildroot.net/buildroot/commit/?id=2b7be2f1de3eec185a720310d418719ccc3f22f2
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

Closes #5732

The symbol for static linking is BR2_PREFER_STATIC_LIB.

Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
 CHANGES                      |    4 ++++
 package/alsa-lib/alsa-lib.mk |    2 +-
 2 files changed, 5 insertions(+), 1 deletions(-)

diff --git a/CHANGES b/CHANGES
index 0da2d77..db7b233 100644
--- a/CHANGES
+++ b/CHANGES
@@ -8,6 +8,10 @@
 	cjson, directfb, gdb, hiawatha, lcdproc, libdaemon, libecore,
 	libhid, libpcap, libusb, linux-fusion, ocf-linux, strace,
 
+	Issues resolved (http://bugs.uclibc.org):
+
+	#5732: Error : package/alsa-lib/alsa-lib.mk
+
 2012.11-rc1, Released November 17th, 2012
 
 	Fixes all over the tree and new features.
diff --git a/package/alsa-lib/alsa-lib.mk b/package/alsa-lib/alsa-lib.mk
index daa551d..eddd3d2 100644
--- a/package/alsa-lib/alsa-lib.mk
+++ b/package/alsa-lib/alsa-lib.mk
@@ -17,7 +17,7 @@ ALSA_LIB_CONF_OPT = --with-alsa-devdir=$(call qstrip,$(BR2_PACKAGE_ALSA_LIB_DEVD
 		    --without-versioned
 
 # Can't build with static & shared at the same time (1.0.25+)
-ifeq ($(BR2_PREFER_STATIC),y)
+ifeq ($(BR2_PREFER_STATIC_LIB),y)
 ALSA_LIB_CONF_OPT += --enable-shared=no
 else
 ALSA_LIB_CONF_OPT += --enable-static=no

^ permalink raw reply related

* [Buildroot] [git commit] CHANGES: update with recent changes
From: Peter Korsgaard @ 2012-11-30  7:00 UTC (permalink / raw)
  To: buildroot

commit: http://git.buildroot.net/buildroot/commit/?id=0f9bad95a08fad5469185628ef91f446ea616d48
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
 CHANGES |   10 ++++++++++
 1 files changed, 10 insertions(+), 0 deletions(-)

diff --git a/CHANGES b/CHANGES
index f8ac04b..0da2d77 100644
--- a/CHANGES
+++ b/CHANGES
@@ -1,3 +1,13 @@
+2012.11, Not released yet:
+
+	Minor fixes around the tree.
+
+	Various manual updates and fixes.
+
+	Updated/fixed packages: arptables, binutils, busybox, ccache,
+	cjson, directfb, gdb, hiawatha, lcdproc, libdaemon, libecore,
+	libhid, libpcap, libusb, linux-fusion, ocf-linux, strace,
+
 2012.11-rc1, Released November 17th, 2012
 
 	Fixes all over the tree and new features.

^ permalink raw reply related

* [Buildroot] [PATCH v2] libroxml: bump version to 2.2.1
From: Samuel Martin @ 2012-11-30  5:42 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <1354245658-7675-1-git-send-email-blunderer@blunderer.org>

Hi Tristan,

2012/11/30  <blunderer@blunderer.org>:
> From: Tristan Lelong <tristan.lelong@blunderer.org>
>
> Thank you Arnout for your quick answer.
> I regenerated the patch according to your advice.
>
> Regards,
>
> Signed-off-by: Tristan Lelong <tristan.lelong@blunderer.org>
> ---

Well,keep the commit as much relevent as possible, without personal comment.

If you want to add additional comments that aren't supposed to go in the git log
message, add it below the Signed-off-by line, separated by ---.
Then git-am will remove that part automatically.
This comment section is usually used for the changelog in case of
update of the patch.
So typically you'll see:

Signed-off-by: ...
---
Some comments.

v2:
* fix this
* rework that as suggested by John Doe


>  .../{libroxml-2.2.0-werror.patch => libroxml-werror.patch}       |    6 +++---
>  package/libroxml/libroxml.mk                                     |    2 +-
>  2 files changed, 4 insertions(+), 4 deletions(-)
>  rename package/libroxml/{libroxml-2.2.0-werror.patch => libroxml-werror.patch} (86%)
>
> diff --git a/package/libroxml/libroxml-2.2.0-werror.patch b/package/libroxml/libroxml-werror.patch
> similarity index 86%
> rename from package/libroxml/libroxml-2.2.0-werror.patch
> rename to package/libroxml/libroxml-werror.patch
> index a72f2a7..a99962f 100644
> --- a/package/libroxml/libroxml-2.2.0-werror.patch
> +++ b/package/libroxml/libroxml-werror.patch
> @@ -7,10 +7,10 @@ Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
>   Makefile |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> -Index: libroxml-2.1.0/Makefile
> +Index: a/Makefile
>  ===================================================================
> ---- libroxml-2.1.0.orig/Makefile
> -+++ libroxml-2.1.0/Makefile
> +--- a/Makefile
> ++++ b/Makefile
>  @@ -41,7 +41,7 @@
>
>   # options
The change in package/libroxml/libroxml-2.2.0-werror.patch does not
seem really needed, though the renaming is ok.


> diff --git a/package/libroxml/libroxml.mk b/package/libroxml/libroxml.mk
> index 457a28a..d7ef6a4 100644
> --- a/package/libroxml/libroxml.mk
> +++ b/package/libroxml/libroxml.mk
> @@ -2,7 +2,7 @@
>  # libroxml
>  #
>
> -LIBROXML_VERSION = 2.2.0
> +LIBROXML_VERSION = 2.2.1
>  LIBROXML_SITE = http://libroxml.googlecode.com/files
>  LIBROXML_INSTALL_STAGING = YES
>
> --


Regards,

-- 
Sam

^ permalink raw reply

* [Buildroot] PATCH > To integrate pycrypto into Buildroot
From: Samuel Martin @ 2012-11-30  5:21 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <07407110F438184D9D87521726FF42D41F65F296@M357PRD2.ad.bcc.qld.gov.au>

Hi Noel,

2012/11/30 Noel Roberts <Noel.Roberts@brisbane.qld.gov.au>:
> Good day Arnout
>
> Grrrr, git send-email has issues with my virtual machine/proxy configuration. Not getting decent error messages and googling didn't help either. Not sure which part isn't working, just that SMPT couldn't initialize correctly.
>
To use git send-email you may need some additional Perl packages:
net-smtp-ssl, authen-sasl.
(see the Example section in:
http://www.kernel.org/pub/software/scm/git/docs/git-send-email.html)


Regards,

-- 
Sam

^ permalink raw reply

* [Buildroot] [PATCH v2] libroxml: bump version to 2.2.1
From: blunderer at blunderer.org @ 2012-11-30  3:20 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <[PATCH] libroxml: bump version to 2.2.1>

From: Tristan Lelong <tristan.lelong@blunderer.org>

Thank you Arnout for your quick answer.
I regenerated the patch according to your advice.

Regards,

Signed-off-by: Tristan Lelong <tristan.lelong@blunderer.org>
---
 .../{libroxml-2.2.0-werror.patch => libroxml-werror.patch}       |    6 +++---
 package/libroxml/libroxml.mk                                     |    2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)
 rename package/libroxml/{libroxml-2.2.0-werror.patch => libroxml-werror.patch} (86%)

diff --git a/package/libroxml/libroxml-2.2.0-werror.patch b/package/libroxml/libroxml-werror.patch
similarity index 86%
rename from package/libroxml/libroxml-2.2.0-werror.patch
rename to package/libroxml/libroxml-werror.patch
index a72f2a7..a99962f 100644
--- a/package/libroxml/libroxml-2.2.0-werror.patch
+++ b/package/libroxml/libroxml-werror.patch
@@ -7,10 +7,10 @@ Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
  Makefile |    2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
 
-Index: libroxml-2.1.0/Makefile
+Index: a/Makefile
 ===================================================================
---- libroxml-2.1.0.orig/Makefile
-+++ libroxml-2.1.0/Makefile
+--- a/Makefile
++++ b/Makefile
 @@ -41,7 +41,7 @@
  
  # options
diff --git a/package/libroxml/libroxml.mk b/package/libroxml/libroxml.mk
index 457a28a..d7ef6a4 100644
--- a/package/libroxml/libroxml.mk
+++ b/package/libroxml/libroxml.mk
@@ -2,7 +2,7 @@
 # libroxml
 #
 
-LIBROXML_VERSION = 2.2.0
+LIBROXML_VERSION = 2.2.1
 LIBROXML_SITE = http://libroxml.googlecode.com/files
 LIBROXML_INSTALL_STAGING = YES
 
-- 
1.7.10.4

^ permalink raw reply related

* [Buildroot] PATCH > To integrate pycrypto into Buildroot
From: Noel Roberts @ 2012-11-30  2:27 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <50B67E54.4060006@mind.be>

Good day Arnout

Grrrr, git send-email has issues with my virtual machine/proxy configuration. Not getting decent error messages and googling didn't help either. Not sure which part isn't working, just that SMPT couldn't initialize correctly.

Attached are the newest patch files.



-----Original Message-----
From: Arnout Vandecappelle [mailto:arnout at mind.be] 
Sent: Thursday, 29 November 2012 7:13 AM
To: Noel Roberts
Cc: buildroot at uclibc.org
Subject: Re: [Buildroot] PATCH > To integrate pycrypto into Buildroot

On 28/11/12 06:05, Noel Roberts wrote:
> This patch allows Buildroot to cross compile the crypto libraries 
> needed for python integration, enabling good cryptographic support within Python.
>
> This is my first patch submission - please advise me, if I need to rework anything.

  We prefer patches to be sent in-line (with git send-email) because then it is easier to comment on them.  But I'll already give some feedback before you re-post.

- If you include it in package/Config.in's 'external python modules' menu, then the 'depends on BR2_PACKAGE_PYTHON' is redundant.

- Please add the license information:
PYTHON_CRYPTO_LICENSE = Public domain, Python 2.2 license PYTHON_CRYPTO_LICENSE_FILES = COPYRIGHT LEGAL/copy/LICENSE.python-2.2

- Since there is a check for wchar.h in configure.ac, I would add an explicit 'depends on BR2_USE_WCHAR', even though python itself already depends on it. But who knows, maybe that will ever be removed.


  Regards,
  Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

****************************************************
This message has passed through an insecure network.
Please direct all enquiries to the message author.
****************************************************

****************************************************
This message has passed through an insecure network.
Please direct all enquiries to the message author.
****************************************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Adding-pyCrypto-functionality-in-Buildroot.patch
Type: application/octet-stream
Size: 1883 bytes
Desc: 0001-Adding-pyCrypto-functionality-in-Buildroot.patch
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121130/5330b901/attachment-0003.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Added-commentator-feedback.patch
Type: application/octet-stream
Size: 1465 bytes
Desc: 0002-Added-commentator-feedback.patch
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121130/5330b901/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0003-Added-missing-Config.in-in-git-commit.patch
Type: application/octet-stream
Size: 810 bytes
Desc: 0003-Added-missing-Config.in-in-git-commit.patch
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121130/5330b901/attachment-0005.obj>

^ permalink raw reply

* [Buildroot] [PATCH 2/2] libsigc: Don't copy devel documentation onto target
From: Charles Manning @ 2012-11-30  1:42 UTC (permalink / raw)
  To: buildroot

The libsigc++ developer documentation was being copied onto the target.
Add a clean-up to fix that.

There is probably a better way to do this but I still have training wheels.

Signed-off-by: Charles Manning <cdhmanning@gmail.com>
---
 package/libsigc/libsigc.mk |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/package/libsigc/libsigc.mk b/package/libsigc/libsigc.mk
index 92d1d8b..10f5803 100644
--- a/package/libsigc/libsigc.mk
+++ b/package/libsigc/libsigc.mk
@@ -8,4 +8,10 @@ LIBSIGC_SOURCE = libsigc++-$(LIBSIGC_VERSION).tar.bz2
 LIBSIGC_SITE = http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.2
 LIBSIGC_INSTALL_STAGING = YES
 
+define LIBSIGC_INSTALL_TARGET_FIXUP
+	rm -rf $(TARGET_DIR)/usr/share/devhelp/books/libsigc++*
+endef
+
+LIBSIGC_POST_INSTALL_TARGET_HOOKS += LIBSIGC_INSTALL_TARGET_FIXUP
+
 $(eval $(autotools-package))
-- 
1.7.1

^ permalink raw reply related

* [Buildroot] [PATCH 1/2] Change Filesystem utilities heading because it has mtd utils too.
From: Charles Manning @ 2012-11-30  1:41 UTC (permalink / raw)
  To: buildroot

Changing it to Filesystem and flash utilities gives far better navigation
for  mtd utils.

Signed-off-by: Charles Manning <cdhmanning@gmail.com>
---
 package/Config.in |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/package/Config.in b/package/Config.in
index 5d9783a..15d7ad6 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -177,7 +177,7 @@ source "package/xterm/Config.in"
 source "package/xvkbd/Config.in"
 endmenu
 
-menu "Filesystem utilities"
+menu "Filesystem and flash utilities"
 source "package/cifs-utils/Config.in"
 source "package/cramfs/Config.in"
 source "package/dosfstools/Config.in"
-- 
1.7.1

^ permalink raw reply related

* [Buildroot] mkcramfs invalid option 'q'
From: Woody Wu @ 2012-11-30  0:50 UTC (permalink / raw)
  To: buildroot

Hi, list

What now concerns me is an warning message in the output of building
cramfs image:


...
tdir=/home/buildroot/buildroot-2012.08/output/target
table='/home/buildroot/buildroot-2012.08/output/build/_device_table.txt'
/home/buildroot/buildroot-2012.08/output/host/usr/bin/mkcramfs: invalid
option -- 'q'
...

I just want to ensure that this is normal and I don't need to warry
about it. Otherwise, please someone tell me a fix.  Thanks!

-- 
woody
I can't go back to yesterday - because I was a different person then.

^ permalink raw reply

* [Buildroot] [PATCH 09/33] linux-fusion: fix build
From: Peter Korsgaard @ 2012-11-30  0:34 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <1353543503-8952-10-git-send-email-s.martin49@gmail.com>

>>>>> "Samuel" == Samuel Martin <s.martin49@gmail.com> writes:

 Samuel> Signed-off-by: Samuel Martin <s.martin49@gmail.com>

Committed, thanks.

-- 
Bye, Peter Korsgaard

^ permalink raw reply

* [Buildroot] [git commit] linux-fusion: fix build
From: Peter Korsgaard @ 2012-11-30  0:33 UTC (permalink / raw)
  To: buildroot

commit: http://git.buildroot.net/buildroot/commit/?id=ba66de55ffc6a331a69ceac42a065da2200f905e
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Acked-by: Simon Dawson <spdawson@gmail.com>
Tested-by: Simon Dawson <spdawson@gmail.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
 .../linux-fusion/linux-fusion-fix-include.patch    |   52 ++++++++++++++++++++
 1 files changed, 52 insertions(+), 0 deletions(-)

diff --git a/package/linux-fusion/linux-fusion-fix-include.patch b/package/linux-fusion/linux-fusion-fix-include.patch
new file mode 100644
index 0000000..fe91488
--- /dev/null
+++ b/package/linux-fusion/linux-fusion-fix-include.patch
@@ -0,0 +1,52 @@
+Fix directfb-fusion kernel module build.
+
+This patch avoids the following error occurs:
+
+/usr/bin/make -f scripts/Makefile.build obj=/opt/br/output/build/linux-fusion-8.8.1/linux/drivers/char/fusion /opt/br/output/host/usr/bin/ccache 
+  /opt/br/output/host/usr/bin/arm-buildroot-linux-uclibcgnueabi-gcc -Wp,-MD,/opt/br/output/build/linux-fusion-8.8.1/linux/drivers/char/fusion/single/.fusioncore_impl.o.d
+  -nostdinc -isystem /opt/br/output/host/usr/lib/gcc/arm-buildroot-linux-uclibcgnueabi/4.6.3/include -I/opt/br/output/build/linux-3.6/arch/arm/include 
+  -Iarch/arm/include/generated -Iinclude  -include /opt/br/output/build/linux-3.6/include/linux/kconfig.h -D__KERNEL__ -mlittle-endian -Iarch/arm/mach-versatile/include
+  -Iarch/arm/plat-versatile/include -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -I/opt/br/output/build/linux-fusion-8.8.1/linux/include -Wall -Wundef 
+  -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -marm 
+  -fno-dwarf2-cfi-asm -mabi=aapcs-linux -mno-thumb-interwork -funwind-tables -D__LINUX_ARM_ARCH__=5 -march=armv5te -mtune=arm9tdmi -msoft-float -Uarm -Wframe-larger-than=1024
+  -fno-stack-protector -Wno-unused-but-set-variable -fomit-frame-pointer -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack  -DMODULE
+  -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(fusioncore_impl)"  -D"KBUILD_MODNAME=KBUILD_STR(fusion)" -c -o 
+/opt/br/output/build/linux-fusion-8.8.1/linux/drivers/char/fusion/single/fusioncore_impl.o /opt/br/output/build/linux-fusion-8.8.1/linux/drivers/char/fusion/single/fusioncore_impl.c
+/opt/br/output/build/linux-fusion-8.8.1/linux/drivers/char/fusion/single/fusioncore_impl.c:25:19: fatal error: debug.h: No such file or directory
+compilation terminated.
+make[3]: *** [/opt/br/output/build/linux-fusion-8.8.1/linux/drivers/char/fusion/single/fusioncore_impl.o] Error 1
+make[2]: *** [_module_/opt/br/output/build/linux-fusion-8.8.1/linux/drivers/char/fusion] Error 2
+make[2]: Leaving directory `/opt/br/output/build/linux-3.6'
+make[1]: *** [modules] Error 2
+make[1]: Leaving directory `/opt/br/output/build/linux-fusion-8.8.1'
+
+
+Signed-off-by: Samuel Martin <s.martin49@gmail.com>
+
+diff -purN linux-fusion-8.8.1.orig/linux/drivers/char/fusion/fusioncore.h linux-fusion-8.8.1/linux/drivers/char/fusion/fusioncore.h
+--- linux-fusion-8.8.1.orig/linux/drivers/char/fusion/fusioncore.h	2012-10-15 21:47:53.881834496 +0200
++++ linux-fusion-8.8.1/linux/drivers/char/fusion/fusioncore.h	2012-10-15 22:05:27.232401023 +0200
+@@ -17,7 +17,7 @@
+ 
+ #include <linux/stddef.h>
+ 
+-#include "fusioncore_impl.h"
++#include "single/fusioncore_impl.h"
+ 
+ typedef enum {
+      FC_OK,
+diff -purN linux-fusion-8.8.1.orig/linux/drivers/char/fusion/single/fusioncore_impl.c linux-fusion-8.8.1/linux/drivers/char/fusion/single/fusioncore_impl.c
+--- linux-fusion-8.8.1.orig/linux/drivers/char/fusion/single/fusioncore_impl.c	2012-10-15 21:47:53.878501243 +0200
++++ linux-fusion-8.8.1/linux/drivers/char/fusion/single/fusioncore_impl.c	2012-10-15 22:05:38.585511304 +0200
+@@ -22,9 +22,9 @@
+ #include <linux/slab.h>
+ #include <linux/sched.h>
+ 
+-#include "debug.h"
++#include "../debug.h"
+ 
+-#include "fusioncore.h"
++#include "../fusioncore.h"
+ 
+ 
+ 

^ permalink raw reply related

* [Buildroot] [PATCH 1/1] strace: remove undef-CTL_PROC patch
From: Peter Korsgaard @ 2012-11-30  0:32 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <1354209118-12653-1-git-send-email-james.hogan@imgtec.com>

>>>>> "James" == James Hogan <james.hogan@imgtec.com> writes:

 James> This patch is no longer necessary since strace-v4.5.15 which always
 James> defines CTL_PROC. Specifically strace git commit
 James> 35a55785ea8ff44d214af52085e3a5ea624730aa.

Committed, thanks.

-- 
Bye, Peter Korsgaard

^ permalink raw reply

* [Buildroot] [git commit] strace: remove undef-CTL_PROC patch
From: Peter Korsgaard @ 2012-11-30  0:32 UTC (permalink / raw)
  To: buildroot

commit: http://git.buildroot.net/buildroot/commit/?id=d490bb6c371468d027e228a445c258af4a272ba7
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

This patch is no longer necessary since strace-v4.5.15 which always
defines CTL_PROC. Specifically strace git commit
35a55785ea8ff44d214af52085e3a5ea624730aa.

Signed-off-by: James Hogan <james.hogan@imgtec.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
 package/strace/strace-undef-CTL_PROC.patch |   12 ------------
 1 files changed, 0 insertions(+), 12 deletions(-)

diff --git a/package/strace/strace-undef-CTL_PROC.patch b/package/strace/strace-undef-CTL_PROC.patch
deleted file mode 100644
index d841999..0000000
--- a/package/strace/strace-undef-CTL_PROC.patch
+++ /dev/null
@@ -1,12 +0,0 @@
---- a/system.c
-+++ b/system.c
-@@ -1614,7 +1614,9 @@ static const struct xlat sysctl_root[] =
- 	{ CTL_KERN, "CTL_KERN" },
- 	{ CTL_VM, "CTL_VM" },
- 	{ CTL_NET, "CTL_NET" },
-+#ifdef CTL_PROC
- 	{ CTL_PROC, "CTL_PROC" },
-+#endif
- 	{ CTL_FS, "CTL_FS" },
- 	{ CTL_DEBUG, "CTL_DEBUG" },
- 	{ CTL_DEV, "CTL_DEV" },

^ permalink raw reply related

* [Buildroot] [PATCH] [PATCH][RFC] new target: live filesystem
From: Steve Calfee @ 2012-11-30  0:04 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <1354003953-10875-1-git-send-email-jeremy.rosen@openwide.fr>

I don't understand why you need this. It is a one line "sudo tar -xf
..." to unpack the tarball into your nfs directory. Either type this
line or add a one line script to your ~/bin directory to do it for
each of your buildroot trees/environments. Don't add clutter to the
buildroot makefile.

Regards, Steve

On Tue, Nov 27, 2012 at 12:12 AM, J?r?my Rosen <jeremy.rosen@openwide.fr> wrote:
> add a new target to deploy a live filesystem to be used by NFS
>
> ---
>
> Hello everybody
>
> this patch is not ready for commit, it's a proposal to help me solve the very common use case of
> a developement FS deployed on NFS. I am not very happy of how it's done at this point but I would
> like to discuss it to see if it has a chance to get merged... What I don't like (and would gladly
> have ideas on how to solve this)
> * no dependency on host-sudo, i'm not sure how to add that
> * using sudo to break out of fakeroot is not clean
> * I am abusing the fs building framework, but I don't know of a cleaner way
> * filesystem can only be under output/images at this point
>
> so this patch is more to start a discussion than anything, i'll gladly take any comments or plain
> 'ol rejection if the project doesn't want it... but if there is some interest i'll work it into
> something mainline worthy
>
> Regards
>
> J?r?my Rosen
> ---
>  fs/Config.in      |    1 +
>  fs/live/Config.in |   16 ++++++++++++++++
>  fs/live/live.mk   |   23 +++++++++++++++++++++++
>  3 files changed, 40 insertions(+)
>  create mode 100644 fs/live/Config.in
>  create mode 100644 fs/live/live.mk
>
> diff --git a/fs/Config.in b/fs/Config.in
> index 94154ea..de2377e 100644
> --- a/fs/Config.in
> +++ b/fs/Config.in
> @@ -11,5 +11,6 @@ source "fs/cpio/Config.in"
>  source "fs/iso9660/Config.in"
>  source "fs/initramfs/Config.in"
>  source "fs/romfs/Config.in"
> +source "fs/live/Config.in"
>
>  endmenu
> diff --git a/fs/live/Config.in b/fs/live/Config.in
> new file mode 100644
> index 0000000..bf24754
> --- /dev/null
> +++ b/fs/live/Config.in
> @@ -0,0 +1,16 @@
> +config BR2_TARGET_ROOTFS_LIVE
> +       bool "live root filesystem"
> +       help
> +         uses sudo to create a live image of the filesystem
> +         this is mainly usefull if you want to use your filesystem
> +         over NFS
> +config BR2_TARGET_ROOTFS_LIVE_DEST
> +       string "directory to put the live image"
> +       depends on BR2_TARGET_ROOTFS_LIVE
> +       default "live"
> +       help
> +         The directory where the image should be stored.
> +         this directory will be emptied and recreated, it is given
> +         relative to the buildroot output/images directory
> +
> +
> diff --git a/fs/live/live.mk b/fs/live/live.mk
> new file mode 100644
> index 0000000..73bcd3e
> --- /dev/null
> +++ b/fs/live/live.mk
> @@ -0,0 +1,23 @@
> +#############################################################
> +#
> +# Build the live root filesystem directory
> +#
> +#############################################################
> +
> +LIVE_OPTS :=
> +
> +
> +ROOTFS_LIVE_DEPENDENCIES = #host-sudo
> +
> +define ROOTFS_LIVE_CMD
> + sudo cp -r $(TARGET_DIR)/* $(BINARIES_DIR)/$(BR2_TARGET_ROOTFS_LIVE_DEST)/
> +endef
> +
> +define ROOTFS_LIVE_INIT
> +       sudo rm -rf $(BINARIES_DIR)/$(BR2_TARGET_ROOTFS_LIVE_DEST)
> +       sudo mkdir $(BINARIES_DIR)/$(BR2_TARGET_ROOTFS_LIVE_DEST)
> +endef
> +
> +ROOTFS_LIVE_PRE_GEN_HOOKS += ROOTFS_LIVE_INIT
> +
> +$(eval $(call ROOTFS_TARGET,live))
> --
> 1.7.10.4
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

^ permalink raw reply

* [Buildroot] [PATCH][RFC] new target: live filesystem
From: Arnout Vandecappelle @ 2012-11-29 23:43 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <1354003953-10875-1-git-send-email-jeremy.rosen@openwide.fr>

On 27/11/12 09:12, J?r?my Rosen wrote:
> add a new target to deploy a live filesystem to be used by NFS
>
> ---
>
> Hello everybody
>
> this patch is not ready for commit, it's a proposal to help me solve the very common use case of
> a developement FS deployed on NFS. I am not very happy of how it's done at this point but I would
> like to discuss it to see if it has a chance to get merged... What I don't like (and would gladly
> have ideas on how to solve this)
> * no dependency on host-sudo, i'm not sure how to add that

  That's impossible. The sudo executable must be setuid root, and to make
it setuid root you have to be root, so sudo must already exist...

  You could instead add a check in live.mk if sudo actually works.  But since
sudo may ask for a password this can get tricky - you should e.g. probably check
if stdin is a terminal as well.

  That said, I don't know if Peter will accept running sudo within buildroot.

> * using sudo to break out of fakeroot is not clean

  I don't see much of a problem there.

> * I am abusing the fs building framework, but I don't know of a cleaner way

  You're not abusing it.

> * filesystem can only be under output/images at this point

  That's not good but easy to solve.

>
> so this patch is more to start a discussion than anything, i'll gladly take any comments or plain
> 'ol rejection if the project doesn't want it... but if there is some interest i'll work it into
> something mainline worthy
>
> Regards
>
> J?r?my Rosen
> ---
>   fs/Config.in      |    1 +
>   fs/live/Config.in |   16 ++++++++++++++++
>   fs/live/live.mk   |   23 +++++++++++++++++++++++
>   3 files changed, 40 insertions(+)
>   create mode 100644 fs/live/Config.in
>   create mode 100644 fs/live/live.mk
>
> diff --git a/fs/Config.in b/fs/Config.in
> index 94154ea..de2377e 100644
> --- a/fs/Config.in
> +++ b/fs/Config.in
> @@ -11,5 +11,6 @@ source "fs/cpio/Config.in"
>   source "fs/iso9660/Config.in"
>   source "fs/initramfs/Config.in"
>   source "fs/romfs/Config.in"
> +source "fs/live/Config.in"

  Sort alphabetically please.

>
>   endmenu
> diff --git a/fs/live/Config.in b/fs/live/Config.in
> new file mode 100644
> index 0000000..bf24754
> --- /dev/null
> +++ b/fs/live/Config.in
> @@ -0,0 +1,16 @@
> +config BR2_TARGET_ROOTFS_LIVE
> +	bool "live root filesystem"
> +	help
> +	  uses sudo to create a live image of the filesystem
> +	  this is mainly usefull if you want to use your filesystem

  useful

> +	  over NFS

  or as a chroot

> +config BR2_TARGET_ROOTFS_LIVE_DEST
> +	string "directory to put the live image"

  "live image location"

> +	depends on BR2_TARGET_ROOTFS_LIVE
> +	default "live"

  Use an empty default, and give an error in live.mk if it's
empty.

> +	help
> +	  The directory where the image should be stored.
> +	  this directory will be emptied and recreated, it is given
> +	  relative to the buildroot output/images directory

  Make it an absolute path instead.

> +
> diff --git a/fs/live/live.mk b/fs/live/live.mk
> new file mode 100644
> index 0000000..73bcd3e
> --- /dev/null
> +++ b/fs/live/live.mk
> @@ -0,0 +1,23 @@
> +#############################################################
> +#
> +# Build the live root filesystem directory
> +#
> +#############################################################
> +
> +LIVE_OPTS :=

  This is unneeded.

> +
> +
> +ROOTFS_LIVE_DEPENDENCIES = #host-sudo

  This as well.

> +
> +define ROOTFS_LIVE_CMD
> + sudo cp -r $(TARGET_DIR)/* $(BINARIES_DIR)/$(BR2_TARGET_ROOTFS_LIVE_DEST)/

  That won't work, because device nodes, symlinks etc. are not
copied correctly.  Use cp -a.  Or even better, rsync -a --delete-during
(then you don't need to remove it first).

  For the target, just use $(BR2_TARGET_ROOTFS_LIVE_DEST).


  Regards,
  Arnout


> +endef
> +
> +define ROOTFS_LIVE_INIT
> +	sudo rm -rf $(BINARIES_DIR)/$(BR2_TARGET_ROOTFS_LIVE_DEST)
> +	sudo mkdir $(BINARIES_DIR)/$(BR2_TARGET_ROOTFS_LIVE_DEST)
> +endef
> +
> +ROOTFS_LIVE_PRE_GEN_HOOKS += ROOTFS_LIVE_INIT
> +
> +$(eval $(call ROOTFS_TARGET,live))

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

^ permalink raw reply

* [Buildroot] Improving config navigation for mtd tools
From: Arnout Vandecappelle @ 2012-11-29 23:22 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <CAE21AQqPOGLxFVdCjaFpPo1x2kXCSo3+VbwvYk=THKfRbk+-UQ@mail.gmail.com>

On 28/11/12 01:12, Charles Manning wrote:
> Hello All
>
> The mtd utilities are part flash utilities and part file system
> utilities. This makes it a bit cryptic to put them under "Filesystem
> utilities".
>
> I suggest this can be resolved by remaining the heading to "Filesystem
> and flash utilities"

  Thank you, that's a good idea.  Could you post a proper patch?
That means:

- Write a commit message that documents the change (more
or less what you wrote above).

- Add a Signed-off-by line for yourself.  This is a short way for you to
assert that you are entitled to contribute the patch under buildroot's
GPL license.  See  http://elinux.org/Developer_Certificate_Of_Origin
for more details.

- Preferably send it with git-send-email.

  This will also add you to the list of buildroot contributors :-)

  Regards,
  Arnout

>
>
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -177,7 +177,7 @@ source "package/xterm/Config.in"
>   source "package/xvkbd/Config.in"
>   endmenu
>
> -menu "Filesystem utilities"
> +menu "Filesystem and flash utilities"
>   source "package/cifs-utils/Config.in"
>   source "package/cramfs/Config.in"
>   source "package/dosfstools/Config.in"
>
>
> Regards
>
> Charles
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

^ permalink raw reply

* [Buildroot] [PATCH] flex: fix build for nommu systems
From: Arnout Vandecappelle @ 2012-11-29 23:19 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <1354113314-30687-1-git-send-email-gustavo@zacarias.com.ar>

On 28/11/12 15:35, Gustavo Zacarias wrote:
> The flex binary uses fork() so it breaks on !MMU builds.
> Since we usually don't require flex in the target and the common
> scenario is that we just want libfl in staging reverse the options so
> that BR2_PACKAGE_FLEX just builds and install libfl.a and change the
> LIBFL option to BR2_PACKAGE_FLEX_BINARY to install the binary in the
> target.
>
> Signed-off-by: Gustavo Zacarias<gustavo@zacarias.com.ar>

Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
  (untested, visual review only)

  Two small comments.

[snip]
> +ifeq ($(BR2_PACKAGE_FLEX_BINARY),)

  I would prefer to compare with y and swap the two branches
(that will also make the diff much more readable...)

> +define FLEX_DISABLE_PROGRAM
> +	$(SED) 's/^bin_PROGRAMS.*//' $(@D)/Makefile.in
>   endef
>
> -define FLEX_UNINSTALL_LEX
> -	-rm $(TARGET_DIR)/usr/bin/lex
> -endef
> +FLEX_POST_EXTRACT_HOOKS += FLEX_DISABLE_PROGRAM

  POST_PATCH_HOOKS would be more appropriate.


  Regards,
  Arnout

>
> -FLEX_POST_INSTALL_HOOKS += FLEX_INSTALL_LEX
> -FLEX_POST_CLEAN_HOOKS += FLEX_UNINSTALL_LEX
> +else
>
> -# libfl installation
> -ifeq ($(BR2_PACKAGE_FLEX_LIBFL),y)
> -define FLEX_INSTALL_LIBFL
> -	install -D $(FLEX_DIR)/libfl.a $(STAGING_DIR)/usr/lib/libfl.a
> +# lex ->  flex
> +define FLEX_INSTALL_LEX
> +	cd $(TARGET_DIR)/usr/bin&&  ln -snf flex lex
>   endef
>
> -define FLEX_UNINSTALL_LIBFL
> -	-rm $(STAGING_DIR)/lib/libfl.a
> -endef
> +FLEX_POST_INSTALL_HOOKS += FLEX_INSTALL_LEX
>
> -FLEX_POST_INSTALL_HOOKS += FLEX_INSTALL_LIBFL
> -FLEX_POST_CLEAN_HOOKS += FLEX_UNINSTALL_LIBFL
>   endif
>
>   $(eval $(autotools-package))
[snip]

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

^ permalink raw reply

* [Buildroot] Problem building libglib2
From: Thomas Petazzoni @ 2012-11-29 23:11 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <50B7C54C.3010103@mind.be>

Dear Arnout Vandecappelle,

On Thu, 29 Nov 2012 21:27:56 +0100, Arnout Vandecappelle wrote:

>   We could obviously solve this by unexporting PKG_CONFIG_SYSROOT_DIR, but
> perhaps the better approach is to remove those environment variables from our
> custom pkgconf?

No, we use PKG_CONFIG_SYSROOT_DIR="/" when we build packages for the
host, so we can't simply remove support for the PKG_CONFIG_SYSROOT_DIR
environment variable. Unexporting PKG_CONFIG_SYSROOT_DIR sounds like
the good solution here.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

^ permalink raw reply


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox