Jump to content


Photo

OpenPLi 6.0 » Release candidate


  • This topic is locked This topic is locked
820 replies to this topic

Re: OpenPLi 6.0 » Release candidate #461 WanWizard

  • PLi® Core member
  • 70,220 posts

+1,798
Excellent

Posted 26 July 2017 - 21:59

With this new way of creating images, everything is a bit confusing.

Release, R/C and develop.

Why can't they be delivered like they were on OP4 ?

The daily image we had on OP4 could be the develop one, and after several days of test on develop and being OK, it can be applied to stable.

Isn't it easier ??

 

I can't help that. ;)

 

Because a daily unstable image is perhaps nice for a developer, but 99.999% of the OpenPli users don't develop. They want an image that always works. And you should develop new features on the "develop" branch, which after testing will becomt the next R/C, which after more rigerous testing becomes the next release.

 

The only point is now that there is no public develop image, and that is simply because of capacity, and the fact that developers should be knowledgable enough to compile their own images. If you develop, having a new image only once a day isn't very useful anyway, so we decided it didn't have priority.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: OpenPLi 6.0 » Release candidate #462 jpuigs

  • Senior Member
  • 1,143 posts

+32
Good

Posted 26 July 2017 - 22:18

 

 

Because a daily unstable image is perhaps nice for a developer, but 99.999% of the OpenPli users don't develop. They want an image that always works. And you should develop new features on the "develop" branch, which after testing will becomt the next R/C, which after more rigerous testing becomes the next release.

 

I see what you mean, but as you say (I agree) 99% of OP users don't develop it has no sense to have a R/C image.

A develop, and a stable image.

From develop images, after rigerous testing they should become Stable Release.

When i said daily develop images, I should have said continous develop images, named like oscam releases, with a sequential number r11380, r11381.....

That's my opinion.


Enigma is getting old....

 

Spoiler

Re: OpenPLi 6.0 » Release candidate #463 Huevos

  • PLi® Contributor
  • 4,621 posts

+161
Excellent

Posted 26 July 2017 - 22:42

"developers should be knowledgable enough to compile their own images."

 

Not just about knowledge, but also resources and hardware. And for people that contribute to multiple images it means setting up multiple build environments.



Re: OpenPLi 6.0 » Release candidate #464 WanWizard

  • PLi® Core member
  • 70,220 posts

+1,798
Excellent

Posted 26 July 2017 - 22:51

I see what you mean, but as you say (I agree) 99% of OP users don't develop it has no sense to have a R/C image.

 

Without an R/C image, you can never release. At some point in time, you need to say "this version of develop should be released". Then you branch of develop to rc and freeze it, and start testing the rc, while development in develop continues. When you find bugs, fix them, when the rc is stable, release it. The main problem we had with OpenPLi 4, is that is was NEVER stable, there was always something going onso a release could never be pinned down.

 

When i said daily develop images, I should have said continous develop images, named like oscam releases, with a sequential number r11380, r11381.....

That's my opinion.

 

That indicates a bit that you don't really know enough to form an opinion about this.  

 

To give you an idea, we use high-end Core I7's with very fast SSD disks as our build servers. An initial single image build takes about 2 hours on this machine. A complete build run, for all images, with a fully populated build cache, takes about 6 hours. If you want to implement contineous integration (a compile run per commit/push), you need an entire server farm of these machines, given the number of commits in a day. Doable given unlimited funding, but unfortunately we're not so rich. ;)


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: OpenPLi 6.0 » Release candidate #465 WanWizard

  • PLi® Core member
  • 70,220 posts

+1,798
Excellent

Posted 26 July 2017 - 22:54

"developers should be knowledgable enough to compile their own images."

 

Not just about knowledge, but also resources and hardware. And for people that contribute to multiple images it means setting up multiple build environments.

 

True.

 

I didn't say they will not come in the future, I just said that given the limited build resources we have at the moment, we have to set priorities. We need to purchase more build servers if we want to build and publish develop images.

 

This is under discussion at the moment, but expensive and complex to organize (needs a location with at least 200Mbps upstream for image and feed distribution), see also my previous post. ;)


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: OpenPLi 6.0 » Release candidate #466 WanWizard

  • PLi® Core member
  • 70,220 posts

+1,798
Excellent

Posted 26 July 2017 - 23:09

@jpuigs,

 

For information, this nicely describes the development methology we have adopted: https://datasift.git...ingGitFlow.html


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: OpenPLi 6.0 » Release candidate #467 jpuigs

  • Senior Member
  • 1,143 posts

