unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Matthew Keeter <matt.j.keeter@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, guile-devel@gnu.org
Subject: Re: Guile 2.2 on MSYS2 + MinGW
Date: Thu, 18 Jan 2018 10:18:36 -0500	[thread overview]
Message-ID: <A88ED77D-C8CC-4441-B4FE-7866129289E6@gmail.com> (raw)
In-Reply-To: <83wp0fuul5.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2180 bytes --]

Yup, I’m building 2.2.3.  I see mktime.c in guile-2.2.3/lib, but do not see
mktime.o when I objdump libgnu.a, indicating that it’s not being built.

In config.log, I see a few lines that could be relevant:

configure:34662: checking for working mktime
...
gl_cv_func_working_mktime=yes
...
GNULIB_MKTIME=‘1'
...
REPLACE_MKTIME=‘0'
...
gl_GNULIB_ENABLED_mktime_FALSE='#'
gl_GNULIB_ENABLED_mktime_TRUE=‘'

(full config.log is here: https://gist.github.com/mkeeter/81c273069a2804ad8d53e72533f6f8da)

Does this offer any insight?  I’m confused by the conflicting GNULIB_MKTIME vs
gl_GNULIB_ENABLED_mktime_TRUE, but am not adept at parsing automake outputs…

-Matt

> On Jan 18, 2018, at 9:09 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: Matthew Keeter <matt.j.keeter@gmail.com>
>> Date: Wed, 17 Jan 2018 17:30:02 -0500
>> Cc: guile-devel@gnu.org
>> 
>> Following your advice, I’m now trying to build a 32-bit version under MinGW,
>> This fails a little earlier in the process:
>> 
>> make[2]: Entering directory '/home/mkeeter/guile/src/build-i686-w64-mingw32/libguile'
>> make  all-am
>> make[3]: Entering directory '/home/mkeeter/guile/src/build-i686-w64-mingw32/libguile'
>>  CCLD     libguile-2.2.la
>> ../lib/.libs/libgnu.a(timegm.o):timegm.c:(.text+0x22): undefined reference to `mktime_internal'
>> collect2.exe: error: ld returned 1 exit status
>> make[3]: *** [Makefile:2373: libguile-2.2.la] Error 1
>> 
>> This appears to be the same bug as #24681
>> (http://lists.gnu.org/archive/html/bug-guile/2017-03/msg00095.html),
>> but I don’t see anyone successfully resolving it
>> (and I can’t find any references to it in the Git history).
>> 
>> Any ideas?
> 
> mktime_internal is in Gnulib's mktime.c.  What version of Guile 2.2.x
> are you building?  The latest v2.2.3 includes mktime.c in
> guile-2.2.3/lib/, do you have it?  If you do have it, do you see
> mktime.o in libgnu.a?
> 
> If mktime.c is in the tree, but is not compiled, you need to
> investigate why, by looking at config.log, where the configure script
> determines whether your system needs mktime.c and/or mktime_internal.


[-- Attachment #2: Type: text/html, Size: 4310 bytes --]

  reply	other threads:[~2018-01-18 15:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16 22:50 Guile 2.2 on MSYS2 + MinGW Matthew Keeter
2018-01-17 15:54 ` Eli Zaretskii
2018-01-17 22:30   ` Matthew Keeter
2018-01-18 14:09     ` Eli Zaretskii
2018-01-18 15:18       ` Matthew Keeter [this message]
2018-01-18 16:00         ` Eli Zaretskii
2018-01-24  2:18           ` Matthew Keeter
2018-01-24 18:57             ` Eli Zaretskii
2018-01-25 14:54               ` Matthew Keeter
2018-01-25 17:22                 ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=A88ED77D-C8CC-4441-B4FE-7866129289E6@gmail.com \
    --to=matt.j.keeter@gmail.com \
    --cc=eliz@gnu.org \
    --cc=guile-devel@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).