FreeBSD ports you maintain which are out of date

[portscout]

Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
misc/gkrellmbgchg2  | 0.1.11  | 0.1.12
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: www/chromium

[René Ladan]

Op 3 mei 2014 05:50 schreef "p90s" :
>
>

[...]

>
> Hi - I have built this on 10, but it will no longer launch, I am seeing
this error:
>
> [jv@yeaguy ~] uname -a
> FreeBSD yeaguy.com 10.0-RELEASE-p2 FreeBSD 10.0-RELEASE-p2 #0: Tue Apr 29
17:06:01 UTC 2014
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
amd64
> [jv@yeaguy ~]
>
>
> [jv@yeaguy ~]  /usr/local/bin/chrome
> /usr/local/bin/chrome: /usr/local/share/chromium/chrome: Exec format error
> [jv@yeaguy ~]
>
>
> [jv@yeaguy ~] pkg info chromium
> chromium-34.0.1847.132
> Name   : chromium
> Version: 34.0.1847.132
> Installed on   : Fri May  2 19:10:14 PDT 2014
> Origin : www/chromium
> Architecture   : freebsd:10:x86:64
> Prefix : /usr/local
> Categories : www
> Licenses   : MPL and LGPL21 and BSD3CLAUSE
> Maintainer : chrom...@freebsd.org
> WWW: http://www.chromium.org/Home
> Comment: Mostly BSD-licensed web browser based on WebKit and Gtk+
> Options:
> CODECS : on
> DEBUG  : on
> GCONF  : on
> PULSEAUDIO : on
> TEST   : on

Hm, what happens if you build chromium without the DEBUG option? I had some
weird abort traps with 34.0.1847.116 when running the debug version (on a
laptop with 4 GB RAM).

René
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Force Dependent ports OPTIONS

[Muhammad Moinur Rahman]

Hi Dirk,

How can I enforce it from inside a ports Makefile?

Thanks in advance.

BR,
Muhammad


On Thu, Apr 17, 2014 at 1:41 PM, Dirk Meyer wrote:

>
> > Is there any way I can force a port to build OPENSSL with RFC3379. The
> > scenario is I am working on a port which requires OPENSSL library with
> RFC
> > 3379 but RFC3379 is not on by default. How can I force that OPENSSL is
> > built with RFC 3379?
>
> a)
> add to /etc/make.conf:
> OPTIONS_SET+= RFC3779
>
> b)
> cd /usr/ports/security/openssl
> echo 'OPTIONS_SET+= RFC3779' >> Makefile.local
>
> kind regards Dirk
>
> - Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany
> - [dirk.me...@dinoex.sub.org],[dirk.me...@guug.de],[din...@freebsd.org]
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Blender + clang problem

[Nilton Jose Rizzo]

Em Sun, 04 May 2014 10:10:46 +0930, Shane Ambler escreveu
> On 04/05/2014 08:45, Shane Ambler wrote:
> > On 03/05/2014 11:16, Nilton Jose Rizzo wrote:
> >>
> >>   HI. the blender now abort in install stage
> 
> >> install  -o root -g wheel -m 555
> >> /usr/ports/graphics/blender/work/blenderplayer 
> >> /usr/ports/graphics/blender/work/stage/usr/local/bin/blenderplayer
> >> install  -s -o root -g wheel -m 555
> >> /usr/ports/graphics/blender/work/.build/bin/blenderplayer 
> >> /usr/ports/graphics/blender/work/stage/usr/local/bin/blenderplayer-bin
> >> install: /usr/ports/graphics/blender/work/.build/bin/blenderplayer: No such
> >> file or directory
> >> *** Error code 71
> >>
> > 
> > It appears to be trying to install the player when it wasn't compiled,
> > or failed to link. As a workaround you may have luck disabling the
> > player, you can still run games within blender without building the
> > standalone player.
> > 
> > Are you sure your ports tree is up to date? Are you using any
> > non-default options when you buildworld?
> > 
> >> root@valfenda:/usr/ports/graphics/blender # uname -a
> >> FreeBSD valfenda 11.0-CURRENT FreeBSD 11.0-CURRENT #4 r265171: Thu May  1
> >> 03:25:54 BRT 2014 rizzo@valfenda:/usr/obj/usr/src/sys/VALFENDA  amd64
> >> root@valfenda:/usr/ports/graphics/blender # 
> >
> 
> I just tested building on an 11-CURRENT machine and found that
> /usr/lib/libcam.so had changed causing linking errors from libcdio -
> re-building libcdio solved the issue. libcdio dependency is via ffmpeg.
> 
> Maybe before the install stage there was another error that should have
> stopped the build but didn't. There might be some indication of another
> port that needs re-building first.
> 
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


  Thankx, I'll try it  yesterday and today I was update and upgrade