+32
Good

Posted 26 July 2017 - 23:11

GitFlowMasterBranch.png

 

 

 

Ok. Understood.


Edited by jpuigs, 26 July 2017 - 23:15.

Enigma is getting old....

 

Spoiler

Re: OpenPLi 6.0 » Release candidate #468 Jackdaw

  • Member
  • 3 posts

0
Neutral

Posted 27 July 2017 - 13:28

What smartcard? I've seen CCcam crash on some, but never freeze.

 

Which is logical, it's an antique, maybe you should switch to Oscam. Soon you'll have to, all new hardware is all ARM CPU based, for which no CCcam exists.

The author of CCcam could recompile his software for ARM CPU's. Why do think this would never happen?

PS I'm not the author, just asking.



Re: OpenPLi 6.0 » Release candidate #469 WanWizard

  • PLi® Core member
  • 70,220 posts

+1,798
Excellent

Posted 27 July 2017 - 14:19

CCcam hasn't been maintained in years. Yes, it could happen. But if I were you, I won't hold your breath.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: OpenPLi 6.0 » Release candidate #470 Ronnie1966

  • Senior Member
  • 232 posts

+8
Neutral

Posted 28 July 2017 - 16:19

Can someone of the team tell me if the BSP layer for Gigablue is coming?
I've heard rumors that they're working on it at the moment

Greets Ronnie1966

VU+ Ultimo 4K OpenPli 8.3 latest 1TB
Gigablue ULTRA UHD OpenPli 8.3
VU+ Zero 4K OpenPli 8.3
Samsung 65” Neo QLED 8K 65QN900A

Bose Soundbar 900 White
Synology 218+ Play 2x 3TB


Re: OpenPLi 6.0 » Release candidate #471 WanWizard

  • PLi® Core member
  • 70,220 posts

+1,798
Excellent

Posted 28 July 2017 - 20:57

Rumours are true, we are talking with Gigablue about OpenPLi support. But no ETA on it, and no idea yet which hardware that BSP will support.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: OpenPLi 6.0 » Release candidate #472 Vytenis P.

  • Senior Member
  • 28 posts

0
Neutral

Posted 29 July 2017 - 07:11

Don't you think the new 6-th Open PLi rename to "Open Expert"? ;)
Becomes bored to repeat for users "Switch On Expert, please"


Vu+ Duo2 & Vu+ Ultimo 4K


Re: OpenPLi 6.0 » Release candidate #473 Pr2

  • PLi® Contributor
  • 6,165 posts

+261
Excellent

Posted 29 July 2017 - 10:10

Hi,

 

I agree people get confused by those different levels, I am not sure if this was a good idea.

 

For people migrating from OpenPLi4 to OpenPLi6 would be better to set them into Expert level by default and perhaps keep the basic level for end-user installing OpenPli6 without restoring any settings (so potentially newbies).

 

Another suggestion is to start a Wizard that explain the different menu levels when there is no menu level defined in configuration, so I think that this will clarify the situation for newbies but also for people migrating to latest OpenPLi.

 

Pr2


NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.
If you think that my answer helps you, you can press the up arrow in bottom right of the answer.

Wanna help with OpenPLi Translation? Please read our Wiki Information for translators

Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)

AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
 


Re: OpenPLi 6.0 » Release candidate #474 littlesat

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 29 July 2017 - 10:15

It is a great idea these levels... the nerds can find it... As every change you have to get used to it.

Edited by littlesat, 29 July 2017 - 10:15.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: OpenPLi 6.0 » Release candidate #475 Dream1975

  • Senior Member
  • 1,634 posts

+14
Neutral

Posted 29 July 2017 - 10:23

Indeed, but it might be a good idea to let the box ask which level you want after the flas when releasing the stable (and set it standard to normal with a short explanation what the levels mean). I think it will save a lot of questions where the settings are if people transfer from 4 to 6 stable as they are now used to seeing everything.


Edited by Dream1975, 29 July 2017 - 10:24.

Mutant HD2400, OpenPLi nightly, 2x DVB-C & 2x DVB-S

Mutant HD51, OpenPLi nightly, 1x DVB-C & 1x DVB-S

Wavefrontier T55 (Astra 1,2,3 en HB)

Smartcards Ziggo (Irdeto) and CDS (Seca) on Oscam

 


Re: OpenPLi 6.0 » Release candidate #476 WanWizard

  • PLi® Core member
  • 70,220 posts

