[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Does current mxe-octave of stable branch supports 4.0.2?
From: |
Tatsuro MATSUOKA |
Subject: |
Re: Does current mxe-octave of stable branch supports 4.0.2? |
Date: |
Sun, 1 May 2016 08:06:04 +0900 (JST) |
> From: Philip Nienhuis
> To: Tatsuro MATSUOKA ; "octave-maintainers
> Cc:
> Date: 2016/5/1, Sun 05:52
> Subject: Re: Does current mxe-octave of stable branch supports 4.0.2?
>
>T atsuro MATSUOKA wrote:
>>> From: PhilipNienhuis
>>
>>> To: octave-maintainers
>>> Cc:
>>> Date: 2016/4/30, Sat 21:19
>>> Subject: Re: Does current mxe-octave of stable branch supports 4.0.2?
>>>
>>> t macchant wrote
>>>> Hello
>>>>
>>>> Octave-4.0.2 was uploaded recently.
>>>> http://octave.1599824.n4.nabble.com/octave-4-0-2-td4676595.html
>>>>
>>>> I have tried to build 64 bit binaries using stable branch build
> for
>>>> mxe-octave.
>>>>
>> CX on the mxe-octave tree
>>> for stable branch
>>>> reports
>>>> the below updates.
>>>>
>>>> index.html
>>>> src/build-gettext.mk
>>>> src/libmng.mk
>>>> src/mingw-texinfo-1-fixes.patch
>>>>
>>>>
>>>> Thus I have to hack the src/stable-octave.mk.
>>>
>>> Maybe i do not understand you well?
>>>
>>> .... but in hg.octave.org/mxe-octave I see this:
>>>
>>> 24 hours ago John Donoghue of-optim: update to 1.5.1 default
> tip
>>> 24 hours ago John Donoghue of-struct: update to 1.0.13
>>> 2 days ago John Donoghue stable-octave: update for v4.0.2
>>> :
>>>
>>> so mxe-octave looks to be up-to-date.
>>>
>>> Philip
>>>
>> OK. In the tutorial of wiki for mxe [1] suggest to use
>>
>>
>> "hg -v pull" and "hg -v update" but not "hg
> pull" and "hg update"
>> Perhaps this is the origin why I was not able to get the recent change.
>
> The "-v" flag merely means "verbose", i.e., show how many
> changesets/files are to be processed / updated.
>
> Could it be that you just by accident pulled / updated just before John
> D. pushed those changesets?
> Whatever happened, I think that if you try now, it will work fine :-)
>
> Philip
I have execute "hg pull" and "hg update" again and execute autoconf,
./configure with options, and make.
Now it seems that octave-4.0.2 is building now.
As you told, perhaps the phenomena that I met are mere bad timing.
Thank you for your follow up
Tatsuro