octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 3.2.0


From: Jaroslav Hajek
Subject: Re: 3.2.0
Date: Thu, 21 May 2009 09:46:40 +0200

On Thu, May 21, 2009 at 9:33 AM, Michael Goffioul
<address@hidden> wrote:
> On Thu, May 21, 2009 at 7:35 AM, Jaroslav Hajek <address@hidden> wrote:
>> I have no problem with any of these, except the texi2dvi - I suggest
>> you either keep this one for yourself, or change it so that the stack
>> size is configurable via configure.
>
> I'd rather keep that one for my own system as it seems more a workaround
> for my configuration. I just included it for completeness (so there's a record
> of the problem), in case someone gets the same problem.
>
>> But I'd like to ask you to add ChangeLog entries for all the patches.
>
> Of course. Note that I have write access to the repository, so I can
> apply them myself, if there's no objection.

None from me. I think all the patches have either been discussed
(though I haven't been following all the discussions), or are bug
fixes. So I'd say go ahead.

I have one more note for support_cpp_scripts: There seems to be a
ChangeLog entry included but buried inside the ChangeLog. Please move
it to the front prior to applying.

>> You can skip patch_templates.diff - this one seems identical to my
>> workaround patch for Intel C++, which I kept for myself so far, so
>> I'll apply that. The code in question is correct C++ AFAIK, but it
>> doesn't seem to hurt clarity to explicitly qualify the templates. Note
>> that GCC is apparently smarter here than its commercial competitors.
>
> Indeed. I'll let you apply your patch and then try again to build octave.
>

It's online now.

cheers

-- 
RNDr. Jaroslav Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz


reply via email to

[Prev in Thread] Current Thread [Next in Thread]