#3122 closed defect (worksforme)
Oscam Compile error Linux x86
Reported by: | slaider | Owned by: | |
---|---|---|---|
Priority: | critical | Component: | General |
Severity: | high | Keywords: | |
Cc: | Sensitive: | no |
Description
Revision
8254
Issue Description
Oscam Compile error Linux x86
When the issue occurs
oscam.c: In function 'check_thread':
oscam.c:1909:3: warning: implicit declaration of function 'cleanupcwcycle' [-Wim
plicit-function-declaration]
LINK Distribution/oscam-1.20-unstable_by_EasyBuild_svn8254-i686-linux-gnu-ssl
lib/libcs-i686-linux-gnu-ssl.a(oscam.o): In function `check_thread':
oscam.c:(.text.check_thread+0x2a1): undefined reference to `cleanupcwcycle'
collect2: ld returned 1 exit status
make[1]: * [Distribution/oscam-1.20-unstable_by_EasyBuild_svn8254-i686-linux-g
nu-ssl] Errore 1
make: * [build_config.mak] Errore 2
cp: impossibile eseguire stat di "/usr/local/bin/oscam-svn/Distribution/oscam*":
File o directory non esistente
mv: impossibile eseguire stat di "*oscam-*svn8254*": File o directory non esiste
nte
How the issue is reproducable
yes
Change History (6)
comment:1 by , 11 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
comment:2 by , 11 years ago
I do not understand why people use scripts from other people to build their revision.
Please do NOT use those scripts but create your own or work from command line
comment:3 by , 11 years ago
@ni_hao:
Because not all people are linux cracks and know how to compile!
comment:4 by , 11 years ago
oscam.c:1909:3: warning: implicit declaration of function 'cleanupcwcycle' [-Wim plicit-function-declaration]
cwc10 patch (CW Cycle Check) don´t work with svn8254 u need a clean svn and cwc11 patch
comment:5 by , 11 years ago
Dear The_Raven, you don't have to be "linux crack" to be able to execute 3 commands by following simple instructions.
comment:6 by , 11 years ago
Excellent gf. If people can not do that and/or do not understand than they should not do try to compile. It is the umpteenth time that a ticket has been created wrongly due to those scripts.
ask the author of your build script. there is no build problem with the current svn.