unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Aaron Turner" <synfinatic@gmail.com>
To: "Cesar Strauss" <cestrauss@gmail.com>
Cc: guile-user@gnu.org, Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: Building shared libs (DLL) under Cygwin (1.8.4)
Date: Thu, 1 May 2008 14:53:39 -0700	[thread overview]
Message-ID: <1ca1c1410805011453o69963566q2133d1063ca37c9d@mail.gmail.com> (raw)
In-Reply-To: <481A1027.3010700@gmail.com>

On Thu, May 1, 2008 at 11:47 AM, Cesar Strauss <cestrauss@gmail.com> wrote:
> 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.

Yep!  That worked! Well mostly... 'guile-config link' doesn't return
the correct string (-L/usr/local/lib is AFTER -lguile) but that's
easily fixed with a little shell script magic.

> > 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.

I'll see if I can ping the maintainer.

> > (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.)
> >

I'm still having problems with the lastest version.  I've been told
that it was due to the Cygwin Guile using a different version of gcc
then what is shipped with Cygwin.   No idea if that's true.

>  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.

Yep, that's what I've been told.  Limited testing so far seems to
indicate this does fix the problem (autogen isn't crashing anymore,
except for using it with pipes: 'autogen -v | echo' for example).

Thanks!

-- 
Aaron Turner
http://synfin.net/
http://tcpreplay.synfin.net/ - Pcap editing & replay tools for Unix
They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -- Benjamin Franklin




  reply	other threads:[~2008-05-01 21:53 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
2008-05-01 21:53     ` Aaron Turner [this message]
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=1ca1c1410805011453o69963566q2133d1063ca37c9d@mail.gmail.com \
    --to=synfinatic@gmail.com \
    --cc=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).