some ports to version ports tree yesterday.  When finish I'll try to
recompile blender.

   In your last email, the clang was version 3.4 and I change the blender
makefile to use llvm3.4, but its fail was showed in my first message,
I change to original makefile and not work too.  All options was default
options (I used the make rmconfig command to clean all user options)


---
/*
**Nilton José RizzoUFRRJ
**http://www.rizzo.eng.br  http://www.ufrrj.br
**http://lattes.cnpq.br/0079460703536198
**/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

make package no longer installing

[Marcin Wisnicki]

portupgrade -p invokes make with DEPENDS_TARGET=package[1] but this no 
longer installs dependencies. Which target or option should be used 
instead ?


 [1] https://github.com/freebsd/portupgrade/issues/58

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

[QAT] 352960: 4x leftovers

[Ports-QAT]

- Pet portlint: rename patch files
-

  Build ID:  20140504153200-40941
  Job owner: sunp...@freebsd.org
  Buildtime: 8 minutes
  Enddate:   Sun, 04 May 2014 15:40:17 GMT

  Revision:  352960
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=352960

-

Port:net/netmap 0.1.3_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~sunp...@freebsd.org/20140504153200-40941-325642/netmap-0.1.3_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~sunp...@freebsd.org/20140504153200-40941-325643/netmap-0.1.3_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~sunp...@freebsd.org/20140504153200-40941-325644/netmap-0.1.3_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~sunp...@freebsd.org/20140504153200-40941-325645/netmap-0.1.3_1.log


--
Buildarchive URL: 
redports 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Persistent problems building nepomuk

[Pete Carah]

For more than 5 years now, the dependency tree surrounding nepomuk
(soprano, redland, raptor, rasqal, etc) has been missing.  I can't get
nepomuk-core to compile (freebsd 10.0, ports tree fetched last week)
- it doesn't spot the virtuoso backend of soprano, though I have
recompiled ALL of the requirements to soprano, and I can see the
virtuoso backend compile/link.  I do note the "install
databases/virtuoso to enable its functionality" message even though
virtuoso was already installed. 

It would be nice if kde4 would compile with just "cd x11/kde4 ; make ;
make install" but that would require
the dependency tree for the above to be correct in the port makefiles. 
This has been a problem since at least the days of kde 4.5, 5 or more
years now.  I'd hope it would be fixed now, or at least there should
be a script shipped with the system somewhere that could compile these
in the right order (if that order exists?).

portupgrade on a working (from binaries) tree fails too...
This has been true with both pkg and pkgng (note the 5 years or more
comment.)

-- Pete

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: make package no longer installing

[Melvyn Sopacua]

HI Marcin,

On Sun, 4 May 2014, Marcin Wisnicki wrote:


portupgrade -p invokes make with DEPENDS_TARGET=package[1] but this no
longer installs dependencies. Which target or option should be used
instead ?



I fixed this locally by creating a new target in Mk/bsd.local.mk:

full-package: install
@cd ${.CURDIR} && ${MAKE} package
@cd ${.CURDIR} && ${MAKE} package-links
@if [ -f ${PACKAGES}/All/${PKGNAME}${PKG_SUFX} ]; then \
${ECHO_MSG} Package installed in 
${PACKAGES}/All/${PKGNAME}${PKG_SUFX}; \
else \
${ECHO_MSG} "Failed to save package"; \
exit 1; \
fi

You will need USE_LOCAL_MK=yes in /etc/make.conf.

The reason is that STAGE now abuses the package and install targets to
do the staged installations. Once the stage installation is done, the
package target reverts to it's old behavior of installing and packaging
the package. For some reason it doesn't invoke package-links anymore, so
I added as well.

Then you need to fix portupgrade to specify full-package as
DEPENDS_TARGET.
I tried DEPENDS_TARGET="install package" but it won't work, probably
because the cookie check that switches the package target is not
re-evaluated, but spawning a sub make does. I didn't check that
thoroughly.

--
Hope this helps,

Melvyn
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Make loosing a variable (emulators/virtualbox-ose-additions)

