From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: bug-guile@gnu.org
Subject: Re: i18n broken on mingw cross compile
Date: Sat, 13 Sep 2008 00:54:41 -0300 [thread overview]
Message-ID: <gafdkm$s6b$1@ger.gmane.org> (raw)
In-Reply-To: <87r67pst7e.fsf@gnu.org>
Ludovic Courtès escreveu:
> Hi,
>
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
>>
>>> In file included from /home/lilydev/vc/gub/target/mingw/root/usr/include/sys/time.h:3,
>>> from ../libguile/scmconfig.h:25,
>>> from /home/lilydev/vc/gub/target/mingw/src/guile-1.9.git/libguile/__scm.h:52,
>>> from /home/lilydev/vc/gub/target/mingw/src/guile-1.9.git/libguile.h:30,
>>> from /home/lilydev/vc/gub/target/mingw/src/guile-1.9.git/libguile/discouraged.c:22:
>>> ../lib/time.h:76: error: expected ';', ',' or ')' before '__timer'
>>> ../lib/time.h:78: error: expected ';', ',' or ')' before '__timer'
>> Reported here:
>>
>> http://thread.gmane.org/gmane.comp.lib.gnulib.bugs/14574
>
> Actually, as suggested by Eric Blake, this is probably fixed by the
> attached patch (committed). Can you confirm it?
adding the include to srfi-4.c, I still get
i686-mingw32-gcc -mms-bitfields -DHAVE_CONFIG_H -DSCM_IMPORT -I. -I.. -I/home/lilydev/vc/gub/target/mingw/src/guile-localhost--home-lilydev-vc-guile-master/srfi -I.. -I/home/lilydev/vc/gub/target/mingw/src/guile-localhost--home-lilydev-vc-guile-master/srfi/.. -I/home/lilydev/vc/gub/target/mingw/src/guile-localhost--home-lilydev-vc-guile-master/lib -I../lib -Wall -Wmissing-prototypes -g -O2 -MT srfi-1.lo -MD -MP -MF .deps/srfi-1.Tpo -c /home/lilydev/vc/gub/target/mingw/src/guile-localhost--home-lilydev-vc-guile-master/srfi/srfi-1.c -DDLL_EXPORT -DPIC -o .libs/srfi-1.o
In file included from /home/lilydev/vc/gub/target/mingw/root/usr/include/sys/time.h:3,
from ../libguile/scmconfig.h:25,
from /home/lilydev/vc/gub/target/mingw/src/guile-localhost--home-lilydev-vc-guile-master/srfi/../libguile/__scm.h:52,
from /home/lilydev/vc/gub/target/mingw/src/guile-localhost--home-lilydev-vc-guile-master/srfi/../libguile.h:30,
from /home/lilydev/vc/gub/target/mingw/src/guile-localhost--home-lilydev-vc-guile-master/srfi/../srfi/srfi-4.h:25,
from /home/lilydev/vc/gub/target/mingw/src/guile-localhost--home-lilydev-vc-guile-master/srfi/srfi-4.c:25:
../lib/time.h:76: error: expected ';', ',' or ')' before '__timer'
../lib/time.h:78: error: expected ';', ',' or ')' before '__timer'
make[3]: ** [srfi-4.lo] Erro 1
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
next prev parent reply other threads:[~2008-09-13 3:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 14:07 i18n broken on mingw cross compile Han-Wen Nienhuys
2008-09-09 9:30 ` Ludovic Courtès
2008-09-09 14:02 ` Han-Wen Nienhuys
2008-09-09 14:42 ` Ludovic Courtès
2008-09-10 2:38 ` Han-Wen Nienhuys
2008-09-11 19:41 ` Ludovic Courtès
2008-09-12 7:45 ` Ludovic Courtès
2008-09-13 3:27 ` Han-Wen Nienhuys
2008-09-13 3:54 ` Han-Wen Nienhuys [this message]
2008-09-13 13:55 ` Ludovic Courtès
2008-09-13 15:13 ` Han-Wen Nienhuys
2008-09-13 18:16 ` Ludovic Courtès
2008-09-13 18:50 ` Han-Wen Nienhuys
2008-09-13 20:06 ` Ludovic Courtès
2008-09-13 15:47 ` Han-Wen Nienhuys
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='gafdkm$s6b$1@ger.gmane.org' \
--to=hanwen@xs4all.nl \
--cc=bug-guile@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).