From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] need help adding apache to buildroot
Date: Wed, 16 Jan 2013 22:54:40 +0100 [thread overview]
Message-ID: <20130116225440.1d45f78c@skate> (raw)
In-Reply-To: <2DD0B9C711CDFC45A3A266C78966CE7F40E3A14E@G4W3291.americas.hpqcorp.net>
Dear Jenkins, Lee (ISS Houston),
On Wed, 16 Jan 2013 21:30:31 +0000, Jenkins, Lee (ISS Houston) wrote:
> I expected make to pick up the new package, but that's clearly not
> happening. What am I missing?
Gustavo gave the explanation for this.
I'm however going to add a few more comments below, as I hope you'll be
submitting this package to Buildroot once it works.
> ----- buildroot/package/apache/Config.in -----
>
> config BR2_PACKAGE_APACHE
> bool "apache"
> help
> Apache web server software
You should add the upstream URL of the project here, separated from the
main description by an empty newline. (See how other packages do it).
>
> ----- buildroot/package/apache/apache.mk -----
>
> #############################################################
> #
> # apache
> #
> #############################################################
> APACHE_VERSION = 2.2.19
We usually put an empty new line between the header and the first
variable declaration.
> #APACHE_SITE = http://mir2.ovh.net/ftp.apache.org/dist/httpd/
Please remove unneeded comments if you want to submit this package to
Buildroot.
> APACHE_SITE = http://archive.apache.org/dist/httpd/
> APACHE_SOURCE = httpd-$(APACHE_VERSION).tar.bz2
> APACHE_INSTALL_STAGING = YES
> APACHE_INSTALL_TARGET = YES
This line is not needed, as it is the default.
> APACHE_AUTORECONF = YES
This is generally not needed, as releases shipped as tarballs usually
have the configure script and the Makefile.in pre-generated. So there
should be a comment above this line that explains why it is needed.
>
> APACHE_CONF_ENV += \
> ac_cv_file__dev_zero=yes \
> ac_cv_func_setpgrp_void=yes \
> apr_cv_tcp_nodelay_with_cork=yes \
> ac_cv_sizeof_struct_iovec=8 \
> apr_cv_process_shared_works=yes \
> apr_cv_mutex_robust_shared=no \
> ac_cv_struct_rlimit=yes \
> ap_cv_void_ptr_lt_long=no \
> CC="$(TARGET_CC)" \
> CFLAGS="$(TARGET_CFLAGS)" \
> LDFLAGS="$(TARGET_LDFLAGS)" \
The CC, CFLAGS and LDFLAGS are not needed here, they are already passed
by the Buildroot autotools infrastructure.
> APACHE_CONF_OPT += \
> --host="$(REAL_GNU_TARGET_NAME)" \
--host is already passed by Buildroot.
> --prefix="/apacheSW/" \
--prefix is already passed by Buildroot (and /apacheSW/ is not a
standard and appropriate location).
> --enable-so \
> --enable-module=all
>
>
>
>
>
Please remove useless empty lines.
> define APACHE_CONFIGURE_CMDS
> (cd $(@D) && rm -rf config.cache; \
> $(APACHE_CONF_ENV) \
> ./configure \
> $(APACHE_CONF_OPT) \
> )
> endef
This is not needed, Buildroot already has a default
<pkg>_CONFIGURE_CMDS for autotools packages that does the right thing.
If it doesn't then please add a comment above that explains why we need
to override the CONFIGURE_CMDS.
> define ADD_INIT_SCRIPT
> $(INSTALL) -m 0755 -D $(APACHE_DIR_PREFIX)/$(APACHE_NAME)/Apache_InitScript $(TARGET_DIR)/etc/init.d/S90Apache;
> endef
> APACHE_POST_INSTALL_STAGING_HOOKS += ADD_INIT_SCRIPT
You should use APACHE_INSTALL_INIT_SYSV to install an init script. See
package/lighttpd/lighttpd.mk for an example. Also, please name your
script S90apache in package/apache/. So in the end, it should look like:
define APACHE_INSTALL_INIT_SYSV
[ -f $(TARGET_DIR)/etc/init.d/S50apache ] || \
$(INSTALL) -D -m 755 package/apache/S50apache \
$(TARGET_DIR)/etc/init.d/S50apache
endef
Thanks!
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:[~2013-01-16 21:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 21:30 [Buildroot] need help adding apache to buildroot Jenkins, Lee
2013-01-16 21:35 ` Gustavo Zacarias
2013-01-17 22:41 ` Jenkins, Lee
2013-01-18 9:25 ` Jérôme Pouiller
2013-01-18 15:31 ` Thomas Petazzoni
2013-01-18 16:11 ` [Buildroot] [PATCH] Add support for plain URL in $(PKG)_PATCH variable Jérôme Pouiller
2013-01-30 18:59 ` Yann E. MORIN
2013-01-30 19:23 ` Yann E. MORIN
2013-01-30 22:37 ` Jérôme Pouiller
2013-01-30 22:37 ` Jérôme Pouiller
2013-01-30 22:54 ` Yann E. MORIN
2013-01-30 23:11 ` Jérôme Pouiller
2013-01-31 8:18 ` [Buildroot] [PATCH 1/2] " Jérôme Pouiller
2013-01-31 8:18 ` [Buildroot] [PATCH 2/2] Add $(PKG_NAME) in name of downloaded patches Jérôme Pouiller
2013-04-26 6:18 ` Arnout Vandecappelle
2013-05-13 15:51 ` [Buildroot] [PATCH v2] Add support for plain URL in $(PKG)_PATCH variable Jérôme Pouiller
2013-05-13 20:59 ` Yann E. MORIN
2013-05-14 9:51 ` Markos Chandras
2013-09-07 6:12 ` Peter Korsgaard
2013-04-26 6:00 ` [Buildroot] [PATCH 1/2] " Arnout Vandecappelle
2013-01-31 8:20 ` [Buildroot] [PATCH] " Jérôme Pouiller
2013-01-30 22:50 ` Thomas Petazzoni
2013-01-30 22:57 ` Yann E. MORIN
2013-01-30 23:04 ` Jérôme Pouiller
2013-01-30 23:10 ` Yann E. MORIN
2013-01-16 21:54 ` Thomas Petazzoni [this message]
2013-07-07 14:16 ` [Buildroot] need help adding apache to buildroot Stephan Hoffmann
2013-07-18 16:46 ` Jenkins, Lee
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=20130116225440.1d45f78c@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