[Melvyn Sopacua]

Hi,

emulators/virtualbox-ose-additions always fails for me in the stage
installation, so today I looked a bit further:

Bad:
install  -o root -g wheel -m 444
/usr/obj/ports/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.3.10/out/freebsd.amd64/release/bin/additions/vboxvideo_drv_.so
/usr/obj/ports/usr/ports/emulators/virtualbox-ose-additions/work/stage/usr/local/lib/xorg/modules/drivers/vboxvideo_drv.so

Good:
install  -o root -g wheel -m 444
/usr/obj/ports/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.3.10/out/freebsd.amd64/release/bin/additions/vboxvideo_drv_17.so
/usr/obj/ports/usr/ports/emulators/virtualbox-ose-additions/work/stage/usr/local/lib/xorg/modules/drivers/vboxvideo_drv.so

The difference between bad and good are the 17 missing in the shared
object name. The bad line is created in a clean build and the good line
if one invokes the install target immediately after that failed one.

Is make really loosing a variable here or could this be a parallelization issue 
in the upstream build system?

--
Melvyn
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Make loosing a variable (emulators/virtualbox-ose-additions)

[Bernhard Fröhlich]

Am 04.05.2014 20:44 schrieb "Melvyn Sopacua" :
>
> Hi,
>
> emulators/virtualbox-ose-additions always fails for me in the stage
> installation, so today I looked a bit further:
>
> Bad:
> install  -o root -g wheel -m 444
>
/usr/obj/ports/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.3.10/out/freebsd.amd64/release/bin/additions/vboxvideo_drv_.so
>
/usr/obj/ports/usr/ports/emulators/virtualbox-ose-additions/work/stage/usr/local/lib/xorg/modules/drivers/vboxvideo_drv.so
>
> Good:
> install  -o root -g wheel -m 444
>
/usr/obj/ports/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.3.10/out/freebsd.amd64/release/bin/additions/vboxvideo_drv_17.so
>
/usr/obj/ports/usr/ports/emulators/virtualbox-ose-additions/work/stage/usr/local/lib/xorg/modules/drivers/vboxvideo_drv.so
>
> The difference between bad and good are the 17 missing in the shared
> object name. The bad line is created in a clean build and the good line
> if one invokes the install target immediately after that failed one.
>
> Is make really loosing a variable here or could this be a parallelization
issue in the upstream build system?

That command is part of the port makefile so it's for sure not an upstream
bug. Sounds like the xserver version that is used there is not read
properly in some case.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Make loosing a variable (emulators/virtualbox-ose-additions)

[Melvyn Sopacua]

Hi Bernhard,

On Sun, 4 May 2014, Bernhard Fröhlich wrote:


Am 04.05.2014 20:44 schrieb "Melvyn Sopacua" :


Hi,

emulators/virtualbox-ose-additions always fails for me in the stage
installation, so today I looked a bit further:

Bad:
install  -o root -g wheel -m 444


/usr/obj/ports/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.3.10/out/freebsd.amd64/release/bin/additions/vboxvideo_drv_.so



/usr/obj/ports/usr/ports/emulators/virtualbox-ose-additions/work/stage/usr/local/lib/xorg/modules/drivers/vboxvideo_drv.so


Good:
install  -o root -g wheel -m 444


/usr/obj/ports/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.3.10/out/freebsd.amd64/release/bin/additions/vboxvideo_drv_17.so



/usr/obj/ports/usr/ports/emulators/virtualbox-ose-additions/work/stage/usr/local/lib/xorg/modules/drivers/vboxvideo_drv.so


The difference between bad and good are the 17 missing in the shared
object name. The bad line is created in a clean build and the good line
if one invokes the install target immediately after that failed one.

Is make really loosing a variable here or could this be a parallelization

issue in the upstream build system?

That command is part of the port makefile so it's for sure not an upstream
bug. Sounds like the xserver version that is used there is not read
properly in some case.


I see and makes sense (Mk/bsd.xorg.mk):
.if exists(${LOCALBASE}/bin/X)
XSERVER_VER!=   ${LOCALBASE}/bin/X -version 2>&1 | sed -n 's;^X\.Org X
Server \([^ ]*\).*;\1;p'
.endif

${LOCALBASE}/bin/X won't exist when this is evaluated, unless you cut up
the build stages into a separate make depends followed by make install.