+1,798
Excellent

Posted 29 July 2017 - 12:04

You have to keep in mind that the vast majority of OpenPLi users are not members of this forum, and are not experts. They would not know how to deal with a question like this. On the other hand, I do expect from "experts" that they are active here, and at least know how to work the settings menu's. ;)

 

The main problem is that for some stupid reason, Enigma doesn't store configuration values that are default. And since originally "expert" seems to have been made the default (another stupid reason), that is not stored in /etc/enigma/settings. This in turn means that if you change the default (like we did for OpenPLi 6), it also changes the users settings, even if that user has restored a backup.

 

I really like this changed, but some fear performance issues, and don't want this changed. Personally, I'd rather have Enigma start up 2 seconds slower than having to deal with all this, but who am I? ;)


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: OpenPLi 6.0 » Release candidate #477 dax

  • Senior Member
  • 228 posts

0
Neutral

Posted 29 July 2017 - 13:06

Could be fixed the this error?

Build Configuration:
BB_VERSION        = "1.32.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "ArchLinux"
TARGET_SYS        = "mipsel-oe-linux"
MACHINE           = "vusolo2"
DISTRO            = "openpli"
DISTRO_VERSION    = "homebuild"
TUNE_FEATURES     = "o32 fpu-hard mips32"
TARGET_FPU        = ""
meta-oe           
meta-filesystems  
meta-multimedia   
meta-networking   
meta-python       = "HEAD:1efa5d623bc64659b57389e50be2568b1355d5f7"
meta              = "HEAD:eb2fc2cd9081a4533ed30fe81c9f491b06cc5ae1"
meta-openpli      
meta-dream        = "rc-6.0:0d16ff0dd93c3e47de64d1c398966ea516c11316"
meta-vuplus       = "HEAD:ba0c73f4ea3433b9bca6946c09cdde3c593dac07"
meta-xsarius.pli5 = "HEAD:260ad02ae4cf867a6bf374a6ab5c5da039a818ad"
meta-xp           = "HEAD:dc30375655b0f1bcf68bb7c7d4a4b0e75563c06f"
meta-xtrend       = "HEAD:1502e5d07a3e61001a89bbceeecd3e4a44d2bed8"
meta-formuler     = "HEAD:8a604a73fbae8ca21d77b2a9a7e91b08e5893b30"
meta-gfutures     = "HEAD:d9a4126c0663868587450647037341e39374d1de"
meta-xpeedc       = "HEAD:6474b33f24809f62825d6701639d1025e36f8f3a"
meta-wetek        = "HEAD:49f4e1e6fa429d4e4be11287c8740f54334a0e96"
meta-zgemma       = "HEAD:c60c12345c099546b3eab2ac464edee4cc5c6e5e"
meta-edision      = "HEAD:5bdc71eac49aa7c683f3b078d3c8ad4c7df57a85"
meta-miraclebox   = "HEAD:d44871d4d1f357d5b38488ed505b48fa8c8feff3"
meta-spycat       = "HEAD:71a20e123f68b80045ea3f3aa6d7db4945b25f47"
meta-gi           = "HEAD:c3aa7e9de3a6b4390036d6c5e3d09bccb150f17e"
meta-sab          = "HEAD:92262feb14e4005c8096150daac7313e9cb3d85a"
meta-local        = "rc-6.0:0d16ff0dd93c3e47de64d1c398966ea516c11316"
meta-qt5          = "HEAD:8ba28144d5571504112fd4f32c7bfcbac531e2cb"

