From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: how to manage 2 guile version
Date: Sat, 01 Apr 2017 12:30:00 -0000 [thread overview]
Message-ID: <6c9ae11b-eee0-6a9d-9a8b-76e2d2529276@gmail.com> (raw)
In-Reply-To: <d07a2100-a402-64fd-84db-69f89f8e0ddc@cygwin.com>
On 28/03/2017 18:08, Yaakov Selkowitz wrote:
> On 2017-03-28 11:00, Marco Atzeri wrote:
>> On 28/03/2017 17:34, Yaakov Selkowitz wrote:
>>> On 2017-03-28 00:50, Marco Atzeri wrote:
>>>> Last week I was planning to just release guile-2.0.14,
>>>> but while the test of guile itself is almost fine I noticed an issue
>>>> when building "make" with it.
>>>>
>>>> Only tested on 64 bits, 'make check' of make fails on all guile tests
>>>
>>> WFM:
>>
>> Than is the Symantec annoying me again.
>> I will check in Safe mode without AV.
>
> I have updated my proposed changes:
>
> https://github.com/cygwinports/guile
> https://github.com/cygwinports/guile1.8
Hi Yaakov,
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.
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.
I will upload as soon I complete the build for both arch.
Regards
Marco
next prev parent reply other threads:[~2017-04-01 12:30 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 [this message]
2017-04-03 2:07 ` Yaakov Selkowitz
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=6c9ae11b-eee0-6a9d-9a8b-76e2d2529276@gmail.com \
--to=marco.atzeri@gmail.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).