From: Cesar Strauss <cestrauss@gmail.com>
To: guile-user@gnu.org
Cc: Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: Building shared libs (DLL) under Cygwin (1.8.4)
Date: Thu, 01 May 2008 15:47:03 -0300 [thread overview]
Message-ID: <481A1027.3010700@gmail.com> (raw)
In-Reply-To: <87iqxyz93k.fsf@ossau.uklinux.net>
Neil Jerram wrote:
> "Aaron Turner" <synfinatic@gmail.com> writes:
>
>> I'm trying to rebuild Guile 1.8.4 under Cygwin (latest stable) because
>> the Cygwin packages seem to have some serious problems (I've been told
>> it was built with the wrong version of gcc). Everything seems ok
>> (configure && make report no errors), but when it's all said and done,
>> all I get is a static library. [snip]
>>
Please try this:
make clean
libtoolize --copy --force
./configure
make
make install
It seems the particular version of libtool included in guile 1.8.4 is
somewhat broken on mingw/cygwin. The above worked for me on both platforms.
>
> I would suggest working with the Cygwin people on this. They are more
> likely to be familiar with this kind of issue (which probably comes
> from how the autotools work on Cygwin), and if there's a problem with
> the current Guile in Cygwin, it would be much better to fix that for
> all Cygwin users.
I agree, that would be best.
>
> (FWIW, when I last updated a couple of weeks ago, the Cygwin Guile
> version was 1.8.2. I've been using that successfully and haven't seen
> any critical problems. I did see a problem with open-input-pipe
> hanging, but worked around that by writing to a temporary file instead
> and then re-reading from that file.)
As far as I could follow the discussion, it seems the Autogen tool used
to crash frequently, but worked when Guile was compiled from source.
Regards,
Cesar
next prev parent reply other threads:[~2008-05-01 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 20:57 Building shared libs (DLL) under Cygwin (1.8.4) Aaron Turner
2008-05-01 9:06 ` Neil Jerram
2008-05-01 18:47 ` Cesar Strauss [this message]
2008-05-01 21:53 ` Aaron Turner
2008-05-01 22:22 ` Aaron Turner
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=481A1027.3010700@gmail.com \
--to=cestrauss@gmail.com \
--cc=guile-user@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).