Initialising tasks: 100% |####################################################################################################################| Time: 0:00:08
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: automake-native-1.15-r0 do_compile: oe_runmake failed
ERROR: automake-native-1.15-r0 do_compile: Function failed: do_compile (log file is located at /home/davide/openpli_RC/openpli-oe-core/build/tmp/work/x86_64-linux/automake-native/1.15-r0/temp/log.do_compile.14579)
ERROR: Logfile of failure stored in: /home/davide/openpli_RC/openpli-oe-core/build/tmp/work/x86_64-linux/automake-native/1.15-r0/temp/log.do_compile.14579
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 4
| rm -f bin/automake bin/automake-t bin/automake-t2 \
|   && /usr/bin/mkdir -p bin \
|   && in=bin/automake.in && ( sed -e "s,[@]configure_input[@],Generated from $in; do not edit by hand.,g" -e 's,[@]datadir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share,g' -e 's,[@]amdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15/am,g' -e 's,[@]bindir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/bin,g' -e 's,[@]docdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/doc/automake,g' -e 's,[@]pkgvdatadir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15,g' -e 's,[@]scriptdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15,g' -e 's,[@]automake_acdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/aclocal-1.15,g' -e 's,[@]system_acdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/aclocal,g' -e 's,[@]am__isrc[@],!!@!!am__isrc!!@!!,g' | /bin/sh ./config.status --file=- | sed -e 's,!!@!!am__isrc!!@!!,@''am__isrc@,g' ) <../automake-1.15/$in >bin/automake-t \
|   && /usr/bin/perl -w ../automake-1.15/bin/gen-perl-protos bin/automake-t > bin/automake-t2 \
|   && mv -f bin/automake-t2 bin/automake-t \
|   && chmod a+x,a-w bin/automake-t && mv -f bin/automake-t bin/automake
| rm -f bin/aclocal bin/aclocal-t bin/aclocal-t2 \
|   && /usr/bin/mkdir -p bin \
|   && in=bin/aclocal.in && ( sed -e "s,[@]configure_input[@],Generated from $in; do not edit by hand.,g" -e 's,[@]datadir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share,g' -e 's,[@]amdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15/am,g' -e 's,[@]bindir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/bin,g' -e 's,[@]docdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/doc/automake,g' -e 's,[@]pkgvdatadir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15,g' -e 's,[@]scriptdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15,g' -e 's,[@]automake_acdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/aclocal-1.15,g' -e 's,[@]system_acdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/aclocal,g' -e 's,[@]am__isrc[@],!!@!!am__isrc!!@!!,g' | /bin/sh ./config.status --file=- | sed -e 's,!!@!!am__isrc!!@!!,@''am__isrc@,g' ) <../automake-1.15/$in >bin/aclocal-t \
|   && /usr/bin/perl -w ../automake-1.15/bin/gen-perl-protos bin/aclocal-t > bin/aclocal-t2 \
|   && mv -f bin/aclocal-t2 bin/aclocal-t \
|   && chmod a+x,a-w bin/aclocal-t && mv -f bin/aclocal-t bin/aclocal
| rm -f t/ax/shell-no-trail-bslash t/ax/shell-no-trail-bslash-t
| in=t/ax/shell-no-trail-bslash.in \
|   && /usr/bin/mkdir -p t/ax \
|   && ( sed -e "s,[@]configure_input[@],Generated from $in; do not edit by hand.,g" -e 's,[@]datadir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share,g' -e 's,[@]amdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15/am,g' -e 's,[@]bindir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/bin,g' -e 's,[@]docdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/doc/automake,g' -e 's,[@]pkgvdatadir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15,g' -e 's,[@]scriptdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15,g' -e 's,[@]automake_acdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/aclocal-1.15,g' -e 's,[@]system_acdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/aclocal,g' -e 's,[@]am__isrc[@],!!@!!am__isrc!!@!!,g' | /bin/sh ./config.status --file=- | sed -e 's,!!@!!am__isrc!!@!!,@''am__isrc@,g' ) <../automake-1.15/$in >t/ax/shell-no-trail-bslash-t \
|   && chmod a+x t/ax/shell-no-trail-bslash-t
| make[1]: Entering directory '/home/davide/openpli_RC/openpli-oe-core/build/tmp/work/x86_64-linux/automake-native/1.15-r0/build'
| make[1]: Leaving directory '/home/davide/openpli_RC/openpli-oe-core/build/tmp/work/x86_64-linux/automake-native/1.15-r0/build'
| rm -f t/ax/cc-no-c-o t/ax/cc-no-c-o-t
| in=t/ax/cc-no-c-o.in \
|   && /usr/bin/mkdir -p t/ax \
|   && ( sed -e "s,[@]configure_input[@],Generated from $in; do not edit by hand.,g" -e 's,[@]datadir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share,g' -e 's,[@]amdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15/am,g' -e 's,[@]bindir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/bin,g' -e 's,[@]docdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/doc/automake,g' -e 's,[@]pkgvdatadir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15,g' -e 's,[@]scriptdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15,g' -e 's,[@]automake_acdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/aclocal-1.15,g' -e 's,[@]system_acdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/aclocal,g' -e 's,[@]am__isrc[@],!!@!!am__isrc!!@!!,g' | /bin/sh ./config.status --file=- | sed -e 's,!!@!!am__isrc!!@!!,@''am__isrc@,g' ) <../automake-1.15/$in >t/ax/cc-no-c-o-t \
|   && chmod a+x t/ax/cc-no-c-o-t
| rm -f runtest runtest-t
| in=t/ax/runtest.in \
|   && /usr/bin/mkdir -p t/ax \
|   && ( sed -e "s,[@]configure_input[@],Generated from $in; do not edit by hand.,g" -e 's,[@]datadir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share,g' -e 's,[@]amdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15/am,g' -e 's,[@]bindir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/bin,g' -e 's,[@]docdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/doc/automake,g' -e 's,[@]pkgvdatadir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15,g' -e 's,[@]scriptdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15,g' -e 's,[@]automake_acdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/aclocal-1.15,g' -e 's,[@]system_acdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/aclocal,g' -e 's,[@]am__isrc[@],!!@!!am__isrc!!@!!,g' | /bin/sh ./config.status --file=- | sed -e 's,!!@!!am__isrc!!@!!,@''am__isrc@,g' ) <../automake-1.15/$in >runtest-t \
|   && chmod a+x runtest-t
| if LC_ALL=C grep '@[a-zA-Z0-9_][a-zA-Z0-9_]*@' t/ax/shell-no-trail-bslash-t; then echo "t/ax/shell-no-trail-bslash contains unexpanded substitution (see lines above)"; exit 1; fi; chmod a-w t/ax/shell-no-trail-bslash-t && mv -f t/ax/shell-no-trail-bslash-t t/ax/shell-no-trail-bslash
| : \
|   && /usr/bin/mkdir -p doc \
|   && f=`echo doc/aclocal.1 | sed 's|.*/||; s|\.1$||; s,x,x,'` \
|   && echo ".so man1/$f-1.15.1" > doc/aclocal.1
| : \
|   && /usr/bin/mkdir -p doc \
|   && f=`echo doc/automake.1 | sed 's|.*/||; s|\.1$||; s,x,x,'` \
|   && echo ".so man1/$f-1.15.1" > doc/automake.1
| rm -f lib/Automake/Config.pm lib/Automake/Config.pm-t
| /usr/bin/mkdir -p lib/Automake
| in=Config.in \
|   && ( sed -e "s,[@]configure_input[@],Generated from $in; do not edit by hand.,g" -e 's,[@]datadir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share,g' -e 's,[@]amdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15/am,g' -e 's,[@]bindir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/bin,g' -e 's,[@]docdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/doc/automake,g' -e 's,[@]pkgvdatadir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15,g' -e 's,[@]scriptdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15,g' -e 's,[@]automake_acdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/aclocal-1.15,g' -e 's,[@]system_acdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/aclocal,g' -e 's,[@]am__isrc[@],!!@!!am__isrc!!@!!,g' | /bin/sh ./config.status --file=- | sed -e 's,!!@!!am__isrc!!@!!,@''am__isrc@,g' ) <../automake-1.15/lib/Automake/Config.in >lib/Automake/Config.pm-t
| ERROR: oe_runmake failed
| rm -f t/ax/test-defs.sh t/ax/test-defs.sh-t
| /usr/bin/mkdir -p t/ax
| in=t/ax/test-defs.in \
|   && ( sed -e "s,[@]configure_input[@],Generated from $in; do not edit by hand.,g" -e 's,[@]datadir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share,g' -e 's,[@]amdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15/am,g' -e 's,[@]bindir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/bin,g' -e 's,[@]docdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/doc/automake,g' -e 's,[@]pkgvdatadir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15,g' -e 's,[@]scriptdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/automake-1.15,g' -e 's,[@]automake_acdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/aclocal-1.15,g' -e 's,[@]system_acdir[@],/home/davide/openpli_RC/openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/share/aclocal,g' -e 's,[@]am__isrc[@],!!@!!am__isrc!!@!!,g' | /bin/sh ./config.status --file=- | sed -e 's,!!@!!am__isrc!!@!!,@''am__isrc@,g' ) <../automake-1.15/$in >t/ax/test-defs.sh-t
| if LC_ALL=C grep '@[a-zA-Z0-9_][a-zA-Z0-9_]*@' t/ax/cc-no-c-o-t; then echo "t/ax/cc-no-c-o contains unexpanded substitution (see lines above)"; exit 1; fi; chmod a-w t/ax/cc-no-c-o-t && mv -f t/ax/cc-no-c-o-t t/ax/cc-no-c-o
| if LC_ALL=C grep '@[a-zA-Z0-9_][a-zA-Z0-9_]*@' runtest-t; then echo "runtest contains unexpanded substitution (see lines above)"; exit 1; fi; chmod a-w runtest-t && mv -f runtest-t runtest
| if LC_ALL=C grep '@[a-zA-Z0-9_][a-zA-Z0-9_]*@' t/ax/test-defs.sh-t; then echo "t/ax/test-defs.sh contains unexpanded substitution (see lines above)"; exit 1; fi; chmod a-w t/ax/test-defs.sh-t && mv -f t/ax/test-defs.sh-t t/ax/test-defs.sh
| if LC_ALL=C grep '@[a-zA-Z0-9_][a-zA-Z0-9_]*@' lib/Automake/Config.pm-t; then echo "lib/Automake/Config.pm contains unexpanded substitution (see lines above)"; exit 1; fi; chmod a-w lib/Automake/Config.pm-t && mv -f lib/Automake/Config.pm-t lib/Automake/Config.pm
| : && /usr/bin/mkdir -p doc && { PATH='/home/davide/openpli_RC/openpli-oe-core/build/tmp/work/x86_64-linux/automake-native/1.15-r0/build/t/wrap:'$PATH && export PATH; } && /usr/bin/perl ../automake-1.15/doc/help2man --output=doc/aclocal-1.15.1 aclocal-1.15
| : && /usr/bin/mkdir -p doc && { PATH='/home/davide/openpli_RC/openpli-oe-core/build/tmp/work/x86_64-linux/automake-native/1.15-r0/build/t/wrap:'$PATH && export PATH; } && /usr/bin/perl ../automake-1.15/doc/help2man --output=doc/automake-1.15.1 automake-1.15
| help2man: can't get `--help' info from automake-1.15
| Try `--no-discard-stderr' if option outputs to stderr
| make: *** [Makefile:3687: doc/automake-1.15.1] Error 255
| make: *** Waiting for unfinished jobs....
| ERROR: Function failed: do_compile (log file is located at /home/davide/openpli_RC/openpli-oe-core/build/tmp/work/x86_64-linux/automake-native/1.15-r0/temp/log.do_compile.14579)
ERROR: Task (virtual:native:/home/davide/openpli_RC/openpli-oe-core/openembedded-core/meta/recipes-devtools/automake/automake_1.15.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 96 tasks of which 0 didn't need to be rerun and 1 failed.
NOTE: Writing buildhistory

Summary: 1 task failed:
  virtual:native:/home/davide/openpli_RC/openpli-oe-core/openembedded-core/meta/recipes-devtools/automake/automake_1.15.bb:do_compile
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

Archlinux machine from rc-6.0 branch

Thanks in advance



Re: OpenPLi 6.0 » Release candidate #478 Jackdaw

  • Member
  • 3 posts

0
Neutral

Posted 29 July 2017 - 13:28

 

What smartcard? I've seen CCcam crash on some, but never freeze.

 

Which is logical, it's an antique, maybe you should switch to Oscam. Soon you'll have to, all new hardware is all ARM CPU based, for which no CCcam exists.

The author of CCcam could recompile his software for ARM CPU's. Why do think this would never happen?

PS I'm not the author, just asking.

 

 

 

CCcam hasn't been maintained in years. Yes, it could happen. But if I were you, I won't hold your breath.

 

I'm using Oscam as well and I'm lucky with it, but it lacks support for the "SoftCam.Key" file.

I wish, the Oscam developers will consider this, because the hardware industry seems to force us to ARM SoC's, according to your statement.



Re: OpenPLi 6.0 » Release candidate #479 Rick Hunter

  • PLi® Core member
  • 9,064 posts

+56
Good

Posted 29 July 2017 - 14:10

Don't you think the new 6-th Open PLi rename to "Open Expert"? ;)
Becomes bored to repeat for users "Switch On Expert, please"

If people would read the release notes first.. then some questions were not asked...  ;)


Plinux member We have a.. (ehmm.. morgage) house.

Re: OpenPLi 6.0 » Release candidate #480 MiLo

  • PLi® Core member
  • 14,055 posts

+298
Excellent

Posted 29 July 2017 - 14:56

Don't you think the new 6-th Open PLi rename to "Open Expert"? ;)
Becomes bored to repeat for users "Switch On Expert, please"


Ah, well, years ago "expert" was made default in OpenPLi for exactly that reason. Not being "expert" used to hide stuff all over the place.
Real musicians never die - they just decompose


8 user(s) are reading this topic

0 members, 8 guests, 0 anonymous users