On 6/26/2019 9:22 AM, Michael Stahl wrote:
On 26.06.19 17:09, Austin Stephens wrote:
Well, that is the odd thing. I am using the the make that lode gave to
me. From what I can tell, the log produced by using "-d" reports that
the submakes that get used are also from the lode thing. The version is
4.2.1.
CreateProcess(D:\lode\opt\bin\make,D:/lode/opt/bin/make -d,...)
GNU Make 4.2.1
Built for Windows32
Copyright (C) 1988-2016 Free Software Foundation, Inc.
maybe it's the top-level one that is problematic?
so you must have "HAVE_GNUMAKE_FILE_FUNC=" in config_host.mk
you could check configure.ac and look what GNUMAKE it detects, if it's
the expected one... and why the HAVE_GNUMAKE_FILE_FUNC check around line
5183 fails.
I can confirm that "HAVE_GNUMAKE_FILE_FUNC=" is in config_host.mk. Running the test manually passes
so it should set it to true. I am going to try running autogen.sh again. Maybe I didn't have LODE_HOME
defined when I ran it last, so it used the wrong make?
--
Sincerely,
Austin Stephens
Western Standard
Fluency Dev
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.