From: Massimiliano Gubinelli <m.gubinelli@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 39999@debbugs.gnu.org
Subject: bug#39999: make install fails on mac (Catilina, Guile-3.0.1)
Date: Wed, 11 Mar 2020 12:20:19 +0100 [thread overview]
Message-ID: <E7E06727-509E-47BF-9F47-536E517096E8@gmail.com> (raw)
In-Reply-To: <87a74nm9iq.fsf@gnu.org>
Hi Ludovic,
the problem seems to be the multiple -e together with -i.
Example:
Horst:clean mgubi$ cat - > test
pippo
Horst:clean mgubi$ sed -i -e 's,pippo,pluto,g' -e 's,pippo,pluto,g' -e 's,pippo,pluto,g' test
sed: -e: No such file or directory
Horst:clean mgubi$ sed -e 's,pippo,pluto,g' -e 's,pippo,pluto,g' -e 's,pippo,pluto,g' test
pluto
Horst:clean mgubi$ sed -i -e 's,pippo,pluto,g' test
Horst:clean mgubi$
The first command give error while the other work. If I put -i at the end I get
Horst:clean mgubi$ sed -e 's,pippo,pluto,g' -e 's,pippo,pluto,g' -e 's,pippo,pluto,g' -i test
sed: -i may not be used with stdin
Is ok to do
Horst:clean mgubi$ sed -e 's,pippo,pluto,g' -e 's,pippo,pluto,g' -e 's,pippo,pluto,g' -i ‘' test
Best,
Max
> On 11. Mar 2020, at 12:11, Ludovic Courtès <ludo@gnu.org> wrote:
>
> Hi,
>
> Massimiliano Gubinelli <m.gubinelli@gmail.com> skribis:
>
>> make install on the last Guile 3.0.1 fails on my Mac (Catilina) with the following message
>>
>>
>> ../build-aux/install-sh -c -d '/Users/mgubi/t/guile3-usr/include/guile/3.0/libguile'
>> /usr/bin/install -c -m 644 version.h scmconfig.h '/Users/mgubi/t/guile3-usr/include/guile/3.0/libguile'
>> /Library/Developer/CommandLineTools/usr/bin/make install-data-hook
>> /usr/bin/install -c -m 644 libguile-3.0-gdb.scm /Users/mgubi/t/guile3-usr/lib/libguile-3.0.a-gdb.scm
>> sed: -e: No such file or directory
>> make[5]: *** [install-data-hook] Error 1
>> make[4]: *** [install-data-am] Error 2
>> make[3]: *** [install-am] Error 2
>> make[2]: *** [install] Error 2
>> make[1]: *** [install-recursive] Error 1
>> make: *** [install] Error 2
>
> I suppose the ‘sed’ invocation in the INSTANTIATE variable in Makefile
> assumes we’re using GNU sed, which is probably not the case on your
> machine.
>
>> I found that the following change to libguile/Makefile go around the problem
>>
>> INSTANTIATE = \
>> $(SED) -i '' -e 's,[@]pkgdatadir[@],$(pkgdatadir),g' \
>> -e 's,[@]pkglibdir[@],$(pkglibdir),g' \
>> -e 's,[@]GUILE_EFFECTIVE_VERSION[@],$(GUILE_EFFECTIVE_VERSION),g’
>
> What if you move ‘-i’ last, and without ''? That should expand to
> something like:
>
> sed -e … -e … -e … -i libguile-3.0-gdb.scm
>
> Thanks,
> Ludo’.
next prev parent reply other threads:[~2020-03-11 11:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 13:29 bug#39999: make install fails on mac (Catilina, Guile-3.0.1) Massimiliano Gubinelli
2020-03-11 11:11 ` Ludovic Courtès
2020-03-11 11:20 ` Massimiliano Gubinelli [this message]
2020-03-11 14:04 ` Ludovic Courtès
2020-04-29 18:22 ` bug#39999: MacOS Catalina with sed W. Lincoln Harvey via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2020-04-29 19:30 ` bug#39999: BSD sed vs Gnu sed W. Lincoln Harvey via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2020-04-30 0:04 ` Greg Troxel
2020-04-30 0:37 ` bug#39999: sed -i non-POSIX wlharvey4--- via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2020-05-01 14:37 ` Greg Troxel
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=E7E06727-509E-47BF-9F47-536E517096E8@gmail.com \
--to=m.gubinelli@gmail.com \
--cc=39999@debbugs.gnu.org \
--cc=ludo@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).