[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: mxe-octave stable-octave
From: |
John D |
Subject: |
RE: mxe-octave stable-octave |
Date: |
Fri, 3 Jan 2014 08:06:26 -0500 |
-----Original Message-----
From: Thorsten Liebig [mailto:address@hidden
Sent: Friday, January 03, 2014 3:54 AM
To: address@hidden; address@hidden
Subject: Re: mxe-octave stable-octave
John,
I think your latest change broke mxe-octave
(http://hg.octave.org/mxe-octave/rev/0779856e1186).
I tried a fresh hg clone and there the file:
$TOPDIR/octave/octave-version`
just does not (yet) exist... and mk-dist fails...
regards
Thorsten
Am 03.01.2014 09:32, schrieb Thorsten Liebig:
> Am 03.01.2014 05:03, schrieb John W. Eaton:
>> On 01/02/2014 10:51 PM, fgnievinski wrote:
>>> Thorsten Liebig wrote
>>>> Thanks for the update, I have build the stable version without any
>>>> problems.
>>>> But I have not had the time to test it on some windows machine.
>>>> If anybody is interested, you can download it here:
>>>> http://www.openems.de/download/octave/octave-3.8.0.exe
>>> It seems that \share\octave\3.8.0-rc2\ doesn't need to be shipped as
>>> there's already \share\octave\3.8.0\ ?
>> This happens because of the way that the distribution is generated.
>> The only way to make one that doesn't possibly contain cruft left
>> over from earlier builds with older versions of packages (not just
>> Octave, but any dependency) is to use "make clean" and build from
scratch.
>>
>> I think we can do better than this, but it wasn't high on my list of
>> priorities.
>>
>> jwe
>>
>>
>>
> I guess that was my mistake? I build rc2 and was to lazy to do a full
> cleanup before building 3.8.0 final...
> What would be the proper approach to have a clean build regardless of
> prior actions??
>
> Thorsten
>
I guess I broke that :)
Fixed now