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 14:16:23 +0200 [thread overview]
Message-ID: <op.v2ipplkh705kjs@rico> (raw)
In-Reply-To: 201109280633.52172.minimod@morethan.org
Am 28.09.2011, 13:33 Uhr, schrieb Michael S. Zick
<minimod@morethan.org>:
> On Wed September 28 2011, Rico Bachmann wrote:
>> Am 28.09.2011, 13:03 Uhr, schrieb Michael S. Zick
>> <minimod@morethan.org>:
>>
>> > On Wed September 28 2011, Rico Bachmann wrote:
>> >> 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.
>> >>
>> >
>> > You might want to check the contents of the patch files attached
>> > to your post. ;-)
>> >
>> > Unless you intended to send two, one-line, patches -
>> > something is missing from each.
>> >
>> > Mike
>>
>> I created the patches with this command:
>>
>> diff -u path/originalfile path/newfile > mypatch.patch
>>
>> there should be everything needed in the file content.
>> at least they're working fine for me, i can use the patches wih this
>> command:
>>
>> patch p0 -i mypatch.patch
>>
>> and it is only one-line per patch i have to change.
>> It's the missing link to the math library by the LDFLAGS which wasn't
>> set.
>>
>
> My bad, I thought the patches where the topic line of this thread.
>
> Thread topic reads: "add fcgi-2.4.0 package..."
> Not: "correct fcgi-2.4.0 package..."
>
> I will have to re-read the topic thread to see where it got hijacked.
>
> Mike
If I manage my two patches to automatically run from buildroot
I can create and upload a patchfile which add the hole package.
But at this moment i don't really know how to do that. Because I
am new to the buildroot developing.
>> Rico
>>
>> >>
>> >> 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
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>>
>>
--
Erstellt mit Operas revolution?rem E-Mail-Modul: http://www.opera.com/mail/
next prev parent reply other threads:[~2011-09-28 12:16 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
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 [this message]
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.v2ipplkh705kjs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.