public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: how to manage 2 guile version
Date: Mon, 03 Apr 2017 02:07:00 -0000	[thread overview]
Message-ID: <ca3b30e1-3f51-639d-52c3-50e386e1bc0b@cygwin.com> (raw)
In-Reply-To: <6c9ae11b-eee0-6a9d-9a8b-76e2d2529276@gmail.com>

On 2017-04-01 07:30, Marco Atzeri wrote:
> thanks. The issue for make was in the lack of
> 2.0.9-module-ldflags.patch.
> With that "make check" has no issue on guile test.

That's because libguilereadline-* is a module, and without linking it 
with -module, cygport removes the .la file needed to load it (since 
guile uses ltdl).  That's also the reason for KEEP_LA_FILES=module.

> I am making minor change to your proposal for package names;
> for 2.0 we have libguile2.0-devel so for 1.8 I am using
> libguile1.8-devel instead of libguile-devel and
> current guile-devel is obsoleted by libguile2.0-devel.

Fair enough.

> I will upload as soon I complete the build for both arch.

Which you've already done.  Thanks!

-- 
Yaakov

      reply	other threads:[~2017-04-03  2:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14 20:13 Marco Atzeri
2016-07-14 21:29 ` Yaakov Selkowitz
2016-07-17 17:02   ` Marco Atzeri
2017-03-28  2:16     ` Yaakov Selkowitz
2017-03-28  5:50       ` Marco Atzeri
2017-03-28  7:09         ` szgyg
2017-03-28 16:01           ` Yaakov Selkowitz
2017-03-28 19:50             ` Marco Atzeri
2017-03-28 21:19               ` Yaakov Selkowitz
2017-03-28 15:34         ` Yaakov Selkowitz
2017-03-28 16:01           ` Marco Atzeri
2017-03-28 16:08             ` Yaakov Selkowitz
2017-04-01 12:30               ` Marco Atzeri
2017-04-03  2:07                 ` Yaakov Selkowitz [this message]

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=ca3b30e1-3f51-639d-52c3-50e386e1bc0b@cygwin.com \
    --to=yselkowitz@cygwin.com \
    --cc=cygwin-apps@cygwin.com \
    /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).