* folajimi <[EMAIL PROTECTED]> [2005-12-29 14:20]:
> Did you ever hear back from the upstream developers regarding our build
> issues?
Paul Kienzle and David Bateman, both upstream developers of octave-forge,
participated to the current thread, but they do not really address the
specific problems
On Thu, 29 Dec 2005, Rafael Laboissiere wrote:
> * folajimi <[EMAIL PROTECTED]> [2005-12-29 11:55]:
>
> > Is there anything that Colin and I can do yet? Colin is out of town,
> > but I was just wondering if we will be able to resume work on the task
> > assigned to us.
>
> IIRC, the task assigned
* folajimi <[EMAIL PROTECTED]> [2005-12-29 11:55]:
> Is there anything that Colin and I can do yet? Colin is out of town,
> but I was just wondering if we will be able to resume work on the task
> assigned to us.
IIRC, the task assigned to Colin and you was to split the octave-forge
binary packag
On Thu, 29 Dec 2005, Rafael Laboissiere wrote:
> * Joaquim Ortega <[EMAIL PROTECTED]> [2005-12-29 10:02]:
>
> > I believe that I have identified the bug. [...] With this three-line
> > fix the package built fine.
>
> Thanks *_a lot_* for that! The package indeed builds fine in sid with
> your sug
* Joaquim Ortega <[EMAIL PROTECTED]> [2005-12-29 10:02]:
> I believe that I have identified the bug. [...] With this three-line
> fix the package built fine.
Thanks *_a lot_* for that! The package indeed builds fine in sid with
your suggested changes. I prepared a new version of octave-forge wh
I believe that I have identified the bug. It is related to the new behaviour
of make documented as
* All pattern-specific variables that match a given target are now used
(previously only the first match was used).
What happens now is that in the file main/Makeconf.in and main/Makeconf.base
6 matches
Mail list logo