Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: ulf at uclibc.org <ulf@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/libcgicc
Date: Wed, 21 Jan 2009 00:21:46 +0000 (UTC)	[thread overview]
Message-ID: <20090121002146.562C8775DB@busybox.osuosl.org> (raw)

Author: ulf
Date: 2009-01-21 00:21:43 +0000 (Wed, 21 Jan 2009)
New Revision: 24932

Log:
include string.h when building cgicc, add libcgicc-unpacked, and clean up libcgicc.mk - still does not build OK

Added:
   trunk/buildroot/package/libcgicc/cgicc-3.2.7-memset.patch

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


Changeset:
Added: trunk/buildroot/package/libcgicc/cgicc-3.2.7-memset.patch
===================================================================
--- trunk/buildroot/package/libcgicc/cgicc-3.2.7-memset.patch	                        (rev 0)
+++ trunk/buildroot/package/libcgicc/cgicc-3.2.7-memset.patch	2009-01-21 00:21:43 UTC (rev 24932)
@@ -0,0 +1,12 @@
+diff -urN cgicc-3.2.7-0rig//demo/dns.cpp cgicc-3.2.7/demo/dns.cpp
+--- cgicc-3.2.7-0rig//demo/dns.cpp	2009-01-21 00:24:13.000000000 +0100
++++ cgicc-3.2.7/demo/dns.cpp	2009-01-21 00:24:30.000000000 +0100
+@@ -34,6 +34,7 @@
+ #include <vector>
+ #include <stdexcept>
+ #include <iostream>
++#include <string.h>
+ 
+ #include "cgicc/CgiDefs.h"
+ #include "cgicc/Cgicc.h"
+

Modified: trunk/buildroot/package/libcgicc/libcgicc.mk
===================================================================
--- trunk/buildroot/package/libcgicc/libcgicc.mk	2009-01-21 00:17:03 UTC (rev 24931)
+++ trunk/buildroot/package/libcgicc/libcgicc.mk	2009-01-21 00:21:43 UTC (rev 24932)
@@ -17,7 +17,8 @@
 
 $(LIBCGICC_DIR)/.unpacked: $(DL_DIR)/$(LIBCGICC_SOURCE)
 	$(LIBCGICC_CAT) $(DL_DIR)/$(LIBCGICC_SOURCE) | tar -C $(BUILD_DIR) $(TAR_OPTIONS) -
-	touch $(LIBCGICC_DIR)/.unpacked
+	toolchain/patch-kernel.sh $(LIBCGICC_DIR) package/libcgicc cgicc\*.patch
+	touch $@
 
 $(LIBCGICC_DIR)/.configured: $(LIBCGICC_DIR)/.unpacked
 	(cd $(LIBCGICC_DIR); rm -f config.cache; \
@@ -40,11 +41,11 @@
 		--mandir=/usr/man \
 		--infodir=/usr/info \
 	)
-	touch $(LIBCGICC_DIR)/.configured
+	touch $@
 
 $(LIBCGICC_DIR)/.compiled: $(LIBCGICC_DIR)/.configured
 	$(MAKE) -C $(LIBCGICC_DIR)
-	touch $(LIBCGICC_DIR)/.compiled
+	touch $@
 
 $(STAGING_DIR)/lib/libcgicc.so: $(LIBCGICC_DIR)/.compiled
 	$(MAKE) DESTDIR=$(STAGING_DIR) -C $(LIBCGICC_DIR) install
@@ -55,6 +56,8 @@
 
 libcgicc: uclibc $(TARGET_DIR)/usr/lib/libcgicc.so
 
+libcgicc-unpacked: $(LIBCGICC_DIR)/.unpacked
+
 libcgicc-clean:
 		-$(MAKE) -C $(LIBCGICC_DIR) clean
 

             reply	other threads:[~2009-01-21  0:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21  0:21 ulf at uclibc.org [this message]
2009-01-21  6:21 ` [Buildroot] svn commit: trunk/buildroot/package/libcgicc Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2009-01-26 19:41 jacmet at uclibc.org
2009-01-26 19:41 jacmet at uclibc.org
2009-01-26 19:14 jacmet at uclibc.org
2009-01-21  0:27 ulf at uclibc.org
2009-01-21  6:22 ` Peter Korsgaard
2009-01-26 15:43   ` Peter Korsgaard
2009-01-26 19:03     ` Ulf Samuelsson
2009-01-26 20:10       ` Peter Korsgaard
2009-01-13 18:42 ulf at uclibc.org
2007-07-17 12:01 ulf 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=20090121002146.562C8775DB@busybox.osuosl.org \
    --to=ulf@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