From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] add libfcgi to buildroot it will have compiling errors as long as -lm isnt added to the buildsystem of libfcgi
Date: Wed, 28 Sep 2011 17:49:58 +0200 [thread overview]
Message-ID: <20110928174958.2a4f433c@skate> (raw)
In-Reply-To: <000001cc7def$9ff6a920$dfe3fb60$@com>
Hello,
Le Wed, 28 Sep 2011 17:02:21 +0200,
"Rico Bachmann" <bachmann@tofwerk.com> a ?crit :
> that wasn't planed ^^ i didn't know that all my comments get i to the subject.
> next time i will use the blank line. Did i have to commit the patch a second time, because of the long subject?
You can simply do a :
git commit --amend
to modify the commit message of the topmost commit.
> i have 2 patches that fix that problem, but i don't know how to add patches to buildroot for files that are created in the build/fcgi-2.4.0/ when fcgi-2.4.0.tar.gz is unpacked
>
> http://lists.busybox.net/pipermail/buildroot/2011-September/046084.html
>
> in this link you can see the patches for 2 makefiles (they're attached to the mail). It is the solution to the -lm problem, but i don't know how to add that to buildroot.
Simply add them in package/fcgi/, under a name like
fcgi-2.4.0-some-useful-description.patch.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-09-28 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <add fcgi-2.4.0 package to buildroot>
2011-09-28 14:13 ` [Buildroot] [PATCH] add libfcgi to buildroot it will have compiling errors as long as -lm isnt added to the buildsystem of libfcgi Rico Bachmann
2011-09-28 14:30 ` Thomas Petazzoni
2011-09-28 15:02 ` Rico Bachmann
2011-09-28 15:49 ` Thomas Petazzoni [this message]
2011-09-28 15:52 ` 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=20110928174958.2a4f433c@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