From: Gasiu <gasiu@konto.pl>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] I'm not able to compile hacked szap. with new multiproto
Date: Mon, 24 Mar 2008 14:04:53 +0100 [thread overview]
Message-ID: <47E7A6F5.8030106@konto.pl> (raw)
I'm not able to compile hacked szap (from
abraham.manu.googlepages.com/szap.c) with new multiproto (b5a34b6a209d).
2 weeks ago was a change, and now by compiling:
CC szap
szap.c: In function ‘zap_to’:
szap.c:368: error: ‘struct dvbfe_info’ has no member named ‘delivery’
szap.c:372: error: ‘struct dvbfe_info’ has no member named ‘delivery’
szap.c:376: error: ‘struct dvbfe_info’ has no member named ‘delivery’
szap.c:401: error: ‘struct dvbfe_info’ has no member named ‘delivery’
szap.c:412: error: ‘struct dvbfe_info’ has no member named ‘delivery’
make: *** [szap] Error 1
szap from:
dvb-apps-2686c080e0b5.tar.gz
doesn't work...
./szap polonia
reading channels from file '/home/gasiu/.szap/channels.conf'
zapping to 4 'polonia':
sat 0, frequency = 11488 MHz H, symbolrate 27500000, vpid = 0x00a0, apid
= 0x0050 sid = 0x13ed
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
FE_READ_STATUS failed: Invalid argument
status 40000 | signal fffe | snr fffe | ber fffffffe | unc fffffffe |
FE_READ_STATUS failed: Invalid argument
status 40000 | signal fffe | snr fffe | ber fffffffe | unc fffffffe |
FE_READ_STATUS failed: Invalid argument
status 40000 | signal fffe | snr fffe | ber fffffffe | unc fffffffe |
"--
Pozdrawiam!
Gasiu
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next reply other threads:[~2008-03-24 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 13:04 Gasiu [this message]
2008-03-24 13:12 ` [linux-dvb] I'm not able to compile hacked szap. with new multiproto Igor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47E7A6F5.8030106@konto.pl \
--to=gasiu@konto.pl \
--cc=linux-dvb@linuxtv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.