<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.embedded.crossdev">
    <title>gmane.comp.embedded.crossdev</title>
    <link>http://blog.gmane.org/gmane.comp.embedded.crossdev</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/114"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/109"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/108"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/106"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/98"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/94"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/77"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/68"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/66"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/65"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/56"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/51"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/47"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/46"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/45"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/40"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/33"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/14"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/13"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.embedded.crossdev/11"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/114">
    <title>[PATCH] [PATCH] only include execinfo.h if crashtracesupport is enabled</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/114</link>
    <description>&lt;pre&gt;On systems without backtrace suport (E.G. uClibc depending on config),
execinfo.h might not be available, breaking the build.

Fix it by only including it if enabled.

Signed-off-by: Peter Korsgaard &amp;lt;jacmet-OfajU3CKLf1/SzgSGea1oA&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
---
 src/logging/nm-logging.c |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/src/logging/nm-logging.c b/src/logging/nm-logging.c
index ca6a709..26c8670 100644
--- a/src/logging/nm-logging.c
+++ b/src/logging/nm-logging.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -23,7 +23,6 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 
 #include &amp;lt;dlfcn.h&amp;gt;
 #include &amp;lt;syslog.h&amp;gt;
-#include &amp;lt;execinfo.h&amp;gt;
 #include &amp;lt;stdio.h&amp;gt;
 #include &amp;lt;stdlib.h&amp;gt;
 #include &amp;lt;unistd.h&amp;gt;
&lt;/pre&gt;</description>
    <dc:creator>Peter Korsgaard</dc:creator>
    <dc:date>2012-01-02T13:49:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/109">
    <title>beecrypt: Use AC_COMPILE_IFELSE for ICU check for crosscompilation compat</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/109</link>
    <description>&lt;pre&gt;AC_RUN_IFELSE doesn't work when cross compiling, but we can do the
check in the preprocessor instead and use AC_COMPILE_IFELSE.

Signed-off-by: Peter Korsgaard &amp;lt;jacmet-OfajU3CKLf1/SzgSGea1oA&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
---
 configure.ac |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

