Opened 7 years ago

Last modified 7 years ago

#44417 new defect

p5-opengl: fails on buildbot; _RegisterApplication(), FAILED TO establish the default connection to the WindowServer

Reported by: mojca (Mojca Miklavec) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: mf2k (Frank Schima)
Port: p5-opengl

Description

See:

The buildbot is not able to compile p5.18-opengl and p5.20-opengl.

DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_mports_dports_perl_p5-opengl/p5.20-opengl/work/OpenGL-0.62" && /opt/local/bin/perl5.20 Makefile.PL INSTALLDIRS=vendor CC="/usr/bin/clang" LD="/usr/bin/clang"'
DEBUG: Executing command line:  cd "/opt/local/var/macports/build/_opt_mports_dports_perl_p5-opengl/p5.20-opengl/work/OpenGL-0.62" && /opt/local/bin/perl5.20 Makefile.PL INSTALLDIRS=vendor CC="/usr/bin/clang" LD="/usr/bin/clang" 
_RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL.
2014-07-24 00:23:13.493 glversion[62839:407] invalid CoreGraphics connection
2014-07-24 00:23:13.494 glversion[62839:407] invalid CoreGraphics connection
2014-07-24 00:23:13.494 glversion[62839:407] GLUT Fatal Error: pixel format with necessary capabilities not found.
make: *** [glversion.txt] Error 1

But it works when building from source on a regular computer. Buildbot is apparently "missing some gui initialization".

Search engines find a lot of hits with the same error message, for example

Change History (3)

comment:1 Changed 7 years ago by ryandesign (Ryan Schmidt)

Yes, it is known that the buildslaves cannot do all the GUI things that you can do on your computer when you're logged in as a regular user. Sorry.

comment:2 Changed 7 years ago by mojca (Mojca Miklavec)

What I don't understand is why the build fails. Couldn't the installation proceed in such a way that one would avoid the failure?

That is: couldn't the source code be modified in such a way that it wouldn't throw an error?

Last edited 7 years ago by mojca (Mojca Miklavec) (previous) (diff)

comment:3 Changed 7 years ago by seanmostafavi

This happens on my machine as well. It started three updates ago and I've been running into it for about three months and haven't been able to update my ports since that time. I'm trying to port upgrade outdated on OS X Mavericks 10.9.5 and run port selfupdate before that. Any help is greatly appreciated. Thanks.

Note: See TracTickets for help on using tickets.