From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: how to manage 2 guile version
Date: Thu, 14 Jul 2016 20:13:00 -0000 [thread overview]
Message-ID: <4e6e442a-1b34-00c6-4705-0dc1a2b62d26@gmail.com> (raw)
I was thinking to pack the last guile-2.0.x
however this will require the repack of 1.8.8
version.
No problem for the headers as they are
properly isolated
/usr/include/guile/1.8/libguile/__scm.h
/usr/include/guile/1.8/libguile.h
but what to do of
/usr/lib/libguile.dll.a
relocate it somewhere like
/usr/lib/guile/1.8/libguile.dll.a
Other suggestion/preference ?
Regards
Marco
next reply other threads:[~2016-07-14 20:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 20:13 Marco Atzeri [this message]
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
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=4e6e442a-1b34-00c6-4705-0dc1a2b62d26@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).