On Sat, 9 Dec 2006, Tzafrir Cohen wrote:
Could you please try to edit vzaphfc_main.c from within the tarball to
remove that line? That include file should be unnecessary, anyway.
If this works then we need to fix vzaphfc.
Ok, line snipped, tarball rebuilt and off we go. It gets past that
On Friday 08 December 2006 21:39, Andrea Borgia wrote:
Tried both m-a and make-kpkg, same errors.
Does it matter that the kernel build link points to an unusual location?
Andrea,
zaptel, as far as I can tell is building fine against 2.6.18 which is the
target kernel for etch.
We only have a
On Sat, 9 Dec 2006, Mark Purcell wrote:
We only have a matter of days/ weeks before etch freezes, so I wouldn't like
to introduce any late changes to zaptel at this stage.
I wasn't aware of the situation, sorry.
Thus I'll give this bug a relatively low priority until etch releases.
By all
Package: zaptel-source
Version: 1:1.2.11.dfsg-1
Followup-For: Bug #400705
Tried both m-a and make-kpkg, same errors.
Does it matter that the kernel build link points to an unusual location?
Below is the m-a log for rc6:
dh_testdir
dh_testroot
rm -f *-stamp
# Add here commands to clean up after
Hi
On Fri, Dec 08, 2006 at 10:39:04PM +0100, Andrea Borgia wrote:
Package: zaptel-source
Version: 1:1.2.11.dfsg-1
Followup-For: Bug #400705
Tried both m-a and make-kpkg, same errors.
Does it matter that the kernel build link points to an unusual location?
Below is the m-a log for rc6:
5 matches
Mail list logo
