Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rico Bachmann <bachmann@tofwerk.com>
To: buildroot@busybox.net
Subject: [Buildroot] add fcgi-2.4.0 package to buildroot
Date: Wed, 28 Sep 2011 12:18:51 +0200	[thread overview]
Message-ID: <op.v2ij9pax705kjs@rico> (raw)
In-Reply-To: op.v15jbakh705kjs@rico

Am 21.09.2011, 11:29 Uhr, schrieb Rico Bachmann  
<bachmann@tofwerk.com>:

> Am 19.09.2011, 22:46 Uhr, schrieb Thomas Petazzoni  
> <thomas.petazzoni@free-electrons.com>:
>>
>> Can you post a proper patch (sent with git send-email so that it
>> doesn't get screwed up by your e-mail client) so that we can test and
>> help you in fixing the problem?
>>
>> Thanks!
>>
>> Thomas
>
> As soon as I've done a proper patch, i will send it.
> But I could use a moment. I'm really a newbie in that section

Is there a good tutorial to use git send-email, at the moment i have a  
patch
that allows me to build my rootfs with the libfcgi.
I attached the patches without git send-email. I hope it's not totaly  
screwed up.

How can i use the patch automatically in buildroot?
it should patch the make files from the libfcgi package after extracting  
them from the tarball.
At the moment I run make, wait for the error, patch the files, run make  
again...
I think i have to add some commands in the libfcgi.mk file.

And should I commit my integration of libfcgi to the buildroot project?
Maybe there are other people that like to compile some fcgi applications  
directly on the embedded system.

Greez
Rico
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fcgiex.patch
Type: application/octet-stream
Size: 419 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110928/d83722e9/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fcgicf.patch
Type: application/octet-stream
Size: 393 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110928/d83722e9/attachment-0001.obj>

  reply	other threads:[~2011-09-28 10:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-16 15:33 [Buildroot] add fcgi-2.4.0 package to buildroot Rico Bachmann
2011-09-16 16:44 ` Thomas Petazzoni
2011-09-19 14:14   ` Rico Bachmann
2011-09-19 20:46     ` Thomas Petazzoni
2011-09-21  9:29       ` Rico Bachmann
2011-09-28 10:18         ` Rico Bachmann [this message]
2011-09-28 11:03           ` Michael S. Zick
2011-09-28 11:22             ` Rico Bachmann
2011-09-28 11:33               ` Michael S. Zick
2011-09-28 12:16                 ` Rico Bachmann
2011-09-28 12:16           ` Thomas Petazzoni
2011-09-28 13:36             ` Rico Bachmann
2011-09-28 13:55               ` Thomas Petazzoni

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.v2ij9pax705kjs@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