Re: [OctDev] admin/mk{doc,texi} and multiple Octave versions.

[Lute K. <Lut...@cw...>]

David Bateman <Dav...@mo...> writes:

> According to Lute Kamstra <Lut...@cw...> (on 11/06/03):
>
>> I just tried to get CVS HEAD from octave forge installed in
>> conjunctions with Octave's CVS HEAD.  I encountered two minor
>> problems:
>> 
>> 1. admin/mk{doc,texi} do not have their execute bit set.  I had to do
>>    this by hand to convince the Makefiles to build the docs.
>
> Sorry, my fault... But I'm damned if I see how I can add this flag
> to the file in the CVS. I tried adding a single space to the files
> and adding the execute flag, but only the space was
> added. Arrgggghhhh...

Normally, to force a commit, touch would be enough.

> How to do this??? I've even tried removing the files and re-adding
> them.  But they get revived from the Attic with the old permissions.
> I think the only way is to do the chmod in the RCS tree, but I don't
> have access to this. Does anyone have this type of access to
> sourceforge???

Yes, if you accidentally add a file before making it executable, you
must go into the repository and manually chmod +x the RCS file.

>> 2. I have several versions of Octave in my path.  configure picks the
>>    first one it encounters, which was not the right one.  I convinced
>>    the configure script to pick the right one with:
>> 
>>      ./configure OCTAVE=/the/right/octave
>> 
>>    Maybe this var should be mentioned in INSTALL?
>
>
> ./configure --help
>
> I always run this to figure the correct install options for me
> everytime I install a new package.

Yup, that's what I do as well.  The help text doesn't mention the
OCTAVE variable (nor the MKOCTFILE variable, by the way).

  Lute.