Index: beecrypt-4.2.1/configure.ac
===================================================================
--- beecrypt-4.2.1.orig/configure.ac
+++ beecrypt-4.2.1/configure.ac
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -295,13 +295,13 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 if test "$ac_with_cplusplus" = yes; then
   AC_MSG_CHECKING([for IBM's ICU library version &amp;gt;= 2.8])
   AC_LANG_PUSH(C)
-  AC_RUN_IFELSE([
+  AC_COMPILE_IFELSE([
     AC_LANG_PROGRAM([[#include &amp;lt;unicode/uversion.h&amp;gt;]],[[
       #if U_ICU_VERSION_MAJOR_NUM &amp;lt; 2
-      exit(1);
+      #error too old
       #elif U_ICU_VERSION_MAJOR_NUM == 2
       # if U_ICU_VERSION_MINOR_NUM &amp;lt; 8
-      exit(1);
+      #error too old
       # else
       exit(0);
       # endif

&lt;/pre&gt;</description>
    <dc:creator>Peter Korsgaard</dc:creator>
    <dc:date>2011-12-14T22:43:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/108">
    <title>beecrypt: Only compile/link cppglue.cxx if--with-cplusplus is used</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/108</link>
    <description>&lt;pre&gt;Bloats libbeecrypt for no use and breaks build on systems without a C++
compiler.

Signed-off-by: Peter Korsgaard &amp;lt;jacmet-OfajU3CKLf1/SzgSGea1oA&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
---
 Makefile.am |    7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

Index: beecrypt-4.2.1/Makefile.am
===================================================================
--- beecrypt-4.2.1.orig/Makefile.am
+++ beecrypt-4.2.1/Makefile.am
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -62,7 +62,12 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 
 lib_LTLIBRARIES = libbeecrypt.la
 
-libbeecrypt_la_SOURCES = aes.c base64.c beecrypt.c blockmode.c blockpad.c blowfish.c dhies.c dldp.c dlkp.c dlpk.c dlsvdp-dh.c dsa.c elgamal.c endianness.c entropy.c fips186.c hmac.c hmacmd5.c hmacsha1.c hmacsha224.c hmacsha256.c md4.c md5.c hmacsha384.c hmacsha512.c memchunk.c mp.c mpbarrett.c mpnumber.c mpprime.c mtprng.c pkcs1.c pkcs12.c ripemd128.c ripemd160.c ripemd256.c ripemd320.c rsa.c rsakp.c rsapk.c sha1.c sha224.c sha256.c sha384.c sha512.c sha2k32.c sha2k64.c timestamp.c cppglue.cxx
+libbeecrypt_la_SOURCES = aes.c base64.c beecrypt.c b&lt;/pre&gt;</description>
    <dc:creator>Peter Korsgaard</dc:creator>
    <dc:date>2011-12-14T22:42:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/106">
    <title>ppc32 TEXTREL fix for binutils-2.22</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/106</link>
    <description>&lt;pre&gt;for anyone who targets powerpc, you'll want to make sure to have this fix from 
upstream when using binutils-2.22
-mike
&lt;/pre&gt;</description>
    <dc:creator>Mike Frysinger</dc:creator>
    <dc:date>2011-12-03T01:58:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/98">
    <title>[RFC/PATCH 0/3 v2] fc-cache --root support</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/98</link>
    <description>&lt;pre&gt;The point of these patchsets is to add a --root flag to fc-cache so that
people can build up the font cache in a tree other than /.  This is useful
to people cross-compiling, and for non-root building (chroot won't work).

This ignores the cache file format issue (that's a later patchset).

Mike Frysinger (3):
  FcStrPathPlus: new helper function
  FcStat: export for people to use
  fc-cache: add a --root option

 fc-cache/fc-cache.c     |   59 ++++++++++++++++++++++++++++------------------
 fc-cache/fc-cache.sgml  |   11 ++++++++-
 fontconfig/fontconfig.h |   15 ++++++++++++
 src/fccache.c           |   40 ++++++++++++++++++++++++++++---
 src/fccfg.c             |   59 +++++++++++++++++++++++------------------------
 src/fcdir.c             |   13 ++++++++-
 src/fcfreetype.c        |   10 +++++++-
 src/fcint.h             |    2 +
 src/fcstr.c             |   51 ++++++++++++++++++++++++++++++++++++++++
 src/fcxml.c             |   22 ++++++++++++++++-
 10 files changed, 219 insertions(+), 63 deletions(-)

&lt;/pre&gt;</description>
    <dc:creator>Mike Frysinger</dc:creator>
    <dc:date>2011-11-08T05:24:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/94">
    <title>Adding an "easy" and "wip" patch stack</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/94</link>
    <description>&lt;pre&gt;Hi,

A next step we have agreed on is to add two example patch stacks, to
learn about the workflow:

1) an "easy" patch stack where we can quickly agree on
2) a more complicated one, which definitely needs some work.

Suggestions?

rsc

PS: The VM makes progress, but unfortunately we had some hardware issues
    with new RAM on the host server. Our administration team is working
    on this. However, it shouldn't slow down the progress, as we can use
    my git tree posted some days ago in the meantime.
&lt;/pre&gt;</description>
    <dc:creator>Robert Schwebel</dc:creator>
    <dc:date>2011-11-07T08:45:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/77">
    <title>Temporary git repo</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/77</link>
    <description>&lt;pre&gt;Hi,

In order to share the README, I've setup a temporary repository here:
http://git.pengutronix.de/?p=rsc/send-patches-org.git;a=summary

It will move to git.send-patches.org when the machine was set up.

rsc
&lt;/pre&gt;</description>
    <dc:creator>Robert Schwebel</dc:creator>
    <dc:date>2011-11-01T08:07:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/68">
    <title>Proposal for send-patches.org patch repository</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/68</link>
    <description>&lt;pre&gt;About the send-patches.org Patch Repository
-------------------------------------------

This repository contains patches for other open source projects which
are necessary to make them more cross-compiling friendly. The cross
build community has a long history of carrying patches arround, but
trust us - we do all hate them :-)

Help us make the upstream better and create more awareness for cross
compile issues!

- The send-patches.org team


Patch Guidelines
----------------

The following checklist should make it easier for you to find out if a
patch contains all necessary information:

[ ] Is the patch documented using the Linux kernel's "canonical patch"
    format [1]?

[ ] The patch must contain a subject line (like an email subject),
    stating clearly what the patch does. Example:

    makefile: fix cross compile issues

[ ] Check if the subject line is descriptive enough to understand the
    patch, even if you wouldn't already know what it does :) Add a
    descriptive text to the body if the subj&lt;/pre&gt;</description>
    <dc:creator>Robert Schwebel</dc:creator>
    <dc:date>2011-10-31T19:24:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/66">
    <title>Where I found a path for a M-501 Board?</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/66</link>
    <description>&lt;pre&gt;
I have a little problem when i try to update my kernel version.
I have a M501 evaluation board kit:
CPU: ATMEL AT91RM9200, with MMU
Clock: 180MHz
SDRAM: 32MB (16MB user space)
Flash: 16MB (12MB user space)
USB Host: x2, USB 2.0 compliant

In this moment, I have 2.6.14-M5 version (it's very old, I Know) and I
need to upgrade it because I can't do to work a webcam on this board.

I tried update many times the linux's kernel and different versions of
kernels  (2.6.18, 2.6.20, 2.6.22, 2.6.24....2.6.38 ) and basically I
can't do it for these reasons:

1) the toolchains is very old (3.3.2 version). I download different
versions of ARM's toolchains (like code sourcery lite version
http://www.codesourcery.com/sgpp/lite/arm  and others more), this
toolchains isn't working for my embedded system.  I wrote to
Artila's support and they wrote to me: "this is the last toolchain for
your board, you must to use them"

2) On Artila's web-site, the "last kernel version" is 2.6.14-M5 kernel
version update to 2010. 

If you ha&lt;/pre&gt;</description>
    <dc:creator>Jorge Yesid Rios Ortiz</dc:creator>
    <dc:date>2011-06-30T16:56:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/65">
    <title>[PATCH] xf86-input-tslib: add support for Xorg Input ABI12</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/65</link>
    <description>&lt;pre&gt;Hello,

  Frederic Wagner has written initial patch for adding support to
xf86-input-tslib for Xorg Input ABI 12.

  I have reworked the attached patch to apply against xf86-input-tslib
SVN r48.

  Is it OK to commit?

Kind regards,
&lt;/pre&gt;</description>
    <dc:creator>Hector Oron</dc:creator>
    <dc:date>2011-06-06T23:59:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/56">
    <title>[PATCH] Make docbook2man optional</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/56</link>
    <description>&lt;pre&gt;module-init-tools build currently fails if docbook2man is not
available on the build system. However, since docbook2man is only used
to build the documentation, it is not strictly necessary, and there
are cases (embedded Linux build systems) where it's really useful to
not have to build things such as docbook2man.

This patch has been present in Buildroot for quite some time
now :

 http://git.buildroot.net/buildroot/tree/package/module-init-tools/module-init-tools-3.11-add-manpages-config-option.patch

OpenEmbedded has a different hack to disable the build of
module-init-tools manpages:

 http://git.openembedded.org/cgit.cgi/openembedded/tree/recipes/module-init-tools/files/no_man_rebuild

PTXdist has yet another different hack to also disable the build of
module-init-tools manpages:

 http://git.pengutronix.de/?p=ptxdist.git;a=blob;f=rules/module-init-tools.make;h=0af89157a0bec221bf44e44a8e66f9be5c23190f;hb=HEAD#l41

The fix consists in adding an automake conditional variable
HAVE_DOCBOOKTOMAN, which is de&lt;/pre&gt;</description>
    <dc:creator>Thomas Petazzoni</dc:creator>
    <dc:date>2011-01-07T17:01:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/51">
    <title>Current state of things</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/51</link>
    <description>&lt;pre&gt;Hi,

I just want to ask, what is the current state of things? Is there
already some collaboration process defined? Is there something already
going on? I was just thinking that it might make sense to extend
collaboration even to non-embedded distributions...

---
   Michal Hrusecky &amp;lt;Michal.Hrusecky-stAJ6ESoqRxg9hUCZPvPmw&amp;lt; at &amp;gt;public.gmane.org&amp;gt;

&lt;/pre&gt;</description>
    <dc:creator>Michal Hrušecký</dc:creator>
    <dc:date>2010-12-25T19:56:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/47">
    <title>[PATCH] add support for LDFLAGS, don't overwrite CFLAGS</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/47</link>
    <description>&lt;pre&gt;When cross compiling the linker can not find libz, this patch
adds the LDFLAGS variable to pass the linkerflags.

Based on earier work by Erwin Rol.

Signed-off-by: Marc Kleine-Budde &amp;lt;mkl-bIcnvbaLZ9MEGnE8C9+IrQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
Signed-off-by: Wolfram Sang &amp;lt;w.sang-bIcnvbaLZ9MEGnE8C9+IrQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
---
 squashfs-tools/Makefile |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/squashfs-tools/Makefile b/squashfs-tools/Makefile
index f45d722..3a649ff 100644
--- a/squashfs-tools/Makefile
+++ b/squashfs-tools/Makefile
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -100,7 +100,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; MKSQUASHFS_OBJS = mksquashfs.o read_fs.o sort.o swap.o pseudo.o compressor.o
 UNSQUASHFS_OBJS = unsquashfs.o unsquash-1.o unsquash-2.o unsquash-3.o \
 unsquash-4.o swap.o compressor.o
 
-CFLAGS = $(INCLUDEDIR) -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE \
+CFLAGS += $(INCLUDEDIR) -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE \
 -D_GNU_SOURCE -DCOMP_DEFAULT=\"$(COMP_DEFAULT)\"  -O2 -Wall
 
 LIBS =
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -196,7 +196,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; endif
 all: mksquashfs unsquashf&lt;/pre&gt;</description>
    <dc:creator>Wolfram Sang</dc:creator>
    <dc:date>2010-11-29T14:05:04</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/46">
    <title>New tslib might be coming...</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/46</link>
    <description>&lt;pre&gt;Hiya,

in case you didn't notice: tslib has an active upstream again and a new release
1.1 might be due soon. So, it is probably a good time to check your local
patch-stacks and clean it up :)

Regards,

   Wolfram

PS: more information here:
https://lists.berlios.de/pipermail/tslib-general/2010-November/thread.html

&lt;/pre&gt;</description>
    <dc:creator>Wolfram Sang</dc:creator>
    <dc:date>2010-11-14T11:48:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/45">
    <title>[PATCH] fix build with --disable-crypto</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/45</link>
    <description>&lt;pre&gt;options.c is missing the definition for struct context when built with
--disable-crypto, as it then doesn't get pulled in through push.h,
leading to build errors like:

options.c: In function ‘parse_http_proxy_fallback’:
options.c:1474: error: dereferencing pointer to incomplete type
options.c:1477: error: dereferencing pointer to incomplete type
options.c:1478: error: dereferencing pointer to incomplete type

Fix it by including forward.h

Signed-off-by: Peter Korsgaard &amp;lt;jacmet&amp;lt; at &amp;gt;sunsite.dk&amp;gt;
---
 options.c |    1 +
 1 file changed, 1 insertion(+)

Index: openvpn-2.1.3/options.c
===================================================================
--- openvpn-2.1.3.orig/options.c
+++ openvpn-2.1.3/options.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -29,6 +29,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 
 #include "syshead.h"
 
+#include "forward.h"
 #include "buffer.h"
 #include "error.h"
 #include "common.h"

&lt;/pre&gt;</description>
    <dc:creator>Peter Korsgaard</dc:creator>
    <dc:date>2010-09-23T20:09:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/40">
    <title>"patch dragging" vs git</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/40</link>
    <description>&lt;pre&gt;I have a question about how you would use git to do what I call "patch
dragging".  Maybe there's a better term for it, but what I mean is when a new
third-party package is released, I look at the patches I have in the previous
version's patch dir, and "drag" only the appropriate patches to the new version's
patch dir.

The dragging process is usually very quick because the patches are small text
files.  In most cases, even though my patches have been sent to the third-party,
they have not been integrated, and dragging them forward to the new version
requires very little manual tweaking.

My question is how would you use git to accomplish this task.  I realize that
this is a merge operation, but I am only a novice git user, and I can not
visualize the workflow.

As an example, let's say I have thirdparty_package-1.1.tar.gz, and a directory
of patches that looks like this:

  thirdparty_package-1.1/functionality1/001_foo.patch
  thirdparty_package-1.1/functionality1/002_foo.patch
  thirdparty_package-1.1/bugfi&lt;/pre&gt;</description>
    <dc:creator>David Wuertele</dc:creator>
    <dc:date>2010-06-25T17:35:31</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/33">
    <title>[PATCH] teach ncurses-config about sysroot</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/33</link>
    <description>&lt;pre&gt;From: Marc Kleine-Budde &amp;lt;mkl-bIcnvbaLZ9MEGnE8C9+IrQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt;

This patch teaches ncursrs-config about sysroot

Signed-off-by: Marc Kleine-Buddde &amp;lt;mkl-bIcnvbaLZ9MEGnE8C9+IrQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
Signed-off-by: Robert Schwebel &amp;lt;rsc-bIcnvbaLZ9MEGnE8C9+IrQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt;

---
 misc/ncurses-config.in |    8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

Index: ncurses-5.7/misc/ncurses-config.in
===================================================================
--- ncurses-5.7.orig/misc/ncurses-config.in
+++ ncurses-5.7/misc/ncurses-config.in
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -75,11 +75,11 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; while test $# -gt 0; do
 # compile/link
 --cflags)
 INCS=
-if test "${prefix}/include" != /usr/include ; then
-INCS="-I${prefix}/include"
+if test "${SYSROOT}${prefix}/include" != /usr/include ; then
+INCS="-I${SYSROOT}${prefix}/include"
 fi
 if test "&amp;lt; at &amp;gt;WITH_OVERWRITE&amp;lt; at &amp;gt;" != no ; then
-INCS="$INCS -I${prefix}/include/${THIS}"
+INCS="$INCS -I${SYSROOT}${prefix}/include/${THIS}"
 fi
 sed -e 's,^[ ]*,,' -e 's, [ &lt;/pre&gt;</description>
    <dc:creator>Robert Schwebel</dc:creator>
    <dc:date>2010-06-24T12:37:31</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/14">
    <title>Is this ml appropriate for announcing new cross-compilerbuild systems?</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/14</link>
    <description>&lt;pre&gt;Howdy, just came across this ml.  Are build systems besides buildroot and ptx
welcome here?

I have a make-based system that I'm developing, which I named "Crossplex".
It is quite mature for mips and intel architectures, and it can build toolchains
and targets using glibc and uClibc.

I would love for Crossplex to join the party if it is welcome.
The website is crossplex.org.

Dave



_______________________________________________
crossdev mailing list

&lt;/pre&gt;</description>
    <dc:creator>David Wuertele</dc:creator>
    <dc:date>2010-06-14T19:04:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/13">
    <title>FYI: paper on oss-qm project</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/13</link>
    <description>&lt;pre&gt;Hi folks,

i've written a little paper on the oss-qm project, which aims to
offload common QM works from invidual distros to an common place:

http://www.metux.de/download/oss-qm-project-2010050101.pdf

cu
&lt;/pre&gt;</description>
    <dc:creator>Enrico Weigelt</dc:creator>
    <dc:date>2010-05-08T17:16:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/11">
    <title>FOSDEM slides online</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/11</link>
    <description>&lt;pre&gt;Hi,

the FOSDEM slides are now online:
http://www.send-patches.org/news/index.html

Thanks again to all participants!

Robert
&lt;/pre&gt;</description>
    <dc:creator>Robert Schwebel</dc:creator>
    <dc:date>2010-02-11T11:50:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.embedded.crossdev/8">
    <title>A couple of comments after Fosdem and OpenWrt repositoryadding</title>
    <link>http://comments.gmane.org/gmane.comp.embedded.crossdev/8</link>
    <description>&lt;pre&gt;Hi,

Following our "Cross-build systems" meeting at Fosdem, I just subscribed to 
this list. I first got a couple of comments:

- the welcome message of the mailing-list is in German, might be worth 
translating it to english for non-german speakers

- can you please reference the OpenWrt packages repository [1] to the "Patch 
repositories" page?

We should probably setup a common patch repository which could be easily used 
by all of our projects as a reference. For instance one might have the 
following structure to let our projects directly checkout patches from the 
send-patches.org repository:

/packages/
/foo/&amp;lt;version 1&amp;gt;/bar.patch
/foo/&amp;lt;version 2&amp;gt;/foo.patch
/bar/&amp;lt;version 1&amp;gt;....
/toolchain/
/gcc/4.4.1/blah.patch

... and whatever you feel is suitable to be shared.

We proposed at Fosdem that we could have two teams of people at send-
patches.org to perform the following actions:

- one team which checks in the patches they maintain in a cross-build project 
to the send-patches.org repository
- anoth&lt;/pre&gt;</description>
    <dc:creator>Florian Fainelli</dc:creator>
    <dc:date>2010-02-09T12:19:00</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.embedded.crossdev">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.embedded.crossdev</link>
  </textinput>
</rdf:RDF>