I believe setting a default that is in sync with x11-servers/xorg-server
in bsd.xorg.mk will fix all cases, since if it doesn't exist the
dependency installed will be provided by that port and if it does, you
got the one that was installed by the user.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Are there plans for updating OpenOCD to version 0.8.0?

[Torfinn Ingolfsen]

Hello,
Are there plans for updating devel/openocd to version 0.8.0?

Have a nice day.
-- 
Regards,
Torfinn Ingolfsen
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

[QAT] 352970: 4x leftovers

[Ports-QAT]

Update to new upstream version 2.1.18.

Bugfixes, DMARC policy support.
New dependency on py-dnspython.

Upstream change log:
https://mail.python.org/pipermail/mailman-announce/2014-May/000193.html
-

  Build ID:  20140504204600-60400
  Job owner: mand...@freebsd.org
  Buildtime: 7 minutes
  Enddate:   Sun, 04 May 2014 20:53:25 GMT

  Revision:  352970
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=352970

-

Port:mail/mailman 2.1.18

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~mand...@freebsd.org/20140504204600-60400-325798/mailman-2.1.18.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~mand...@freebsd.org/20140504204600-60400-325799/mailman-2.1.18.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~mand...@freebsd.org/20140504204600-60400-325800/mailman-2.1.18.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~mand...@freebsd.org/20140504204600-60400-325801/mailman-2.1.18.log


--
Buildarchive URL: 
redports 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Upgrade of astro/kstars to 4.12.4_1 fails - linker error

[Dr. Peter Voigt]

I am running 10.0-RELEASE-p2 and after the latest ports tree update the
upgrade of astro/kstars to 4.12.4_1 fails:

# portmaster --no-confirm --no-term-title -D -G kstars

Scanning dependencies of target testcsvparser
[100%] Building CXX object
Tests/CMakeFiles/testfwparser.dir/testfwparser.o [100%] Building CXX
object Tests/CMakeFiles/testcsvparser.dir/testcsvparser.o Linking CXX
executable
testfwparser /usr/ports/astro/kstars/work/kstars-4.12.4/kstars/kstars.cpp:122:7:
warning: '__GLIBC__' is not defined, evaluates to 0 [-Wundef] #if
( __GLIBC__ >= 2 &&__GLIBC_MINOR__ >= 1  && !defined(__UCLIBC__) )
^ /usr/local/lib/libcfitsio.so: undefined reference to
`compress2mem_from_mem' /usr/local/lib/libcfitsio.so: undefined
reference to `compress2file_from_mem' /usr/local/lib/libcfitsio.so:
undefined reference to `uncompress2mem' /usr/local/lib/libcfitsio.so:
undefined reference to `zuncompress2mem' /usr/local/lib/libcfitsio.so:
undefined reference to `uncompress2file' /usr/local/lib/libcfitsio.so:
undefined reference to `uncompress2mem_from_mem' c++: error: linker
command failed with exit code 1 (use -v to see invocation) ---
Tests/testfwparser --- *** [Tests/testfwparser] Error code 1

make[3]: stopped in /usr/ports/astro/kstars/work/.build
1 error

make[3]: stopped in /usr/ports/astro/kstars/work/.build
--- Tests/CMakeFiles/testfwparser.dir/all ---
*** [Tests/CMakeFiles/testfwparser.dir/all] Error code 2

make[2]: stopped in /usr/ports/astro/kstars/work/.build
A failure has been detected in another branch of the parallel make

make[3]: stopped in /usr/ports/astro/kstars/work/.build
--- Tests/CMakeFiles/testcsvparser.dir/all ---
*** [Tests/CMakeFiles/testcsvparser.dir/all] Error code 2

make[2]: stopped in /usr/ports/astro/kstars/work/.build
1 warning generated.
A failure has been detected in another branch of the parallel make

make[3]: stopped in /usr/ports/astro/kstars/work/.build
--- kstars/CMakeFiles/kstars.dir/all ---
*** [kstars/CMakeFiles/kstars.dir/all] Error code 2

make[2]: stopped in /usr/ports/astro/kstars/work/.build
3 errors

make[2]: stopped in /usr/ports/astro/kstars/work/.build
--- all ---
*** [all] Error code 2

make[1]: stopped in /usr/ports/astro/kstars/work/.build
1 error

make[1]: stopped in /usr/ports/astro/kstars/work/.build
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the
failure to the maintainer.
*** Error code 1

