[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [forge] octclip & octproj build loop
From: |
José Luis García Pallero |
Subject: |
Re: [forge] octclip & octproj build loop |
Date: |
Tue, 16 Jun 2015 15:56:17 +0200 |
2015-06-16 15:53 GMT+02:00 Marco Atzeri <address@hidden>:
> On 6/16/2015 2:12 PM, José Luis García Pallero wrote:
>>
>> 2015-06-16 14:07 GMT+02:00 Marco Atzeri <address@hidden>:
>>>
>>> On 6/16/2015 1:07 PM, José Luis García Pallero wrote:
>
>
>>> CC is one of the variable used by mkoctfile
>>>
>>> $ /usr/bin/mkoctfile-4.0.0.exe -p CC
>>> gcc
>>>
>>> At least on cygwin package build system
>>> using CC=mkoctfile causes a circular
>>> dependency loop that spins a never ending
>>> fork chain of mkoctfile's
>>>
>>> Attached similar patch for octproj.
>>
>>
>> I understand and I'll do the changes. But which is the problem with
>> the 'clean' target? I think I could maintain it
>>
>
> aesthetical preference ?
>
> I feel wrong to have build and remove instructions
> coupled. It looks to me a risk of undefined behaviour
I've deleted the 'clean' order from the 'all' target. I've uploaded
OctCLIP and OctPROJ to the sourceforge tracker, so they will be soon
on octave-forge
Thanks
>
> Regards
> Marco
>
>
>
--
*****************************************
José Luis García Pallero
address@hidden
(o<
/ / \
V_/_
Use Debian GNU/Linux and enjoy!
*****************************************