From: Rico Bachmann <bachmann@tofwerk.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] add libfcgi to buildroot
Date: Tue, 11 Oct 2011 16:29:42 +0200 [thread overview]
Message-ID: <op.v26yjsdz705kjs@rico> (raw)
In-Reply-To: 201110012259.10267.arnout@mind.be
Am 01.10.2011, 22:59 Uhr, schrieb Arnout Vandecappelle
<arnout@mind.be>:
> 3. Create the patch relative to the build directory:
> cd output/build
> diff -rup fcgi-2.4.0.orig fcgi-2.4.0 > \
> ../../package/fcgi/fcgi-2.4.0-add-lm.patch
>
When I try to create my patch with this command I got a fault, file or
folder not found, when I
delete the backslash after the '>' it works fine. But my patch still have
no effect if i try to build the
package with buildroot and use the patch automatically.
If I use my patch manual it works fine:
commands:
cd /buildroot/output/build
patch -p0 < ../../package/fcgi/fcgi-2.4.0-add-lm.patch
output:
patching file fcgi-2.4.0/cgi-fcgi/Makefile.in
patching file fcgi-2.4.0/examples/Makefile.in
After that I can build the package (of course only without a make
fcgi-dirclean)
Here is the output form buildroot while using the patch:
>>> fcgi 2.4.0 Patching packages/fcgi
for file in config.guess config.cub; do for i $(find
/buildroot/output/build/fcgi-2.4.0 -name $file);
do cp package/gnuconfig/$file $i;
done; done
After that, the build still failed.
next prev parent reply other threads:[~2011-10-11 14:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <add libfcgi to buildroot>
2011-09-29 8:45 ` [Buildroot] [PATCH 2/2] add libfcgi to buildroot Rico Bachmann
2011-09-29 9:58 ` Thomas Petazzoni
2011-10-01 20:59 ` Arnout Vandecappelle
2011-10-06 6:53 ` Rico Bachmann
2011-10-11 14:29 ` Rico Bachmann [this message]
2011-10-11 16:06 ` Arnout Vandecappelle
2011-10-12 10:12 ` Rico Bachmann
2011-10-13 22:33 ` Arnout Vandecappelle
2011-10-13 22:46 ` [Buildroot] [PATCH] package: add libfcgi fast cgi library Arnout Vandecappelle
2011-10-14 6:35 ` Thomas Petazzoni
2011-10-14 7:59 ` [Buildroot] [PATCH v2] " Arnout Vandecappelle
2011-10-14 9:08 ` Thomas Petazzoni
2011-10-14 9:16 ` [Buildroot] [PATCH v3] " Arnout Vandecappelle
2012-04-25 10:24 ` Rico Bachmann
2012-04-27 21:11 ` Arnout Vandecappelle
2012-04-29 18:37 ` Peter Korsgaard
2012-04-30 14:13 ` Rico Bachmann
2012-04-30 14:23 ` Rico Bachmann
2012-04-30 15:48 ` Rico Bachmann
2012-04-30 17:11 ` Peter Korsgaard
2012-05-01 8:40 ` Rico Bachmann
2011-09-29 9:30 ` [Buildroot] [PATCH 2/2] add libfcgi to buildroot Rico Bachmann
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=op.v26yjsdz705kjs@rico \
--to=bachmann@tofwerk.com \
--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