Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] add libfcgi to buildroot
Date: Thu, 29 Sep 2011 11:58:49 +0200	[thread overview]
Message-ID: <20110929115849.73cbefaa@skate> (raw)
In-Reply-To: <1317285917-2134-1-git-send-email-bachmann@tofwerk.com>

Le Thu, 29 Sep 2011 10:45:17 +0200,
Rico Bachmann <bachmann@tofwerk.com> a ?crit :

> added the patches, still not working
> could be a problem with the filepath in the patch?

I'm sorry to say so, but: please read my e-mails. I said:

"""
Simply add them in package/fcgi/, under a name like
fcgi-2.4.0-some-useful-description.patch.
"""

So link_math_cgifcgi.patch should be fcgi-2.0.4-link_math_cgifcgi.patch
if you want the patch to be applied.

Also, here you have only sent PATCH 2/2, and this patch should be
merged into the previous one to create a single patch that adds the
package and its associated patches. To do so, you can do:

 git rebase -i master

When the editor pops up, on the second line that corresponds to the
second commit, replace "pick" by "fixup", and exit your editor. This
will instruct git to merge your second commit into your first commit.

Also:

 * Your two patches link_math_cgifcgi.patch and link_math_example.patch
   should be just one patch.

 * This patch should have a description and a Signed-off-by line.

 * Patching the Makefiles in an autotools-based package is really
   wrong, it's the Makefile.am that should be patched. I think your
   LDFLAGS = -lm is more a workaround than a correct fix.

Regards,

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

  reply	other threads:[~2011-09-29  9:58 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 [this message]
2011-10-01 20:59     ` Arnout Vandecappelle
2011-10-06  6:53       ` Rico Bachmann
2011-10-11 14:29       ` Rico Bachmann
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=20110929115849.73cbefaa@skate \
    --to=thomas.petazzoni@free-electrons.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