From: Andy Wingo <wingo@pobox.com>
To: 16451-done@debbugs.gnu.org
Subject: bug#16451: build newest guile on FreeBSD error
Date: Tue, 21 Jun 2016 14:44:00 +0200 [thread overview]
Message-ID: <87mvmezp7z.fsf@pobox.com> (raw)
In-Reply-To: <87y52ht7dg.fsf@netris.org> (Mark H. Weaver's message of "Wed, 15 Jan 2014 13:41:47 -0500")
No additional info; let's close. Please file a new bug if you have
errors building Guile from git again. Thanks!
Andy
On Wed 15 Jan 2014 19:41, Mark H Weaver <mhw@netris.org> writes:
> z_axis <z_axis@163.com> writes:
>
>> hi,friends
>> After `git clone git://git.sv.gnu.org/guile.git`, `./autogen` reports:
>> m4: illegal option -- -
>> usage: m4 [-d flags] [-t name] [-gs] [-D name[=value]]...
>> [-U name]... [-I dirname]... file...
>>
>> on my FreeBSD 9.1 box.
>
> Following up on this: it turns out that the call to "m4 --version" in
> autogen.sh is apparently the only problem here.
>
> I suggested (on IRC) that he run "autoreconf -i --force --verbose" (the
> only important thing in autogen.sh) and it seems to have worked properly
> and created a working configure script.
>
> Some other notes on FreeBSD, while the knowledge is fresh: On FreeBSD,
> the "boehm-gc" package is compiled without threading support. To
> support threads, the "boehm-gc-threaded" package is needed, which
> installs the library with a nonstandard name -lgc-threaded, so
> BDW_GC_LIBS="-L/usr/local/lib -lgc-threaded" must be passed to
> configure.
>
> Maybe some of this should go into a README, but first I should ask:
> z_axis: did these steps produce a working Guile on FreeBSD 9.1?
>
> Thanks,
> Mark
prev parent reply other threads:[~2016-06-21 12:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 5:51 bug#16451: build newest guile on FreeBSD error z_axis
2014-01-15 18:41 ` Mark H Weaver
2016-06-21 12:44 ` Andy Wingo [this message]
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=87mvmezp7z.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=16451-done@debbugs.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).