ejabberd - Comments for "expat.h: No such file or directory" https://www.ejabberd.im/node/1679 en The patch is complete, at https://www.ejabberd.im/node/1679#comment-41233 <p>The patch is complete, at least concerning the expat part. Seems I never bothered to look at the SVN version ☺</p> <p>And this patch should really be applied to <code>conftools/expat.m4</code> in expat CVS. I'll try to write them a more coherent bug report some day.</p> <p>But the patch does confuse me a bit. <code>aclocal.m4</code> is supposed to be automatically generated by <code>aclocal</code>, using bits and pieces from all the libraries that the program in question uses (this is described in the <noindex><a href="http://www.gnu.org/software/automake/manual/html_node/Invoking-aclocal.html" rel="nofollow" >automake manual</a></noindex>), but it seems that the <code>aclocal.m4</code> of ejabberd is very much handcrafted, having grown lots of local hacks over the years.</p> <p>Now I'm really confused ☺</p> Thu, 09 Aug 2007 23:26:53 +0000 legoscia comment 41233 at https://www.ejabberd.im I am not sure to understand https://www.ejabberd.im/node/1679#comment-40502 <p>I am not sure to understand right now. However, I can consider a fix proposal.<br /> Do you have a suggestion ?<br /> How is it related to this fix: <noindex><a href="https://support.process-one.net/browse/EJAB-204" title="https://support.process-one.net/browse/EJAB-204" rel="nofollow" >https://support.process-one.net/browse/EJAB-204</a></noindex><br /> It the patch incomplete ?</p> <p>--<br /> Mickaël Rémond<br /> <noindex><a href="http://www.process-one.net/" rel="nofollow" >Process-one</a></noindex></p> Thu, 09 Aug 2007 12:02:14 +0000 mremond comment 40502 at https://www.ejabberd.im Hm… memory is hazy. https://www.ejabberd.im/node/1679#comment-38076 <p>Hm… memory is hazy. Apparently I just commented on that bug, which seemed to be about the same problem…</p> Mon, 06 Aug 2007 13:16:06 +0000 legoscia comment 38076 at https://www.ejabberd.im The bug is that the https://www.ejabberd.im/node/1679#comment-38074 <p>The bug is that the configure script doesn't properly distinguish between CPPFLAGS and CFLAGS. CPPFLAGS names the flags that are necessary for both preprocessing and compiling, while CFLAGS names the flags that are only needed for compiling, i.e:</p> <p><code>cpp $CPPFLAGS foo.c</code></p> <p><code>cc $CFLAGS $CPPFLAGS foo.c</code></p> <p>However, the configure tests for expat don't include CPPFLAGS when using the compiler.</p> <p>I <noindex><a href="https://sourceforge.net/tracker/?func=detail&amp;atid=110127&amp;aid=842049&amp;group_id=10127" rel="nofollow" >reported </a></noindex> this to the expat people four years ago, and was a bit surprised by their response (they basically misunderstood what the bug report was about), but didn't bother responding as most people never will understand autoconf anyway, and my workaround is good enough for me.</p> <p>So yes, the bug is really in expat, but ejabberd does include the erroneous code in <code>src/aclocal.m4</code>.</p> Mon, 06 Aug 2007 12:38:21 +0000 legoscia comment 38074 at https://www.ejabberd.im It does not seem a bug in https://www.ejabberd.im/node/1679#comment-38073 <p>It does not seem a bug in configure. To me it does the right thing. if you pass CFLAGS (expat is a C program), it works correctly.<br /> I do not know if it is the job of configure to look into /usr/local for expat.</p> <p>what do you think ?</p> <p>--<br /> Mickaël Rémond<br /> <noindex><a href="http://www.process-one.net/" rel="nofollow" >Process-one</a></noindex></p> Mon, 06 Aug 2007 08:43:04 +0000 mremond comment 38073 at https://www.ejabberd.im It's a bug in the configure https://www.ejabberd.im/node/1679#comment-37660 <p>It's a bug in the configure script. You need to set CFLAGS to the same value as CPPFLAGS.</p> Sun, 05 Aug 2007 15:00:55 +0000 legoscia comment 37660 at https://www.ejabberd.im