From: Michael Burghart <mb@michaelburghart.de>
To: buildroot@busybox.net
Subject: [Buildroot] Compiling Apache
Date: Tue, 22 Mar 2011 17:07:19 +0100 [thread overview]
Message-ID: <4D88C937.2010902@michaelburghart.de> (raw)
In-Reply-To: <4D88C6B3.5010103@free.fr>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Am 22.03.2011 16:56, schrieb Eric BENARD:
> Hi,
>
> please keep list in copy when answering,
sorry. Yes, I will.
>
>> Am 22.03.2011 15:59, schrieb Eric BENARD:
>>
>>> http://cgit.openembedded.net/cgit.cgi/openembedded/tree/recipes/apache2/apache2_2.2.17.bb
>>>
>>> http://cgit.openembedded.net/cgit.cgi/openembedded/tree/recipes/libpcre/libpcre_8.10.bb
>>>
>>> http://cgit.openembedded.net/cgit.cgi/openembedded/tree/recipes/apr/apr_1.4.2.bb
>>>
>>> http://cgit.openembedded.net/cgit.cgi/openembedded/tree/recipes/apr/apr-util_1.3.10.bb
>>>
>>
>> thanks for your info. Seems pretty weird and more complex than I
>> thought. But how do you integrate those rules into buildroot? I only saw
>> the "standard" autoconf and cmake Makefiles.in the documentation..
>>
> well for that part you will need to ask on the mailing list.
does any on this list know how to implement Eric's knowledge on Apache
into an .mk file? Or does anybody already have a .mk file to share? Or
am I the only guy who wants to cross compile an Apache? :)
- --
- --
cheers
- -micha-
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJNiMk2AAoJEEMkp/gkis19u+EH/3MuAQCNXG2Dz6+5OnBja5+M
BDx/OuQjfkSKyNN019PDf+ua/2oWe4OZJ7MiI/VaR/i5UFNCxoKAT+aRMpFR2PZf
Pp3BmMBfpHpJLZRHoOjWsgr2pkU4mugD17aV/nRHdPXVt1XavLbue4pUwvXb/9t8
EA9tryKHJ2L/u0ax1hLJZB5jAku2u1LaO7sY6kOGrKOVGi678QnMpQ7t610RCsiX
R/vHnSzl3Uy+aqWWbpWK508snYyd/w9tnoEU8A6LJZNGoDFswbxPzS/XciRdwltG
HteI9ut+R5UmiAJmdmJ4iV+D+0EQa6839celXJ4YPahyNSMtjaxo653huwgDCE8=
=vwSS
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-03-22 16:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 21:39 [Buildroot] Compiling Apache Michael Burghart
2011-03-22 14:59 ` Eric BENARD
[not found] ` <4D88BD19.7070901@michaelburghart.de>
[not found] ` <4D88C6B3.5010103@free.fr>
2011-03-22 16:07 ` Michael Burghart [this message]
2011-03-22 19:33 ` Michael Burghart
2011-03-22 19:55 ` Baruch Siach
2011-03-22 20:00 ` Michael Burghart
2011-03-22 20:03 ` Baruch Siach
2011-03-22 20:21 ` Michael Burghart
2011-03-23 6:12 ` Michael Burghart
2011-03-23 17:16 ` Baruch Siach
2011-03-23 19:02 ` [Buildroot] proc not mouning Heyendal, Carl
2011-03-23 19:27 ` bruce bushby
2011-03-23 19:32 ` ANDY KENNEDY
2011-03-23 19:35 ` Heyendal, Carl
2011-03-23 19:43 ` ANDY KENNEDY
2011-03-23 19:46 ` Heyendal, Carl
2011-03-23 19:36 ` bruce bushby
2011-03-23 20:35 ` Heyendal, Carl
2011-03-23 21:14 ` ANDY KENNEDY
2011-03-24 18:58 ` Thomas Petazzoni
2011-03-24 19:04 ` Heyendal, Carl
2011-10-21 16:29 ` vbr vbr
2011-10-28 12:50 ` Peter Korsgaard
2011-03-24 6:42 ` [Buildroot] Compiling Apache Michael Burghart
2011-03-22 19:35 ` Michael Burghart
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=4D88C937.2010902@michaelburghart.de \
--to=mb@michaelburghart.de \
--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