Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: andersen at uclibc.org <andersen@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/fontconfig
Date: Sat,  3 Feb 2007 12:52:34 -0800 (PST)	[thread overview]
Message-ID: <20070203205234.6E42B48629@busybox.net> (raw)

Author: andersen
Date: 2007-02-03 12:52:33 -0800 (Sat, 03 Feb 2007)
New Revision: 17743

Log:
grumble grumble.  fontconfig's fc-lang is broken upstream and
doesn't understand how to deal with trailing whitespace...  So
I had to whip up this patch to bludgeon it into submission.


Added:
   trunk/buildroot/package/fontconfig/fc-lang.patch


Changeset:
Added: trunk/buildroot/package/fontconfig/fc-lang.patch
===================================================================
--- trunk/buildroot/package/fontconfig/fc-lang.patch	                        (rev 0)
+++ trunk/buildroot/package/fontconfig/fc-lang.patch	2007-02-03 20:52:33 UTC (rev 17743)
@@ -0,0 +1,51 @@
+--- /tmp/Makefile.am	2006-04-25 15:47:49.313035880 +0200
++++ fontconfig-2.3.94/fc-lang/Makefile.am	2006-04-25 15:48:22.807943880 +0200
+@@ -31,6 +31,7 @@
+ TMPL=fclang.tmpl.h
+ STMPL=${top_srcdir}/fc-lang/fclang.tmpl.h
+ TARG=fclang.h
++FC_LANG=./fc-lang
+ 
+ noinst_PROGRAMS=fc-lang
+ 
+@@ -44,6 +45,6 @@
+ 
+ $(TARG):$(ORTH) fc-lang${EXEEXT} $(STMPL)
+ 	rm -f $(TARG)
+-	./fc-lang${EXEEXT} -d ${srcdir} $(ORTH) < $(STMPL) > $(TARG)
++	$(FC_LANG)${EXEEXT} -d ${srcdir} $(ORTH) < $(STMPL) > $(TARG)
+ 
+ CLEANFILES=$(TARG)
+--- fontconfig-2.4.2/fc-lang/fc-lang.orig.c	2007-02-03 13:39:49.000000000 -0700
++++ fontconfig-2.4.2/fc-lang/fc-lang.c	2007-02-03 13:46:08.000000000 -0700
+@@ -116,6 +116,20 @@
+     return f;
+ }
+ 
++char* trim(char *s)
++{
++	int len = strlen(s);
++
++	/* nuke trailing whitespace */
++	while (len > 0 && (isspace(s[len - 1]) || s[len - 1]=='\n'))
++		s[--len] = '\0';
++
++	/* skip leading whitespace */
++	s += strspn(s, " \n\r\t\v");
++
++	return s;
++}
++
+ /*
+  * build a single charset from a source file
+  *
+@@ -142,8 +156,7 @@
+             if (!file)
+                 fatal (line, lineno, 
+                        "invalid syntax, expected: include filename");
+-	    while (isspace(*file))
+-		file++;
++	    file = trim(file);
+ 	    f = scanopen (file);
+ 	    if (!f)
+ 		fatal (file, 0, "can't open");

             reply	other threads:[~2007-02-03 20:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-03 20:52 andersen at uclibc.org [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-01-10 13:47 [Buildroot] svn commit: trunk/buildroot/package/fontconfig thomasez at uclibc.org
2008-12-22 22:10 jacmet at uclibc.org
2008-11-11 19:38 tpetazzoni at uclibc.org
2008-09-14 19:35 jacmet at uclibc.org
2008-08-16 19:13 jacmet at uclibc.org
2008-06-26 14:04 jacmet at uclibc.org
2008-05-01 19:01 ninevoltz at uclibc.org
2008-03-06 18:09 ninevoltz at uclibc.org
2007-08-12 12:06 ulf at uclibc.org
2007-08-10 14:44 ulf at uclibc.org
2007-07-23  8:18 ulf at uclibc.org
2007-06-28 14:03 aldot at uclibc.org
2007-05-24  8:41 jacmet at uclibc.org
2007-05-22 10:31 jacmet at uclibc.org
2007-01-29 12:59 aldot at uclibc.org
2007-01-16 16:06 aldot at uclibc.org
2007-01-16  8:10 andersen at uclibc.org
2007-01-15 21:26 andersen 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=20070203205234.6E42B48629@busybox.net \
    --to=andersen@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