Re: [Slackbuilds-users] runc

2020-06-05 Thread Bruno T. Russo
Hi Gabriel, thanks for your help. The problem was solved. Atenciosamente, ___ *Bruno Tadeu Russo | Consultor de TI* *e-mail.* b...@brunorusso.com.br | bru...@gmail.com *tel.* +55 11 98277-9985 | +55 11 3280-8086 *skype.* brunorusso *site.*

[Slackbuilds-users] Updates - 20200606.1

2020-06-05 Thread Willy Sudiarto Raharjo
Sat Jun 6 03:08:25 UTC 2020 academic/R: Updated for version 4.0.0. academic/fet: Updated for version 5.44.8. academic/nco: Updated for version 4.9.3. academic/sage: Updated for version 9.1. academic/xiphos: Updated for version 4.2.1. audio/snd: Updated for version 20.3. desktop/autorandr: Updated

Re: [Slackbuilds-users] runc

2020-06-05 Thread Christopher L Duston via SlackBuilds-users
Indeed, this was my real problem. I saw the comments about /etc/profile in the README, and so I reasoned that su would get me the environment if it had been set right. su - indicates my environment was originally set up correctly by google-go-lang. I would advocate for inclusion of relog

Re: [Slackbuilds-users] runc

2020-06-05 Thread Willy Sudiarto Raharjo
> I am having the same problem with runc - and the wrong compiler might be the > issue, since I get: > > $ go version > go version go1.4.2 gccgo (GCC) 5.5.0 linux/amd64 > > But this was installed by google-go-lang, upon which runc depends. So is the > dependency list for runc inaccurate? If

Re: [Slackbuilds-users] runc

2020-06-05 Thread B Watson
On 6/5/20, Christopher L Duston via SlackBuilds-users wrote: > Thanks, indeed, that was the problem. I successfully installed runc with a > temporary fix to the $PATH for root (since I don't know the proper place to > permanently set root environmental variables). > > Shouldn't this be discussed

Re: [Slackbuilds-users] runc

2020-06-05 Thread Christopher L Duston via SlackBuilds-users
Thanks, indeed, that was the problem. I successfully installed runc with a temporary fix to the $PATH for root (since I don't know the proper place to permanently set root environmental variables). Shouldn't this be discussed in the README for google-go-lang? Instead, I'm going to Google to

Re: [Slackbuilds-users] runc

2020-06-05 Thread Erich Ritz via SlackBuilds-users
‐‐‐ Original Message ‐‐‐ On Friday, June 5, 2020 1:58 PM, Christopher L Duston via SlackBuilds-users wrote: > I am having the same problem with runc - and the wrong compiler might be the > issue, since I get: > > $ go version > go version go1.4.2 gccgo (GCC) 5.5.0 linux/amd64 > > But

Re: [Slackbuilds-users] runc

2020-06-05 Thread Christopher L Duston via SlackBuilds-users
I am having the same problem with runc - and the wrong compiler might be the issue, since I get: $ go version go version go1.4.2 gccgo (GCC) 5.5.0 linux/amd64 But this was installed by google-go-lang, upon which runc depends. So is the dependency list for runc inaccurate? Sent with

[Slackbuilds-users] Multimedia > xvidcore (1.3.5) update

2020-06-05 Thread King Beowulf
Hello xvidcore-1.3.7 builds and appears to work on both 14.2 and current. -Ed signature.asc Description: OpenPGP digital signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org