From: Oliver.Graute@neuhaus.de
To: Oliver Graute <oliver.graute@gmail.com>
Cc: ptxdist@pengutronix.de
Subject: [ptxdist] Antwort: [PATCHv2 2/2] apache2: added patches to compile 2.4.12
Date: Wed, 18 Feb 2015 13:56:21 +0100 [thread overview]
Message-ID: <OF2257A3A2.75F8077C-ONC1257DF0.00468EF7-C1257DF0.0047171C@neuhaus.de> (raw)
In-Reply-To: <1424257249-19944-2-git-send-email-oliver.graute@neuhaus.de>
[-- Attachment #1.1.1: Type: text/plain, Size: 1634 bytes --]
> diff --git a/patches/httpd-2.4.12/0007-workaround-for-
> exports_errors.patch b/patches/httpd-2.4.12/0007-workaround-for-
> exports_errors.patch
> new file mode 100644
> index 0000000..160f27a
> --- /dev/null
> +++ b/patches/httpd-2.4.12/0007-workaround-for-exports_errors.patch
> @@ -0,0 +1,8318 @@
> +diff -rupN AQ/server/exports.c AR/server/exports.c
> +--- AQ/server/exports.c 1970-01-01 01:00:00.000000000 +0100
> ++++ AR/server/exports.c 2015-02-18 08:35:53.700805309 +0100
> +@@ -0,0 +1,8272 @@
> ++/*
> ++ * THIS FILE WAS AUTOGENERATED BY make_exports.awk
> ++ *
> ++ * This is an ugly hack that needs to be here, so
> ++ * that libtool will link all of the APR functions
> ++ * into server regardless of whether the base server
> ++ * uses them.
> ++ */
the make_exports.awk rewrite the httpd-2.4.12/server/exports.c
during the build, then the build fails:
exports.c:4117:55: error: 'apr_hash_this_key' undeclared here (not in a
function)
exports.c:4121:59: error: 'apr_hash_this_key_len' undeclared here (not in a
function)
exports.c:4125:55: error: 'apr_hash_this_val' undeclared here (not in a
function)
exports.c:4568:62: error: 'apr_sockaddr_is_wildcard' undeclared here (not
in a function)
exports.c:5307:55: error: 'apr_shm_create_ex' undeclared here (not in a
function)
exports.c:5323:55: error: 'apr_shm_attach_ex' undeclared here (not in a
function)
if I manually overwrite the pachted exports.c after a first failed build it
compiles...
the solution with manually patching the exports.c file is the dirty way
here.
Can somebody explain me how i adapt the make_exports.awk to generate a
prober exports.c?
[-- Attachment #1.1.2: Type: text/html, Size: 1974 bytes --]
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2446 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-02-18 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 11:00 [ptxdist] [PATCHv2 1/2] apache2: version bump to 2.4.12 Oliver Graute
2015-02-18 11:00 ` [ptxdist] [PATCHv2 2/2] apache2: added patches to compile 2.4.12 Oliver Graute
2015-02-18 12:56 ` Oliver.Graute [this message]
2015-02-19 16:23 ` [ptxdist] [PATCHv2 1/2] apache2: version bump to 2.4.12 Michael Olbrich
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=OF2257A3A2.75F8077C-ONC1257DF0.00468EF7-C1257DF0.0047171C@neuhaus.de \
--to=oliver.graute@neuhaus.de \
--cc=oliver.graute@gmail.com \
--cc=ptxdist@pengutronix.de \
/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