From: Andy Wingo <wingo@pobox.com>
To: Volker Grabsch <vog@notjusthosting.com>
Cc: bug-guile@gnu.org, guile-devel@gnu.org, Mike Gran <spk121@yahoo.com>
Subject: Re: Guile with win32 cross compiling
Date: Fri, 20 May 2011 12:32:29 +0200 [thread overview]
Message-ID: <m3mxihwtky.fsf@unquote.localdomain> (raw)
In-Reply-To: <20110516230101.GB3311@flap> (Volker Grabsch's message of "Tue, 17 May 2011 01:01:01 +0200")
Hi Volker,
Thanks for the report.
On Tue 17 May 2011 01:01, Volker Grabsch <vog@notjusthosting.com> writes:
> "fix-include-error-in-gen-scmconfig.patch"
> The patch re-introduces a change which I already proposed
> in my last patch: You can't use $(AM_CPPFLAGS) for the native
> build, because it adds "-I../lib" which means that <stdio.h>
> is taken from the local GNU-lib installation. The problem is
> that the GNU-lib in "lib/" has been configured for MinGW, not
> for the native system. So it performs some fixes which don't
> work on non-MinGW systems, leading to strange, unhelpful error
> messages. It took me quite some time to figure this out, mostly
> because I thought that this should have already been fixed.
Hmmmm! Yes, sorry for overlooking this part of your patch. After
thinking for a while about it I agree with you. I modified your patch
to add a comment.
> "remove-mingw-ifsock.patch"
> This patch fixes an issue that also appears on native MinGW
> build, because _S_IFSOCK simply isn't defined there. Note that
> this issue was already reported, but hasn't been fixed up to
> now, at least not in the stable-2.0 branch:
> http://lists.gnu.org/archive/html/guile-devel/2011-01/msg00183.html
I'll look at this when I'm back on the internet.
> CC net_db.lo
> net_db.c:460:1: error: 'AI_ALL' undeclared here (not in a function)
> net_db.c:460:1: error: expression in static assertion is not an integer
> net_db.c:482:33: warning: 'struct addrinfo' declared inside parameter list [enabled by default]
If your target does not have e.g. struct addrinfo, because it does not
have IPv6, then you need to configure with
ac_cv_type_struct_addrinfo=no. Check your config.log. Or should this
be working somehow?
There are other ac_cv_* for getaddrinfo and other routines.
Happy hacking,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-05-20 10:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 22:06 Guile with win32 cross compiling Volker Grabsch
2011-04-01 10:38 ` Andy Wingo
2011-04-01 18:50 ` Volker Grabsch
2011-04-12 11:14 ` Andy Wingo
2011-04-23 16:10 ` Volker Grabsch
2011-04-24 10:42 ` Andy Wingo
2011-05-16 23:01 ` Volker Grabsch
2011-05-20 10:32 ` Andy Wingo [this message]
2011-05-20 12:25 ` Volker Grabsch
2011-05-20 12:48 ` Jan Nieuwenhuizen
2011-05-20 13:25 ` Andy Wingo
2011-05-20 22:19 ` Volker Grabsch
2011-06-17 9:03 ` Andy Wingo
2011-07-01 13:52 ` Andy Wingo
2011-04-24 20:22 ` Ludovic Courtès
2011-04-28 21:03 ` Andy Wingo
2011-06-19 14:42 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2011-04-05 19:43 Mike Gran
2011-04-06 1:38 ` Volker Grabsch
2011-04-06 12:46 ` Ludovic Courtès
2011-03-26 22:04 Volker Grabsch
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=m3mxihwtky.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=guile-devel@gnu.org \
--cc=spk121@yahoo.com \
--cc=vog@notjusthosting.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).