From: "Shawn O. Pearce" <spearce@spearce.org>
To: Nicolas Pitre <nico@cam.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH, resent] fix openssl headers conflicting with custom SHA1 implementations
Date: Tue, 30 Sep 2008 13:39:28 -0700 [thread overview]
Message-ID: <20080930203928.GN21310@spearce.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0809301621091.3635@xanadu.home>
Nicolas Pitre <nico@cam.org> wrote:
> On ARM I have the following compilation errors:
...
> This is a bit ugly but given the rat nest of system includes we have I
> don't know how to solve this any better.
Hmm. On Linux x86 with your change:
In file included from imap-send.c:32:
cache.h: In function 'create_ce_mode':
cache.h:186: error: 'S_IFLNK' undeclared (first use in this function)
I think that last hunk which moved the openssl includes to be before
cache.h is the problem. This squashed in seems to make it my build
work again:
diff --git a/imap-send.c b/imap-send.c
index 01f1c9a..6b8c66e 100644
--- a/imap-send.c
+++ b/imap-send.c
@@ -22,6 +22,7 @@
* Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
*/
+#include "cache.h"
#ifdef NO_OPENSSL
typedef void *SSL;
#else
@@ -29,8 +30,6 @@ typedef void *SSL;
#include <openssl/err.h>
#endif
-#include "cache.h"
-
struct store_conf {
char *name;
const char *path; /* should this be here? its interpretation is driver-specific */
--
Shawn.
next prev parent reply other threads:[~2008-09-30 20:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 20:22 [PATCH, resent] fix openssl headers conflicting with custom SHA1 implementations Nicolas Pitre
2008-09-30 20:39 ` Shawn O. Pearce [this message]
2008-09-30 20:46 ` Nicolas Pitre
2008-09-30 20:51 ` Shawn O. Pearce
2008-10-01 3:47 ` Jeff King
2008-10-01 15:54 ` Shawn O. Pearce
2008-10-01 16:04 ` Jeff King
2008-10-01 16:10 ` Shawn O. Pearce
2008-10-01 16:35 ` Nicolas Pitre
2008-10-01 16:39 ` Shawn O. Pearce
2008-10-01 18:05 ` [PATCH v2] " Nicolas Pitre
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=20080930203928.GN21310@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
/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;
as well as URLs for NNTP newsgroup(s).