From: John Dallaway <john@dallaway.org.uk>
To: Sergei Gavrikov <sg@belvok.com>
Cc: eCos development list <ecos-devel@ecos.sourceware.org>
Subject: Re: heapgen.tcl permission
Date: Fri, 09 Jan 2009 09:07:00 -0000 [thread overview]
Message-ID: <496713CC.50703@dallaway.org.uk> (raw)
In-Reply-To: <20090109085415.GA3900@sg-ubuntu.local>
Hi Sergei
Sergei Gavrikov wrote:
> headers finished
> /bin/sh: /home/sg/repo/clean/ecos/packages/services/memalloc/common/current/src/heapgen.tcl: Permission denied
> make[1]: *** [heaps.cxx] Error 126
> make: *** [build] Error 2
>
> Unfortunately, it has 644 instead 755 after last CVS update. I did miss
> something?
The custom make rule for heaps.cxx now assumes that the user has execute
permission for heapgen.tcl. On reflection, this is not the most robust
approach for anonCVS repositories. I will sort this out. In the meantime:
chmod a+x services/memalloc/common/current/src/heapgen.tcl
John Dallaway
next prev parent reply other threads:[~2009-01-09 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 8:54 Sergei Gavrikov
2009-01-09 9:07 ` John Dallaway [this message]
2009-01-09 9:57 ` Sergei Gavrikov
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=496713CC.50703@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-devel@ecos.sourceware.org \
--cc=sg@belvok.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).