Stop.
make: stopped in /usr/ports/astro/kstars

===>>> make failed for astro/kstars
===>>> Aborting update

===>>> Update for astro/kstars failed
===>>> Aborting update

===>>> Killing background jobs
Terminated

===>>> You can restart from the point of failure with this command line:
   portmaster  astro/kstars 

===>>> Exiting

Can this easily be solved or should I open a PR?

Regards,
Peter
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

chrome does not work inside a jail

[Erich Dollansky]

Hi,

I just installed chrome inside a jail. It does not display anything. No
matter what it is like settings or configuration or any website. The
same works as expected when chrome runs inside the host system.

The chrome version is Version 33.0.1750.152 (256984).

When I run other applications like firefox, kate, gedit or claws-mail
in a jail, it all works.

Is this normal?

Erich

PS: this is the console output I get when I run chrome inside a jail:

[88985:293626880:0504/204051:ERROR:browser_main_loop.cc(234)] Gdk:
shmget failed: error 78 (Function not implemented)
[88997:293626880:0504/204052:ERROR:context_group.cc(149)]
ContextGroup::Initialize failed because too few texture units
supported.
[88997:293626880:0504/204052:ERROR:gles2_cmd_decoder.cc(2255)]
GpuScheduler::InitializeCommon failed because group failed to
initialize.
[88993:293626880:0504/204052:ERROR:command_buffer_proxy_impl.cc(165)]
Failed to initialize command buffer service.
[88997:293626880:0504/204052:ERROR:context_group.cc(149)]
ContextGroup::Initialize failed because too few texture units
supported.
[88997:293626880:0504/204052:ERROR:gles2_cmd_decoder.cc(2255)]
GpuScheduler::InitializeCommon failed because group failed to
initialize.
[88993:293626880:0504/204052:ERROR:command_buffer_proxy_impl.cc(165)]
Failed to initialize command buffer service.
[88997:293626880:0504/204052:ERROR:context_group.cc(149)]
ContextGroup::Initialize failed because too few texture units
supported.
[88997:293626880:0504/204052:ERROR:gles2_cmd_decoder.cc(2255)]
GpuScheduler::InitializeCommon failed because group failed to
initialize.
[88993:293626880:0504/204052:ERROR:command_buffer_proxy_impl.cc(165)]
Failed to initialize command buffer service.
[88997:293626880:0504/204052:ERROR:context_group.cc(149)]
ContextGroup::Initialize failed because too few texture units
supported.
[88997:293626880:0504/204052:ERROR:gles2_cmd_decoder.cc(2255)]
GpuScheduler::InitializeCommon failed because group failed to
initialize.
[88993:293626880:0504/204052:ERROR:command_buffer_proxy_impl.cc(165)]
Failed to initialize command buffer service.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: chrome does not work inside a jail

[Fbsd8]

Erich Dollansky wrote:

Hi,

I just installed chrome inside a jail. It does not display anything. No
matter what it is like settings or configuration or any website. The
same works as expected when chrome runs inside the host system.

The chrome version is Version 33.0.1750.152 (256984).

When I run other applications like firefox, kate, gedit or claws-mail
in a jail, it all works.

Is this normal?

Erich




What do you mean by "installed chrome inside a jail"?

What version of FreeBSD you running?
Are you running xorg and desktop in a jail?
What video card are you using?

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: chrome does not work inside a jail

[Erich Dollansky]

Hi,

On Sun, 04 May 2014 21:10:53 -0400
Fbsd8  wrote:

> Erich Dollansky wrote:
> > 
> > I just installed chrome inside a jail. It does not display
> > anything. No matter what it is like settings or configuration or
> > any website. The same works as expected when chrome runs inside the
> > host system.
> > 
> > The chrome version is Version 33.0.1750.152 (256984).
> > 
> > When I run other applications like firefox, kate, gedit or
> > claws-mail in a jail, it all works.
> > 
> > Is this normal?
> > 
> > Erich
> > 
> 
> 
> What do you mean by "installed chrome inside a jail"?

I created a normal FreeBSD jail. I copied the ports tree into the jail.
Started the jail and compiled chrome.
> 
> What version of FreeBSD you running?

10.0 STABLE.

> Are you running xorg and desktop in a jail?

No, X run directly on the machine. Also the desktop. I used telnet to
connect to the jail.

> What video card are you using?
> 
I use the internal GPU of a second generation i7 CPU.

Erich
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"