>>> "Bruce" == Bruce Korb <[EMAIL PROTECTED]> writes:
[...]
Bruce> Distributing files marked read-only or in read-only directories
Bruce> really ought not cause a distribution failure.
They really wouldn't cause distcheck failures if they weren't rebuilt.
(Does it ring a bell?)
[...]
Bruc
Hi,
Is this question appropriate here?
I have three directories that each contain source code. I also have one
directory that is called include. In all I have these 4 directories at
the same level.
src/ annotate-two-src/ gdb-mi-src/ include/
I would like to create 1 static library from the
Alexandre Duret-Lutz wrote:
> Bruce> cp: cannot create regular file \
> Bruce> `blocksort-1.4.2/libopts/.deps/save.Plo': Permission denied
>
> Simply don't distribute these files.
Distributing files marked read-only or in read-only directories
really ought not cause a distribution failure. It
>>> "Bruce" == Bruce Korb <[EMAIL PROTECTED]> writes:
Bruce> At the end of this log, you'll see lines like this:
Bruce> cp: cannot create regular file \
Bruce> `blocksort-1.4.2/libopts/.deps/save.Plo': Permission denied
Simply don't distribute these files.
--
Alexandre Duret-Lutz
At the end of this log, you'll see lines like this:
cp: cannot create regular file \
`blocksort-1.4.2/libopts/.deps/save.Plo': Permission denied
It used to work, of course, but I was persuaded to "upgrade"
automake/autoconf/libtool again. Silly me. I should learn.
It's as aggravating as heck
For one of my project there was a bug report regarding
the project.m4 file that is going to be installed. So
far I did just use $datadir/aclocal of course - as it
is uncertain whether some `aclocal --print-ac-dir`
can be written to. Using a prefix-related default
happens to be gnu-style anyway. And
