Re: [forge] octclip & octproj build loop

[Marco Atzeri]

On 6/16/2015 1:07 PM, José Luis García Pallero wrote:
> 2015-06-16 12:48 GMT+02:00 Marco Atzeri <address@hidden>:
> > On 6/16/2015 12:38 PM, José Luis García Pallero wrote:
> > > Hi, Marco:
> > >
> > > I've installed both packages (from sourceforge) in Octave 4.0 on a
> > > debian box with gcc-4.9 and make 4.0 and 4.1 (make 4.0 is the one in
> > > Debian, and make 4.1 was installed by me in order to match your
> > > version) and all works fine. I haven't any problem in the compilation
> > > process
> > >
> > > Best regards
> >
> > Hi Jose,
> > Thanks for the test.
> >
> > I discovered that running "make" works fine, and removing
> > the "clean" step in "all" does not solve the issue.
> >
> > The problem is in the redefinition of CC=mkoctfile
> > when calling from inside octave "pkg build .."
> >
> > Using MKOCTFILE=mkoctfile, as for the attached patch, solve my
> > build issue.
>
> Hello:
>
> I don't understand. In my installation all works without problems
> using also pkg build instead of pkg install

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.


Regards
Marco

octproj.patch
Description: Text document