unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: wgl@ciexinc.com
Cc: 17060@debbugs.gnu.org, request@debbugs.gnu.org
Subject: bug#17060: libguile install-data-hook target fails on BSD make
Date: Sat, 22 Mar 2014 00:28:09 -0400	[thread overview]
Message-ID: <87eh1un9gm.fsf@yeeloong.lan> (raw)
In-Reply-To: <87vbv7qrke.fsf@ciexinc.com> (wgl@ciexinc.com's message of "Fri,  21 Mar 2014 19:28:49 +0000")

retitle 17060 libguile install-data-hook target fails on BSD make
thanks

wgl@ciexinc.com writes:

> The install step for building guile 2.0.11 fails after successful
> compile on amd 64 bit FreeBsd 10.0. The error message is
>
>     install: : No such file or directory
>     
> where the item being installed has a blank name.
>
> At the suggestion of mark_weaver on IRC, i tried 'gmake' instead of
> 'make' and the install went through successfully.
>
> The thinking is that there is something non-portable in the make file.

wgl provided more information on IRC, so let me fill in the details.

The failing target is 'install-data-hook' in libguile/Makefile.am.
It prints this on the console: (modulo whitespace)

 /usr/bin/install -c -m 644
      /usr/local/lib/libguile-2.0.so.29-gdb.scm

Notice that the source filename is missing, suggesting that '$<' is the
empty string.  It then fails with the following error message:

  install: : No such file or directory

This is when using BSD 'make' from FreeBSD 10.
When using 'gmake' (GNU Make), it works properly.

      Mark





  reply	other threads:[~2014-03-22  4:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 19:28 bug#17060: wgl
2014-03-22  4:28 ` Mark H Weaver [this message]
2014-03-29 13:27   ` bug#17060: libguile install-data-hook target fails on BSD make Ludovic Courtès
2016-06-21 13:06     ` Andy Wingo

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=87eh1un9gm.fsf@yeeloong.lan \
    --to=mhw@netris.org \
    --cc=17060@debbugs.gnu.org \
    --cc=request@debbugs.gnu.org \
    --cc=wgl@ciexinc.com \
    /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).