[libgpg-error PATCH] doc: if ever, depend on yat2m$(EXEEXT)

Michael Haubenwallner michael.haubenwallner at ssi-schaefer.com
Thu Jul 12 17:49:04 CEST 2018

On 07/12/2018 05:15 PM, Michael Haubenwallner wrote:
> Hello,
> I've thought about EXEEXT for build too and found AC_PROG_CC_FOR_BUILD to
> set $BUILD_EXEEXT, but because that was commented out in configure.ac I've
> not followed that further, as I was not aware of AX_CC_FOR_BUILD at all.

Ohw, shouldn't the build tools in src/ also use EXEEXT_FOR_BUILD?


> So yes, your attempt looks good to me, thanks> 
> /haubi/
> On 07/10/2018 04:12 AM, NIIBE Yutaka wrote:
>> Hello,
>> Thanks for your patch.
>> Michael Haubenwallner <michael.haubenwallner at ssi-schaefer.com> writes:
>>> * doc/Makefile.am (CROSS_COMPILING, HAVE_YAT2M): Set empty YAT2M_DEP.
>>> (not CROSS_COMPILING): Ignore detected yat2m, use local one.  Use EXEEXT
>>> in YAT2M_DEP rather than explicit '.exe' based on HAVE_W32_SYSTEM.
>> I agree that using EXEEXT is better than HAVE_W32_SYSTEM.  Also, I agree
>> that we don't need to use detected yat2m for !CROSS_COMPILING.
>> Furthermore, I also think that the detection of yat2m on build system is
>> not needed for CROSS_COMPILING now, because we can build
>> yat2m-for-build.
>> Remaining problem is we need to have something like EXEEXT for build
>> machine, so that we can support cross building on Windows (say, for
>> POSIX machine).
>> Here is my attempt.  How do you think?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-build-use-EXEEXT_FOR_BUILD-everywhere.patch
Type: text/x-patch
Size: 3575 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20180712/73d63274/attachment.bin>

More information about the Gnupg-devel mailing list