From: Marius Schamschula <mschamschula@gmail.com>
To: 14201@debbugs.gnu.org
Subject: bug#14201: guile build issue under Mac OS X
Date: Sat, 13 Apr 2013 09:16:52 -0500 [thread overview]
Message-ID: <5B6BB6BC-4207-47FA-924C-D0E0E96F570B@gmail.com> (raw)
Hi there,
I just tried building guile 2.0.9 under three versions of Mac OS X (10.6.8, 10.7.5 and 10.8.3). In all cases I get the following error:
<snip>
Making all in lib
make[2]: Entering directory `/private/tmp/guile-2.0.9/lib'
make[2]: ../build-aux/install-sh: Command not found
make[2]: *** [arpa/inet.h] Error 127
make[2]: Leaving directory `/private/tmp/guile-2.0.9/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/private/tmp/guile-2.0.9'
make: *** [all] Error 2
</snip>
Notes:
* the tile /private/tmp/guile-2.0.9/build-aux/install-sh does exist and is executable.
* /usr/include/arpa/inet.h is also available, so no CPPFLAGS should be needed
Any ideas?
--
Marius Schamschula
next reply other threads:[~2013-04-13 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 14:16 Marius Schamschula [this message]
2013-04-14 13:52 ` bug#14201: guile build issue under Mac OS X Ludovic Courtès
2013-04-14 14:01 ` Marius Schamschula
2013-04-14 14:25 ` Ludovic Courtès
2013-04-14 22:11 ` 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=5B6BB6BC-4207-47FA-924C-D0E0E96F570B@gmail.com \
--to=mschamschula@gmail.com \
--cc=14201@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).