From: Matthieu Vachon <matthieu.o.vachon@gmail.com>
To: "kawa@sourceware.org" <kawa@sourceware.org>
Subject: Compilation (make) problem
Date: Fri, 20 Sep 2013 18:51:00 -0000 [thread overview]
Message-ID: <CAOTvmomJD0WVUbgHJR=AGvr79V6b-FsJj1zgAs5JA9rVS0r+1A@mail.gmail.com> (raw)
Hi,
Under CentOS 6.3, I have some problems executing the Makefile found in
the `bin/` directory.
When arriving at this Makefile, the build failed saying that `tmp` is
a folder and cannot be written to. This problem comes from this line
in the Makefile (there is more that one instance):
echo '#!/bin/sh' >tmp
This kind of lines are seen in target `kawa.sh`, `gckawa` and `gexo`.
I understand the purpose of this code, i.e. creating a temp file
containing the generated script then putting it at the right place.
But I can't find if it is either injected, or it's a macro, or what
else.
For now, my workaround is to replace all instance of `> tmp` by `>
/tmp/tempfile.out` so it can output the data correctly.
What would be the right fix for this problem?
Regards.
Matt
next reply other threads:[~2013-09-20 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 18:51 Matthieu Vachon [this message]
2013-09-20 19:53 ` Per Bothner
2013-09-21 6:05 ` Matthieu Vachon
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOTvmomJD0WVUbgHJR=AGvr79V6b-FsJj1zgAs5JA9rVS0r+1A@mail.gmail.com' \
--to=matthieu.o.vachon@gmail.com \
--cc=kawa@sourceware.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).