From: Jan Nieuwenhuizen <janneke-list@xs4all.nl>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: cross building 1.9.14 for mingw
Date: Mon, 31 Jan 2011 21:16:24 +0100 [thread overview]
Message-ID: <1296504984.17905.7.camel@vuurvlieg> (raw)
In-Reply-To: <874o8r8kdn.fsf@gnu.org>
Ludovic Courtès schreef op za 29-01-2011 om 22:34 [+0100]:
Hi Ludovic,
> OK but all the modules listed after ‘accept’ above are needed too,
> right?
Yes, sure.
> Hmm could it be that there was a typo? Here running ‘git-version-gen’
> outside of a Git tree works fine:
>
> $ guile/build-aux/git-version-gen .tarball-version s/foo/bar/
> UNKNOWN
Yes, does it also work when you change configure.ac and autoreconf?
> Ouch. May I suggest reporting it to bug-gnulib@gnu.org? :-) I think
> people there would be happy to provide an appropriate fix and we
> wouldn’t even have to worry. ;-)
Yes, hat would be nice.
> > --- a/libguile/bdw-gc.h
> > +++ b/libguile/bdw-gc.h
> > @@ -30,7 +30,9 @@
> > allocation. */
> >
> > # define GC_THREADS 1
> > +#ifndef __MINGW32__
> > # define GC_REDIRECT_TO_LOCAL 1
> > +#endif /* __MINGW32__ */
>
> Why?
I'm using gc-6.8 and cannot seem to build a version for Mingw that
includes GC_local_malloc -- that seems to be for linux pthreads only.
Removing this redirect to local, fixes these
.libs/libguile_2.0_la-alist.o:alist.c:(.text+0x6bf): undefined reference to `_GC_local_malloc'
build errors.
> > - buf->st_mode = _S_IFSOCK | _S_IREAD | _S_IWRITE | _S_IEXEC;
> > + buf->st_mode = _S_IREAD | _S_IWRITE | _S_IEXEC;
>
> Why? Isn’t ‘_S_IFSOCK’ defined on all MinGW?
I don't have in it my mingw-runtime-3.14. If there's a newer version,
I've misses something and would like to hear it.
> > +#ifndef __MINGW32__
> > /* Make sure the `AI_*' flags can be stored as INUMs. */
> > verify (SCM_I_INUM (SCM_I_MAKINUM (AI_ALL)) == AI_ALL);
>
> Does MinGW lack getaddrinfo?
No, it lacks the AI_* definitions. I realise that you may not want
to include this just yet, although it "documents" my progress building
it for mingw.
> Gnulib’s ‘getaddrinfo’ module, which we use, is supposed to take care of
> this, i.e., it should fall back to ‘gethostbyname’ if needed.
Yes.
More bits in a new thread.
Thanks, greetings,
Jan.
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
next prev parent reply other threads:[~2011-01-31 20:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-29 19:41 cross building 1.9.14 for mingw Jan Nieuwenhuizen
2011-01-29 21:34 ` Ludovic Courtès
2011-01-31 20:16 ` Jan Nieuwenhuizen [this message]
2011-01-31 20:44 ` Ludovic Courtès
2011-02-15 10:20 ` Jan Nieuwenhuizen
2011-02-22 8:34 ` Andy Wingo
2011-02-24 9:39 ` Jan Nieuwenhuizen
2011-02-24 10:37 ` Ludovic Courtès
2011-03-04 11:11 ` problems solved by AC_LIB_HAVE_LINKFLAGS [was: cross building 1.9.14 for mingw] Andy Wingo
2011-03-20 8:08 ` Jan Nieuwenhuizen
2011-03-20 8:21 ` Ralf Wildenhues
2011-03-20 8:34 ` Jan Nieuwenhuizen
2011-03-20 8:56 ` Ralf Wildenhues
2011-01-29 21:39 ` Relocatable installation Ludovic Courtès
2011-01-31 20:26 ` Jan Nieuwenhuizen
2011-01-31 20:50 ` Andy Wingo
2011-01-31 20:55 ` Jan Nieuwenhuizen
2011-01-31 21:30 ` Andy Wingo
2011-01-31 21:49 ` Jan Nieuwenhuizen
2011-01-31 21:00 ` Ludovic Courtès
2011-01-31 21:18 ` Jan Nieuwenhuizen
2011-01-31 22:09 ` Ludovic Courtès
2011-01-31 22:26 ` Jan Nieuwenhuizen
2011-02-14 12:29 ` cross building 1.9.14 for mingw Ludovic Courtès
2011-02-15 10:02 ` Jan Nieuwenhuizen
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=1296504984.17905.7.camel@vuurvlieg \
--to=janneke-list@xs4all.nl \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
/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).