From: hanwen@byrd.xs4all.nl (Han-Wen Nienhuys)
Cc: guile-devel@gnu.org
Subject: Re: Guile 1.7.91 has been released.
Date: Mon, 13 Feb 2006 08:37:13 +0000 (UTC) [thread overview]
Message-ID: <dspgfp$kvo$1@sea.gmane.org> (raw)
In-Reply-To: 87y80gyxrq.fsf@zagadka.de
In article <87y80gyxrq.fsf@zagadka.de>, Marius Vollmer <mvo@zagadka.de> wrote:
>We are pleased to announce the release of Guile 1.7.91. This is a
>release candidate for Guile 1.8. It can be found here:
cross-compiling from Linux/x86 to Mingw/x86:
Making all in libguile
make[2]: Entering directory `/home/hanwen/vc/gub/target/mingw/build/guile-1.7.91/libguile'
make[2]: *** Geen regel voor aanmaken doel `fileblocks.x', nodig voor `all'. Stop.
make[2]: Leaving directory `/home/hanwen/vc/gub/target/mingw/build/guile-1.7.91/libguile'
make[1]: *** [all-recursive] Fout 1
make[1]: Leaving directory `/home/hanwen/vc/gub/target/mingw/build/guile-1.7.91'm
there is no fileblocks.* anywhere. Configure mentions
## Remove fileblocks.o from the object list. This file gets added by
## the Autoconf macro AC_STRUCT_ST_BLOCKS. But there is no need.
#LIBOBJS="`echo ${LIBOBJS} | sed 's/fileblocks\.o//g'`"
I got this when configuring with
/home/hanwen/vc/gub/target/mingw/src/guile-1.7.91/configure
--config-cache --enable-shared --disable-static
--build=i386-redhat-linux --host=i686-mingw32 --target=i686-mingw32
--prefix=/usr --sysconfdir=/usr/etc --includedir=/usr/include
--libdir=/usr/lib --without-threads --with-gnu-ld --enable-deprecated
--enable-discouraged --disable-error-on-warning --enable-relocation
--disable-rpath PATH_SEPARATOR=;
LDFLAGS=-L/home/hanwen/vc/gub/target/mingw/system/usr/lib
CC_FOR_BUILD= C_INCLUDE_PATH= CPPFLAGS= LIBRARY_PATH= LDFLAGS= cc
-I/home/hanwen/vc/gub/target/mingw/build/guile-1.7.91
-I/home/hanwen/vc/gub/target/mingw/src/guile-1.7.91
-I/home/hanwen/vc/gub/target/mingw/build/guile-1.7.91/libguile
-I. -I/home/hanwen/vc/gub/target/mingw/src/guile-1.7.91/libguile
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2006-02-13 8:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 23:15 Guile 1.7.91 has been released Marius Vollmer
2006-02-12 23:46 ` Michael Tuexen
2006-02-14 21:50 ` Marius Vollmer
2006-02-18 23:45 ` Han-Wen Nienhuys
2006-02-20 20:59 ` Marius Vollmer
2006-02-13 8:37 ` Han-Wen Nienhuys [this message]
2006-02-13 9:41 ` Ludovic Courtès
2006-02-13 19:50 ` Marius Vollmer
2006-02-14 9:22 ` Ludovic Courtès
2006-02-14 19:39 ` Marius Vollmer
2006-02-13 12:49 ` Bill Schottstaedt
2006-02-13 21:35 ` Kevin Ryde
2006-02-13 22:33 ` Bill Schottstaedt
2006-02-13 22:50 ` Kevin Ryde
2006-02-13 23:35 ` Bill Schottstaedt
2006-02-14 0:58 ` Kevin Ryde
2006-02-14 1:28 ` Kevin Ryde
2006-02-14 21:36 ` Bill Schottstaedt
2006-02-15 0:03 ` Kevin Ryde
2006-02-15 7:56 ` Ludovic Courtès
2006-02-15 12:37 ` Guile 1.7.91 has been released (x86-64 segfault) Bill Schottstaedt
2006-02-14 9:27 ` Guile 1.7.91 has been released Ludovic Courtès
2006-02-13 15:31 ` Bill Schottstaedt
2006-02-14 8:50 ` Andy Wingo
2006-02-20 18:36 ` Neil Jerram
2006-02-20 20:04 ` Bill Schottstaedt
2006-02-13 18:40 ` Bill Schottstaedt
2006-02-14 11:35 ` Han-Wen Nienhuys
2006-02-14 21:32 ` Marius Vollmer
2006-02-14 13:58 ` Ludovic Courtès
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='dspgfp$kvo$1@sea.gmane.org' \
--to=hanwen@byrd.xs4all.nl \
--cc=guile-devel@gnu.org \
--cc=hanwen@xs4all.nl \
/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).