From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: building cvs guile on Mac OS X 10.4
Date: Sat, 14 May 2005 13:49:54 +0100 [thread overview]
Message-ID: <4285F3F2.9090201@ossau.uklinux.net> (raw)
In-Reply-To: <6B73DD52-DE68-457F-AFAA-A353CED78052@mac.com>
Richard Todd wrote:
>
> Problem 2.*****
> Libtoolize not found. Turns out OS X calls it glibtoolize, but
> nothing in ./autogen.sh figured this out.
>
> My solution: export LIBTOOLIZE=glibtoolize
> I assume there is a better solution.
Actually, HEAD CVS does not call libtoolize anymore (since 8th March).
Were you building with a CVS snapshot from before this date?
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-05-14 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-08 7:36 building cvs guile on Mac OS X 10.4 Richard Todd
2005-05-12 6:39 ` Neil Jerram
2005-05-12 23:51 ` Richard Todd
2005-05-13 1:48 ` Kevin Ryde
2005-05-13 6:55 ` Neil Jerram
2005-05-14 12:49 ` Neil Jerram [this message]
2005-05-14 13:07 ` Neil Jerram
2005-05-14 16:32 ` Richard Todd
2005-05-15 23:31 ` Kevin Ryde
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=4285F3F2.9090201@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@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).